Jump to content
Search In
  • More options...
Find results that contain...
Find results in...
blur

Fplaunch With Jukebox And New Focus Routines

Recommended Posts

With the latest FPLaunch, do I need ExitEmulatorKey1, 2, and 3 or can I delete these settings from the ini file, and just use ExitKey instead?

Share this post


Link to post
Share on other sites

Sly this latest version will rename 4 lines and deletes 1 but it leaves the old ones behind. My second post in this thread shows which ones can be deleted and or the change log tells you. 

Share this post


Link to post
Share on other sites

Jasonsmith thanks so much, I have deleted those lines and it still works correctly, yeah.  I always was confused why exit2 and exit3 keys were set up.  Much cleaner settings.ini, thanks.  

 

I'm using Win7x64 and with WIP10 from yesterday seems a little slower exiting tables (PinMame stays open longer).  Is this normal?   Not complaining just making sure my setup is working right.  I see some chatter with Blur and pausing PinMame in some other thread, maybe this has something to do with that?

 

Thanks guys, love this stuff more than anything :)

Share this post


Link to post
Share on other sites

Pausing makes problems only if you use Esc for exit and when you open menu game is paused.
If you use e you will have no problems.
pinmame stays open longer only on directb2s tables.

Share this post


Link to post
Share on other sites

As for settings.ini layout - it's best to use order that i have in fplaunch - you just copy lines from there and edit what you need to change.

I'm not sure if comments are aloud after value in settings - but will test it.

This order is most logical and easily readable for users.

 

By the way exitemulatorkey2 and exitemulatorkey3 keys are named that way cause on exitemulatorkey or pause key you would get only pause screen and you would exit with exitemulatorkey2 or exitemulatorkey3.

Now that keys are used for entering into submenus so names are: exitkey, exitkey1, enterkey, enterkey1

 

recomended order is:

exitScriptKey    = ~q & ~s  ; kill script key
; menu keys
exitKey          = e        ; invoke exit menu, can be joy button also (Joy1)
exitKey1         = p        ; former pauseKey, works same as exit key
enterKey         = 1        ; key for entering into menus
enterKey1        = Enter    ; and another one
upKey            = LShift   ; left flipper goes up in menus
upKey1           = LShift   ; another left flipper key - for joystick
downKey          = RShift   ; right flipper goes down in menus
downKey1         = RShift   ; another right flipper key - for joystick
; old settings
toggleCursorKey  = t
hideCursor       = true
hideDesktop      = true
hideTaskbar      = true
; new settings
useLoadingScreen = true     ; show loading slider
useExitScreen    = true     ; show exit321 countdown on long press
useExitAsPause   = true     ; open pause window on short press
useExitMenu      = true     ; use exit menu instead of pause window
fadespeed        = 25
pauseFPKey       = RButton  ; pause in FP
saveFPTables     = true     ; save fp table position on exit
editTableKey     = !F4      ; close table and go to vp/fp editor
printScreenKey   = o        ; save playfield
printBGKey       = u        ; save backglass
pfScreenNum      = 1        ; playfield Screen Number (used for print screen)
bgScreenNum      = 2        ; backglass Screen Number (used for print screen)
instructionsKey  = i
flyerKey         = f
hyperScale       = 0.75
debugMode        = file
ledwiz           = false
toggleLedwizKey  = 1
hyperpinexe      = hyperpin.exe
focusSleep       = 500

Share this post


Link to post
Share on other sites

Ok, When I put this new FPLAunch in place, and re-mapp my exit key to E in the Winpac utility... It will exit tables fine. But it will not exit Hyperpin.

 

From reading this thread, it sounds like it should write the below info to the settings.ini file when FPLaunch is run? Because my hyperspin settings.ini does not seem to get edited. And when I replace everything under [FPLaunch} with this info.. my tables stop working.

 

Nevermind.. found my own answer here...

http://www.hyperspin-fe.com/forum/showthread.php?10935-FPLaunch-MOD-Pause-and-Loading-screens&p=223456&viewfull=1#post223456

 

 

