53 replies to this topic

[DDH69]

@Slydog43, tell me more of what you're looking to achieve .......

 

I recall looking at something gamepad related many moons ago from a TerryRed idea.

[Slydog43]

I'm looking to run doflinx off of gamepad buttons instead of keyboard buttons.  In the ini file there is

 

# The keyboard hex code for the key that is used for each flipper from https://msdn.microso...1(v=vs.85).aspx

 

but I can only get these if I also run something like joy2key to emulate keystrokes.  It would be cleaner to interpret the actual gamepad buttons directly

[DDH69]

 

I'm looking to run doflinx off of gamepad buttons instead of keyboard buttons.  In the ini file there is

 

# The keyboard hex code for the key that is used for each flipper from https://msdn.microso...1(v=vs.85).aspx

 

but I can only get these if I also run something like joy2key to emulate keystrokes.  It would be cleaner to interpret the actual gamepad buttons directly

 

 

Well why not!  I've setup a new thread here so that we can get into the depths of it as my attempts start.  The first step will be educating me about the controllers themselves!

[GInsonic]

I just tested 5.01a and the focus issues are still there (of course they are, there is nothing mentioned in the changelog   )

I now tested different configurations and it seems, that DOFLinx takes the focus during startup process even when b2s options are not enabled. PBFX2 then interrupts gameplay and you have to press Escape as mentioned above (seemless window mode).

When starting DOFLinx a few seconds before starting PBFX2, it seems that it has finished some internal processing and PBFX2 remains in the gameplay. When I set the new delay parameter, the interruption happens after the chosen delay time.

It did not happen before introducing the new b2s functionality, so would it be possible to disable these code parts completely using a new parameter (e.g. ENABLE_B2S=1) ?

 

Or am I the only one who suffers from the interruption disease   ?

[DDH69]

@Ginsonic, No B2S actions occur unless you have a XXX.directB2s file in the correct path and where XXX is the same name as the FX2 file for DOFLinx.  So, no file, no B2S actions, no need for a disabling parameter.

 

Just to be clear, are you starting / stopping DOFLinx from your front end as "Launch Before" / "Launch After" commands?  What delay parameter are you referring to, there are no new ones.  Are you referring to PROCESS_TO_ACTIVE_TIME= ?  If so this has not been changed.  I have suggested people with focus issues when using B2S may want to change it down to 1.  The default was, and remains 2000.

 

Presuming you re talking about manipulating PROCESS_TO_ACTIVE_TIME= its interesting that you say your issue happens after that time expires.  Have you ramped it way out, like to say 180000 (3 minutes) to see what happens - not suggesting leaving it there.  Have you tried swapping back to DOFLInx 4.3 EXE and changing nothing else to see if the issue goes away again?

 

I've looked through the startup sections of code this morning with your symptoms in mind, I can't see anything that would impact this.  As always I discount nothing, perhaps you can post a LOG, it might job some other thoughts loose.

 

..... we'll find the issue.

[GInsonic]

Thanks DDH69 for your answer ! Well I continued testing and I think, I now have the explanations.

 

First, the "issue" has nothing to do with version 5 or b2s functionality, it was already there in v4, but It did not matter there.

 

Explanation:

 

During startup DOFLinx somehow "steals" the focus from PBFX2 for a short time, THIS is, what interrupts the gameplay.

When using DOFLInx version 4, I started PBFX2 in full screen mode (because the b2s functionality was not there yet), and in full screen mode DOFLinx is not able to steal the focus.

 

Now in seamless window mode (to prevent PBFX2 hiding when using backglasses), the startup of DOFLinx is able to steal the focus and so to interrupt the gameplay.

 

I can easily live with that, I only have to start DOFLinx some second before starting PBFX2 (e.g. together with PinballX) and keep leaving it running in the background.

When it has finished its startup process, it dows no longer interrupt PBFX2, regardless if a b2s is activated or not.

 

Sorry for some previous false alerts regarding PROCESS_TO_ACTIVE_TIME parameter !

Edited by GInsonic, 18 July 2017 - 06:14 AM.

[DDH69]

Can you move to the state of just leaving DOFLinx running, ie startup with Windows?

 

I will research more about the focus issue, DOFLinx certainly never puts itself in focus purposefully, but there may be some default application behaviour under windows that I can suppress - not sure.

[GInsonic]

Can you move to the state of just leaving DOFLinx running, ie startup with Windows?

 

I will research more about the focus issue, DOFLinx certainly never puts itself in focus purposefully, but there may be some default application behaviour under windows that I can suppress - not sure.

Yes, of course ! I will start it together with PinballX, the delay is long enough for DOFLinx to settle down then.

And you are right, it does not really steal the focus, it only lets PBFX2 "think" somewhow, that it should interrupt...

Please tell me, if I can help !

[DDH69]

