5 replies to this topic

[anarkizt]

I have spent all day trying to get the plunger in my newly built cab to work with Pinball FX3. It works in VPX and I also managed to make it work using x360ce but that caused a problem where I were unable to launch the ball many times. It was like the window lost focus. I guess weird things might be happening when the other buttons of the 360 controller is not emulated in any way...?

 

Anyway, this is what I am using:

 

Pinscape (KL25Z board)

Doflinx 6.84

Direct Output Framework 3

Pinball FX3 through Steam

 

Things I have gotten to work: NUDGE! Is working pretty good.

In debug mode and Joystick Test I can see the values changing, but changing the ini file does nothing...

 

This is my doflinx.ini

 

#########################

DEBUG=1

DIRECTOUTPUTCONFIG=c:\DirectOutput\config\directoutputconfig.ini

PROCESSES=Pinball FX3

 

# Set the joystick settings for nudge with Pinscape and FX3

JOY_PORT=1

JOY_X_OFFSET=32767

JOY_Y_OFFSET=32767

FX_LEFT_NUDGE_POINT=-2500

FX_RIGHT_NUDGE_POINT=2500

FX_FORWARD_NUDGE_POINT=2500

FX_LEFT_NUDGE_KEY=4C

FX_RIGHT_NUDGE_KEY=52

FX_FORWARD_NUDGE_KEY=20

FX_LEFT_NUDGE_INPUT=A2

FX_RIGHT_NUDGE_INPUT=A3

 

# Configure the analogue plunger, such a Pinscape Z axis, to work with FX3

PLUNGER_AXIS=Z

PLUNGER_JOYSTICK_NUMBER=1

PLUNGER_KEY=0D

PLUNGER_PULL_POINT=60000

PLUNGER_RELEASE_POINT=35000

 

####################

 

What strikes me as a but weird is that when pulling the plunger inside a table in FX3 will Doflinx prints "Key sent for PLUNGER" in the debug window. And nothing else. As opposed to pressing the launch button (and holding it) generates a "No trigger response for LAUNCHBALL were found"... I am not entirely sure these are related of course...

 

The joystick shows up in windows device manager and I can see it working there as well through the Z-axis test bar. 

 

What am I missing? 

Edited by anarkizt, 24 August 2019 - 09:00 PM.

[DDH69]

The fact that you are seeing "Key sent for PLUNGER" is good.  This, as expected means the sending of the PLUNGER_KEY is occurring, so your setting are most likely all correct.  I don't know what's wrong, but a few thoughts / questions;

 

1. Is your launch key in FX3 set to <ENTER> ?  (obvious I know, but I've done it!)
2. I wonder if having DOFLinx in DEBUG=1 is stealing focus, the key is set to the keyboard queue, the in focus application will collect that key.  You can put DOFLInx in DEBUG=2, same level of debugging but the window is hidden.  Perhaps try that and pull the plunger a couple of times when ready to launch and collect the DEBUG.LOG then share it.
3. Before sharing the DEBUG.LOG though, do a "Show Variables" so that they all get in there as well.

[anarkizt]

Ah, it wasn't set to <ENTER> of course, now I feel stupid! It's working. Thank you so much DDH69! 

 

Of course, this sparked another question... Using the x360ce-application to translate Dinput to Xinput I was able to get pretty much 1:1 movement with the physical plunger and the in game animation. So is not the case here. This was more of a "do the whole movement", wait a while, see the plunger animation. I wasn't able to affect the strength of the launch so to speak. Is it possible to achieve that 1:1 lag-free sensation using DOFlinx? Changing the PULL/RELEASE values only seemed to decide when the event is sent to FX3. I guess a whole bunch of events would have to be sent for it to work the way I'm describing? 

Edited by anarkizt, 25 August 2019 - 02:33 AM.

[DDH69]

Its a good question, and one I plan to look at over the coming weeks.  It was only Friday that I got my analogue plunger installed into my cabinet.  I now have a potentiometer for my plunger on a PinScape.

 

At present the analogue plunger routine in DOFLinx  is purely sending a press of the defined key (usually <ENTER> ) when the thresholds are passed.  The next possibility is to press the key at one point and release at the other.

[anarkizt]

I see, then I wish you good luck. Thanks!

[DDH69]

Just to wrap this one up, the plunger changes are all done in V7.0 which is now available.