exitScriptKey    = ~q & ~s  ; kill script key
; menu keys
exitKey          = e        ; invoke exit menu, can be joy button also (Joy1)
exitKey1         = p        ; former pauseKey, works same as exit key
enterKey         = 1        ; key for entering into menus
enterKey1        = Enter    ; and another one
upKey            = LShift   ; left flipper goes up in menus
upKey1           = LShift   ; another left flipper key - for joystick
downKey          = RShift   ; right flipper goes down in menus
downKey1         = RShift   ; another right flipper key - for joystick
; old settings
toggleCursorKey  = t
hideCursor       = true
hideDesktop      = true
hideTaskbar      = true
; new settings
useLoadingScreen = true     ; show loading slider
useExitScreen    = true     ; show exit321 countdown on long press
useExitAsPause   = true     ; open pause window on short press
useExitMenu      = true     ; use exit menu instead of pause window
fadespeed        = 25
pauseFPKey       = RButton  ; pause in FP
saveFPTables     = true     ; save fp table position on exit
editTableKey     = !F4      ; close table and go to vp/fp editor
printScreenKey   = o        ; save playfield
printBGKey       = u        ; save backglass
pfScreenNum      = 1        ; playfield Screen Number (used for print screen)
bgScreenNum      = 2        ; backglass Screen Number (used for print screen)
instructionsKey  = i
flyerKey         = f
hyperScale       = 0.75
debugMode        = file
ledwiz           = false
toggleLedwizKey  = 1
hyperpinexe      = hyperpin.exe
focusSleep       = 500

Share this post


Link to post
Share on other sites

I have configured the dwjukebox and works very well with jukebox.bat in my pincab. But when I try to insert the table called jukebox, hyperpin responding "do not find jukebox.fpt table". Why?

 

Hyperpin Database XML VP:

 

<game name="jukebox">
<description>jukebox</description>
<manufacturer>dwjukebox</manufacturer>
<year>2013</year>
<type>SS</type>
</game>

 

Grazie!

Share this post


Link to post
Share on other sites

RESOLVED.

You simply delete the contents of the script in the new table in visual pinball.
Save as: jukebox.vpt
and everything works!
thanks

Share this post


Link to post
Share on other sites

This version caused my HyperPin to lose focus or lockup. So I had to go back to wip9 for the time being.

Share this post


Link to post
Share on other sites