From the reading I've done so far it seems that despite the form never being forced with focus, that a default setting in Visual Studio may make a form take focus at startup.  This would have been the DOFLinx behaviour since the very beginning.  I'll have to read more about this setting, as it seems to affect A LOT of default application startup behaviour.

 

Given that I don't have the issue testing is more difficult on this one.  If you want I can compile a version of 5.0 (I didn't save a specific 5.01 source) with the setting turned off and you can try it out.  I have no idea of the resultant behaviour.  I did turn the setting off and compile then run 5.10 and I couldn't see anything obviously wrong.  Let me know.  If you're keen I'll PM a link to a test version, especially since you have a perfect test bed at present.

[GInsonic]

Great, Yes, please send me a PM, I will be able to test it soon !

[Baronir2d2]

Ok, now working fine for Pinball FX2 and FP.

I updated the .NET

 

But I'm not able to make DOF work with VP ....

I will open a topic about it now, if you can help me I would be very happy.

[DDH69]

@Baronir2d2, thanks for the update.  Always great to hear about positive progress.

 

I'll keep an eye out for your new topic and help where I can.

[kiwiBri]

Right. I have updated my cab to VPX 10.3.1 and VPinMame 2.9 with a Pinscape board + expansion boards (Main & power) .  First install of this going to happen tonight. I assume there is a install guide etc included in the notes?  Hopefully its a one click to install and just works ;-)

[DDH69]

Plenty of information in the guide.

 

http://www.vpforums....showtopic=36184 This thread might help as well for more of a run through the setup.

[kiwiBri]

Plenty of information in the guide.

 

http://www.vpforums....showtopic=36184 This thread might help as well for more of a run through the setup.

 

 

Ah! thanks..  Just read it. So, it helps to have Future Pinball installed? I only have VPX and FX2 installed and working.. 

[DDH69]

Sorry,  I misread.  No there is no advantage to the installation to have FP installed if you don't want it.  VPX and FX2 do not require FP.  Somehow my eyes saw FP in your question, which on reflection it clearly is not

[coreduo0099]

From the reading I've done so far it seems that despite the form never being forced with focus, that a default setting in Visual Studio may make a form take focus at startup.  This would have been the DOFLinx behaviour since the very beginning.  I'll have to read more about this setting, as it seems to affect A LOT of default application startup behaviour.

 

Given that I don't have the issue testing is more difficult on this one.  If you want I can compile a version of 5.0 (I didn't save a specific 5.01 source) with the setting turned off and you can try it out.  I have no idea of the resultant behaviour.  I did turn the setting off and compile then run 5.10 and I couldn't see anything obviously wrong.  Let me know.  If you're keen I'll PM a link to a test version, especially since you have a perfect test bed at present.

 

After spending well over 10 hours on this stealing focus (which hangs up my table pretty good) I found this thread.  I think i have the same thing going on.  What's interesting is if I start fresh and try say Portal, on first launch everything is good.  on subsequent launches, that's when FX2 locks up.  I run with DOFLinx running at startup and have tried PROCESS_TO_ACTIVE_TIME=1, 2000, 10000, 30000.  The issue is definately a conflict when both the FX2 DBS and FX2 run together.  

 

BTW, my rig is a dual LetWiz setup and all force feedback/lights work great on first launch.

I eliminated pinballX and still get it with command line cycles of the following with all debug looking perfectly fine:

 

E:\Emulator\Pinball emu\Pinball FX2>"E:\Emulator\Pinball emu\DirectOutput\DOFLinxMsg.exe" GAME_NAME=Portal

E:\Emulator\Pinball emu\Pinball FX2>"Pinball FX2.exe" Portal

E:\Emulator\Pinball emu\Pinball FX2>"E:\Emulator\Pinball emu\DirectOutput\DOFLinxmsg.exe" "KILL=Pinball FX2"#GAME_NAME=

 

I was hoping an auto hot key script might help so tried that to change focus, but no luck, which makes sense since I cant Alt-Tab to switch once things lock up.  (lock up meaning I cant switch to Pinball FX2 and it wont run on the rare case I can switch to it)

 

If I remove the B2S path, not backglass loads and FX2 plays fine.

 

If there is an alternate build, I'd like to try it too.

 

Also, I'd 2nd the notion of disabling the b2s feature.  I understand by removing the b2s directory reference it won't load/start, but I used to launch FX2 and be able to see my pinball x backglass videos in place of a b2s.  Now the screen goes black and my pinball x is still set to not hid backglass when testing this out. 

 

One last item. there is an error in the guide for v5.  it refers to:  PATH_FX2_BG=The path to the directb2s files for FX2 games.    This should be PATH_FX2_B2S=

 

Thanks for the awesome work.  Happy to help any way I can.

One other observation.. I have an older FX2 build from January and have not updated (nor want to at this point).  Not sure if table names have changed since then, but here is my observation...

 

My table for American Dad! Pinball is: AmericanDad.pxp

My backglass is: AmericanDadPinball.directb2s

 

If I launch with the following, I get no flashing lights on backglass, but do get force feedback:

E:\Emulator\Pinball emu\Pinball FX2>"E:\Emulator\Pinball emu\DirectOutput\DOFLinxMsg.exe" GAME_NAME=AmericanDad

E:\Emulator\Pinball emu\Pinball FX2>"Pinball FX2.exe" AmericanDad

 

If I launch with the following, I get flashing lights on backglass and get force feedback as expected:

E:\Emulator\Pinball emu\Pinball FX2>"E:\Emulator\Pinball emu\DirectOutput\DOFLinxMsg.exe" GAME_NAME=AmericanDadPinball

E:\Emulator\Pinball emu\Pinball FX2>"Pinball FX2.exe" AmericanDad

 

I tried re-naming and editing the xml of the directb2s files but could never get it to work with the GAME_NAME=AmericanDad, which matches the table name.

 

This happens with all backglasses ending in 'Pinball'

 

Did FX2 change the pxp names to now end in Pinball on these tables, or is there a mis-match?

 

This all resulted me in changing my pinballX to use [Description] instead of [Filename] and tweaking my pinball x descriptions, but the focus issue a few posts up ^^^ i'm experiencing made it all moot anyways...

 

[DDH69]

@coreduo0099 to address your points

 

PATH_FX2_BG=  My bad, this was the working name and I left it in the guide.  Thanks for pointing this out, I've fixed it up and I'm sure you'll save someone confusion later.

 

If DOFLinx can not find the matching B2S file (ie removing the path) then no activity for B2S takes place, it is completely disabled.  DOFLinx is not doing anything to disable your backglass videos, the blank back box screen could be the PinballX setting to hide backglass (although you say this is not set), or Pinball FX2 having the cabinet option set for backglass image but not finding one.  These are the only two ways I'm aware of achieving this result.

 

There is no alternate version as removing the ability for DOFLinx to find a B2S file completely disables the functionality.

 

As per the posts here, and I think one other thread, focus with Pinball FX2 has been an issue.  I too have a two LEDWiz on WIndows 10, and have no problems at all.  I've spent a lot of time looking at the focus issue around FX2 and can't figure out how to change the behaviour of FX2.  So ultimately, if with your setup and FX2 your focus issues are so pronounced, I don't have anything more I can offer.

 

I had the older build of FX2 but do not recall table name changes.  Its always been AmericanDadPinball to me.  I'm not sure if the FX2 version and table names are directly linked.  Either way, the FX2 file and B2S file names are simply the Game Name reported by DOFLinx.  This will be in your log file regardless of the DEBUG= setting if you have OUTPUT_GAME_NAME=1

[coreduo0099]

Thanks.

 

I did a bunch of experimenting and have it working 80-90% now without focus change hanging things up and the proper game/backglass loading properly and indicating so in the debug.

 

The video turning off turns out to be a pinball X Setting.  If you have the preference "Use DirectB2S in Front End" set as Yes, videos play.  If No, they are aborted.  (Regardless of DOFLinx).   I had tuned it off a few weeks ago to speed up pinballX, never imagining it would impact FX2 videos playing in the background.

 

My settings:

PinBallX.ini (relevant section)

[PinballFX2]
Enabled=True
WorkingPath=E:\Emulator\Pinball emu\Pinball FX2
Executable=Pinball FX2.exe
Parameters="[TABLEFILE]"
Process=Pinball FX2.exe
WaitFor=-1
LaunchBeforeEnabled=True
LaunchBeforeWorkingPath=E:\Emulator\Pinball emu\DirectOutput
LaunchBeforeExecutable=DOFLinxMsg.exe
LaunchBeforeParameters=GAME_NAME="[DESCRIPTION]"
LaunchBeforeWaitForExit=False
LaunchBeforeHideWindow=True
LaunchAfterEnabled=True
LaunchAfterWorkingPath=E:\Emulator\Pinball emu\DirectOutput
LaunchAfterExecutable=DOFLinxMsg.exe
LaunchAfterParameters="KILL=Pinball FX2"#GAME_NAME=
LaunchAfterWaitForExit=False
LaunchAfterHideWindow=False

where [Description] is the name of the backglass files in my PinballX Games List Manager

 

 

and in DofLinx.ini:

PROCESS_TO_ACTIVE_TIME=12000

(it seems to work better loading right after table load)

 

At one point it seemed to be related to the video length and the "Use DirectB2S in Front End" setting, but I'm no longer convinced.  I'll post back if I can improve things...

[DDH69]

Nice to see someone using the KILL= option.  I was only wondering the other day if that was actually getting used, or if it had slipped past everyone

 

Let me know if you notice anything around the KILL=.  I use it myself.  Its a "soft" kill at present, ie it sends a terminate message to the process.  You can "hard" kill a process where you close it regardless of its desire.  This is what many other options do, but I decided to start slow and see how it performed.  So far for me its cleaned up the occasional rouge Pinball FX2 process every time.