Why is focus such an issue in Windows 7? Is it due to 2 screens displaying different things? My screen must flicker and fight 3-4 times before it finally settles on a screen, and it really does seem like the whole process pauses everything until it finally decides. In my mind, a table should be loading in the background, regardless of if it is in focus or not. (maybe that's just how the routines are written), but the point is, Win 7 sure does some odd things with these programs.

Share this post


Link to post
Share on other sites
RESOLVED.

You simply delete the contents of the script in the new table in visual pinball.

Save as: jukebox.vpt

and everything works!

thanks

Okay help me out here, where is the PinJukeLaunch folder supposed to be and where should the dwjukebox folder go. Also must we have ledblinky installed as well. When I load this from HP I'm getting can't find path errors ti ledblinky etc.

EDIT: Okay, edited the bat file and took out the blinky stuff and changed the path to DWJ but I can't exit out of it when in HP. Help...

Share this post


Link to post
Share on other sites

Are you have any issues in exiting the JB from HP, mine won't exit at all (HP mapped to e) and when I press esc on the keyboard HP goes focus crazy. 

Share this post


Link to post
Share on other sites

Last version of WIP 9 worked great.

 

Last version 10 causes focus issues. I am running win xp. Here are my settings for version 10.

 


[startup Program]
Executable          = C:\HyperPin\LEDSet.bat
Parameters          =
Working_Directory   =
WinState            = HIDDEN

[Exit Program]
Executable          = C:\HyperPin\LEDClear.bat
Parameters          =
Working_Directory   =
WinState            = HIDDEN

[FPLaunch]

exitScriptKey    = ~q & ~s

exitKey          = e        
exitKey1         = g        
enterKey         = 1        
enterKey1        = Enter    
upKey            = LShift  
upKey1           = LShift   
downKey          = RShift   
downKey1         = RShift   

toggleCursorKey  = t
hideCursor       = true
hideDesktop      = true
hideTaskbar      = true

useLoadingScreen = true    
useExitScreen    = true     
useExitAsPause   = true    
useExitMenu      = true     
fadespeed        = 25
pauseFPKey       = RButton
saveFPTables     = true   
editTableKey     = !F4     
printScreenKey   = o       
printBGKey       = u       
pfScreenNum      = 1        
bgScreenNum      = 2        
instructionsKey  = i
flyerKey         = f
hyperScale       = 0.75
debugMode        = false
ledwiz           = true
toggleLedwizKey  = 1
hyperpinexe      = hyperpin.exe
focusSleep       = 500

Share this post


Link to post
Share on other sites

Did you see post about debugging and tuning focus in this thread?

 

What happens when you exit - do you hear diagnostic sounds, are they fast or slow or you never hear two solenoid sounds?

Share this post


Link to post
Share on other sites
As for settings.ini layout - it's best to use order that i have in fplaunch - you just copy lines from there and edit what you need to change.

I'm not sure if comments are aloud after value in settings - but will test it.

This order is most logical and easily readable for users.

 

Tested and failed. I copied it all over and got an error when trying to launch a table citing the first "; Kill Script Key". 

 

I then deleted all the descriptions but left the ; menu, ; old settings etc and had many issues when trying to exit the table. In the end, I kept the order of things but deleted all the "; ______". All is fine again, phew. 

 

EDIT: Can we use # before a comment? I really like the comments. 

Share this post


Link to post
Share on other sites

yup - looks like comments don't work - they go into settings value - maybe i can remove them manually from the script when i'm loading settings

in the meanwhile - you can just move all comments to next line

Share this post


Link to post
Share on other sites

So Blur (sorry if this is the wrong thread to discuss this, but this is where you put your diag suggestions)


While I don't consider it a true issue, my screen does like what was posted in the video on the first page in Win7-64bit. Anything to make things snappier is always nice though right :D

 

I took some time to do some comparisons with WIP released prior to this batch with the diag stuff. What I'm finding is that  in Win7 with or without the focus scripts, nothing changes. Same flashes, same delays. I changed the focussleep from values of 100, 500, 1000, 2000, and notice no real change. I tried removing the "break" and saw no real change. The delays are really seen in both starting and exiting tables, however much more noticeable in FP as it flashes alot.

 

The diag clicks are helpful though. This is what I see:

 

In VP:

On table exit: Hyperpin screen immediately comes up for an instant, then goes black

3-4 second delay

Click

3-4 second delay

Click - Hyperpin comes into focus again

 

In FP:

On table exit: Hyperpin screen immediately comes up for an instant, then goes black

6-7 Second Delay (flashes)

2 clicks back to back as Hyperpin comes into focus

 

Is there a way to force Hyperpin to stay on top even if the emulators have not fully exited? They shoudl be doing all that in the background, and it seems like Win7 is trying to force them front until they are done. (just throwing out ideas here)

Share this post


Link to post
Share on other sites

i can try to push winclose in background or in another thread and then continue with activation of hyperpin, and see if this will improve closing times

Share this post


Link to post
Share on other sites

If you could that would be great, starting to wonder why I'm even using Win7.  About one out of every 10 or so table exits HP crashes. All the clicks seem normal and it makes it to the wheel screen but it locks up. 

Share this post


Link to post
Share on other sites

Jason, that's odd...I have 0 issues with crashing tables, everything works great actually. I actually dont even consider the "blacking focus" thing to be an issue, just noticed I wasn't only person who had it and saw others who's screens were much faster at changing from one program to another.

 

Are you sure you aren't having heat issues?

Share this post


Link to post
Share on other sites

No heat issue that's for sure, could be something else though. I'm always crossing my fingers when closing a table, it just doesn't seem right. I don't have any odd settings either, actually they are identical to what blur posted some posts back. Maybe a memory thing, or processing thing, idunno. On XP it was solid, never had an issue at all, but Win7, oh my. 

Share this post


Link to post
Share on other sites

damn, I cant get WIP 10 to work with my win xp 32 bit rig. while all versions of WIP 9 worked fine. I guess its something with the new focus routine?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...