44 replies to this topic

[DDH69]

So I'm currently back working on something I started ages ago.  That is getting the accelerometer nudge from the Pinscape that comes in as joystick input, to trigger left, right and forward nudge in FX3.  When I tried this ages ago I got stuck sending the key strokes to FX3, but now that is working.  Well almost, it seems you just can't get L-CTRL and R-CTRL to simulate into FX3.  I can get this into all other test applications and Notepad, etc, but not FX3.  Not to fear, there is a way around this by setting FX3 nudge keys to something else, I've been using L and R.

 

Anyway, I should have something ready for testing soon if anyone has a Pinscape and likes to use FX3.

 

Thanks to Tom Speirs (PinballX) for some valuable words of advice on getting simulated key presses working with FX3.

[Rappelbox]

Cool!
I’d like to help you out. Will be in the office again from Thursday/Friday.

I know there’s the workaround with x360ce to get analogue nudge work with fx3. I already tested it with Ioannis Giavridis some time ago but I suspect you want an doflinx integrated concept?

Greets,
Dom

[TerryRed]

I find that getting keystrokes to register with FX3, is hit and miss, as FX3 is picky with what controller it allows to register. When you have more than one "controller" seen it can get worse. (I jhad two x360 gamepads in the cab before)

 

Using Pinnacle Game Profiler...usually works, but sometimes if you are not completely in focus with FX3, gamepad controls will still work, but not keys. That being said, I have my D-Pad left / Right as my nudge "buttons" which always work.

 

Getting native accelerometer support with FX3 would be neat if possible...but for analogue axis with nudge, FX3 only seems to recognize X-input devices (x360, xone). Using x360ce is currently the only methos that seems to work, though it can be tricky to setup.

[DDH69]

The process I'm working on is to emulate the left, right and forward nudge keys when the Pinscape accelerometer causes the joystick to go past a set threshold.  Given that it needs to use keys, ie nudged or not nudged, its not proportional like proper joystick intensity is in VP.

 

It might not be for everybody, but I do like the idea of putting the hip into the cabinet and getting FX3 to nudge.  Much more fun than pressing a button, of coarse its also a bit more imprecise!

[TerryRed]

Some people swear by having only nudge from something like pinscape instead of buttons. My problem is my cab is just too damn heavy to make it fun to nudge.

 

What you are trying to do is the kind of thing I would have done with PGP. Simply using the pinscape nudge axis to set off a key once it reaches over a certain threshold.

[DDH69]

Well testing has gone well today.  I've been slamming the hip into my cabinet and getting lots of nudge (and some tilt) into FX3.  As TerryRed said, it might not be for everybody, but then you can choose to truly nudge or use keys.  I'll do a new release with this in it soon.

 

TerryRed, you need to either loosen the legs on your cabinet or just beef up a bit 

[kiwiBri]

The process I'm working on is to emulate the left, right and forward nudge keys when the Pinscape accelerometer causes the joystick to go past a set threshold.  Given that it needs to use keys, ie nudged or not nudged, its not proportional like proper joystick intensity is in VP.

 

It might not be for everybody, but I do like the idea of putting the hip into the cabinet and getting FX3 to nudge.  Much more fun than pressing a button, of coarse its also a bit more imprecise!

 

Just catching up on things (been away for months) and just found this thread!  Awesome!

I just installed FX3 on my machine which has a Pinscape installed. I *FINALLY* installed DOFLinx last night and the one table in FX3 seems to be working..  (though my 2 addressable strips - Playfield R and Playfield L ) don't fire.. ?  
 

I hope you are able to release something that works reasonably well for nudge !

Edited by kiwiBri, 10 September 2018 - 04:29 PM.

[DDH69]

 

I hope you are apple to release something that works reasonably well for nudge !

 

 

It is now released.  Just grab the latest DOFLinx package.

[kiwiBri]

 

 

I hope you are able to release something that works reasonably well for nudge !

 

 

It is now released.  Just grab the latest DOFLinx package.

 

 

I reviewed my install.. I actually had installed v6.40 ..  so I went through the setup again using the Guide document and the instructions on the DOFLinx download page along with the content of your DOFLink_INI file example.  I set JOYSTICK PORT = 1 and started DOFLINX in Debug mode  (I really like this.. I was able to test all my DOF outputs including addressable LEDs etc using the tools in there) .  When I selected the Test Joystick option,  I 'm not getting readings from the Pinscape  accelerometer..  but when I test it in the Pinscape tool, it works fine, as it does in VPX. 

 

The good news is that DOFLINX seems to otherwise work well in the one table I have for FX3   - yay!     

[DDH69]

Good to hear things are running well.

 

Make sure you have JOY_PORT not JOYSTICK_PORT.  I've pasted the relevant section of my INI below.

 

Do you know what joystick port Windows is seeing the Pinscape as?  Is it 1 or 2?  If you don't make suitable progress then post your DOFLinx.INI here and I will take a look.

 

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

[kiwiBri]

thanks - I Will look into this tonight. Was busy with PuP installation and testing. 

[jthompson]

....... you need to either loosen the legs on your cabinet or just beef up a bit 

 

LOL, I know you were kind of joking but I actually might try this a bit to see if it helps on my cabinet. I didn't realize you had nudge working too. I might try it out tonight. Is this a feature in FP too? 

[svesch]

I would also be interested how digtal nudging works in detail for FP!

[Tempest43528]

@DDH69 - I am seeing the same thing as KiwiBri.     I have the KL25Z w/ Pinscape working in VPX but I am not seeing any nudge in DofLink.    I copied the nudge settings into my DofLinx.ini  and confirmed that FX3 is set to

nudge using L.R,  and Space.

 

If I go to the debug Window and click Test Joy I got:         Should I see move the board?

 

 

When I get offset they went to:

 

 

 

Here is my DofLinx.ini

 

JOY_PORT=1

JOY_X_OFFSET=0

JOY_Y_OFFSET=0

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

 

 

Output from Log file.   If I press L,Right, space on keyboard Doflinx is definately seeing it.

 

06-Dec-18 14:29:48.695 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

06-Dec-18 14:29:48.719 - Starting up - version 6.52

06-Dec-18 14:29:48.723 - For support come and visit the community here http://www.vpforums....p?showforum=104

06-Dec-18 14:29:48.734 - Pre-Reading DOFLinx.INI startup config file details

06-Dec-18 14:29:48.866 - No DOF Global Config file supplied

06-Dec-18 14:29:48.928 - 1 Pinscape device(s) found

06-Dec-18 14:29:48.939 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller

06-Dec-18 14:29:48.965 - DOFLinx device:1 Pinscape setup with 22 outputs

06-Dec-18 14:29:48.991 - 1 LEDWiz device(s) found

06-Dec-18 14:29:48.996 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=0

06-Dec-18 14:29:49.012 - DOFLinx device:2 LEDWiz setup with 32 outputs

06-Dec-18 14:29:49.020 - 0 FTDI (Sainsmart) device(s) found

06-Dec-18 14:29:49.030 - 0 Ultimate IO device(s) found

06-Dec-18 14:29:49.039 - Reading DOFLinx.INI startup config file details

06-Dec-18 14:29:49.049 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini

06-Dec-18 14:29:50.222 - Found valid process name of 'Pinball FX3'

06-Dec-18 14:29:50.229 - Setting FX3 process ID to :8636

06-Dec-18 14:29:50.254 - Activated by process name : 'Pinball FX3'

06-Dec-18 14:29:50.263 - Named process detected and startup commenced

06-Dec-18 14:29:50.270 - Process has administration rights

06-Dec-18 14:29:50.877 - FX3 EXE name=C:\Program Files (x86)\Steam\steamapps\common\Pinball FX3\Pinball FX3.exe Size=18085008 bytes, Dated 12/6/2018 1:40:47 PM

06-Dec-18 14:29:50.883 - Applying memory offsets for FX3 version circa 04/12/18

06-Dec-18 14:29:50.899 - FX3 full link active

06-Dec-18 14:29:50.908 - Using full colour palette

06-Dec-18 14:29:50.914 - 122 colours added to the palette

06-Dec-18 14:29:50.932 - 1 Pinscape device(s) found

06-Dec-18 14:29:50.940 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller

06-Dec-18 14:29:50.947 - DOFLinx device:1 Pinscape setup with 22 outputs

06-Dec-18 14:29:50.954 - 1 LEDWiz device(s) found

06-Dec-18 14:29:50.963 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=0

06-Dec-18 14:29:50.977 - DOFLinx device:2 LEDWiz setup with 32 outputs

06-Dec-18 14:29:50.992 - 0 FTDI (Sainsmart) device(s) found

06-Dec-18 14:29:51.007 - 0 Ultimate IO device(s) found

06-Dec-18 14:29:51.938 - Loading FX3 configuration file C:\DirectOutput\FX3\ALL.FX3

06-Dec-18 14:29:51.963 - Loading FX3 configuration file C:\DirectOutput\FX3\BallyPartyZone.FX3

06-Dec-18 14:29:51.974 - No DOF Global Config file supplied

06-Dec-18 14:29:52.013 - B2S file not found : BallyPartyZone

06-Dec-18 14:29:52.035 - Using full colour palette

06-Dec-18 14:29:52.048 - 122 colours added to the palette

06-Dec-18 14:29:52.061 - Cabinet Mode = 0   Backglass Mode = 0

06-Dec-18 14:29:58.827 - GAMEMODE mode=1 action #0 of 'FF_COLOUR,BLACK,RGB_DF,0'

06-Dec-18 14:29:58.843 - GAMEMODE mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_FL,6,750,100,RANDOM'

06-Dec-18 14:29:58.894 - GAMEMODE mode=1 action #2 of 'FF_FLASHER,DV_FLOR,FL_FL,6,750,100,RANDOM'

06-Dec-18 14:29:58.936 - GAMEMODE mode=1 action #3 of 'FF_FLASHER,DV_FLIL,FL_FL,6,750,100,RANDOM'

06-Dec-18 14:29:58.945 - GAMEMODE mode=1 action #4 of 'FF_FLASHER,DV_FLIR,FL_FL,6,750,100,RANDOM'

06-Dec-18 14:29:58.986 - GAMEMODE mode=1 action #5 of 'FF_FLASHER,DV_FLCN,FL_FL,6,750,100,RANDOM'

06-Dec-18 14:29:58.996 - GAMEMODE mode=1 action #6 of 'FF_DOF,E424,-1'

06-Dec-18 14:30:00.335 - NOSE_GLASSES mode=1 action #0 of 'FF_DOF,E418,-1'

06-Dec-18 14:30:00.347 - CPT_BIZARRE mode=1 action #0 of 'FF_DOF,E419,-1'

06-Dec-18 14:30:00.358 - BALLIN_SENSOR mode=1 action #0 of 'FF_DEV,DV_MC,-1'

06-Dec-18 14:30:00.404 - BALLIN_SENSOR mode=1 action #1 of 'FF_DOF,E311,-1'

06-Dec-18 14:30:00.412 - SENSOR_76_TROUGH_1 mode=1 action #0 of 'FF_FLASHER,DV_FLIR,FL_TT,1,200,100,YELLOW'

06-Dec-18 14:30:00.443 - SENSOR_76_TROUGH_1 mode=1 action #1 of 'FF_DOF,E413,-1'

06-Dec-18 14:30:00.484 - SENSOR_76_TROUGH_1 mode=1 action #2 of 'FF_B2S,B2SSTARTANIMATION,MONSTER4'

06-Dec-18 14:30:00.494 - SENSOR_77_TROUGH_2 mode=1 action #0 of 'FF_DOF,E416,-1'

06-Dec-18 14:30:00.529 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'

06-Dec-18 14:30:00.570 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'

06-Dec-18 14:30:04.516 - NUDGERIGHT mode=1 action #0 of 'FF_DEV,DV_SH,10000'

06-Dec-18 14:30:04.654 - NUDGERIGHT mode=1 action #5 of 'FF_B2S,B2SSTARTANIMATION,BALLY'

06-Dec-18 14:30:04.667 - There are no OFF actions for SENSOR_76_TROUGH_1

06-Dec-18 14:30:04.959 - There are no OFF actions for SENSOR_78_TROUGH_3

06-Dec-18 14:30:05.100 - NUDGERIGHT mode=1 action #0 of 'FF_DEV,DV_SH,10000'

06-Dec-18 14:30:06.003 - NUDGERIGHT mode=1 action #1 of 'FF_COLOUR,RED,RGB_TT,1500'

06-Dec-18 14:30:06.036 - NUDGERIGHT mode=1 action #2 of 'FF_FLASHER,DV_FLOR,FL_ON,1,1,100,RED'

06-Dec-18 14:30:06.044 - NUDGERIGHT mode=1 action #3 of 'FF_FLASHER,DV_FLIR,FL_ON,1,1,100,RED'

06-Dec-18 14:30:06.079 - NUDGERIGHT mode=1 action #4 of 'FF_DOF,E404,-1'

06-Dec-18 14:30:06.122 - NUDGERIGHT mode=1 action #5 of 'FF_B2S,B2SSTARTANIMATION,BALLY'

06-Dec-18 14:30:06.174 - There are no OFF actions for SENSOR_76_TROUGH_1

06-Dec-18 14:30:06.187 - SENSOR_77_TROUGH_2 mode=1 action #0 of 'FF_DOF,E416,-1'

06-Dec-18 14:30:06.208 - SENSOR_78_TROUGH_3 mode=1 action #0 of 'FF_FLASHER,DV_FLIL,FL_TT,1,200,100,YELLOW'

06-Dec-18 14:30:06.246 - SENSOR_78_TROUGH_3 mode=1 action #1 of 'FF_DOF,E411,-1'

06-Dec-18 14:30:06.279 - SENSOR_78_TROUGH_3 mode=1 action #2 of 'FF_B2S,B2SSTARTANIMATION,SHIP'

06-Dec-18 14:30:06.321 - NUDGERIGHT mode=2 action #0 of 'FF_DEV,DV_SH,250'

06-Dec-18 14:30:06.334 - NUDGERIGHT mode=2 action #1 of 'FF_FLASHER,DV_FLOR,FL_OFF,1,1,100,RED'

06-Dec-18 14:30:06.364 - NUDGERIGHT mode=2 action #2 of 'FF_FLASHER,DV_FLIR,FL_OFF,1,1,100,RED'

06-Dec-18 14:30:06.484 - SENSOR_76_TROUGH_1 mode=1 action #0 of 'FF_FLASHER,DV_FLIR,FL_TT,1,200,100,YELLOW'

06-Dec-18 14:30:06.575 - There are no OFF actions for SENSOR_78_TROUGH_3

06-Dec-18 14:30:07.331 - NUDGELEFT mode=1 action #0 of 'FF_DEV,DV_SH,10000'

06-Dec-18 14:30:07.340 - NUDGELEFT mode=1 action #1 of 'FF_COLOUR,RED,RGB_TT,1500'

06-Dec-18 14:30:07.370 - NUDGELEFT mode=1 action #2 of 'FF_FLASHER,DV_FLOL,FL_ON,1,1,100,RED'

06-Dec-18 14:30:07.378 - NUDGELEFT mode=1 action #3 of 'FF_FLASHER,DV_FLIL,FL_ON,1,1,100,RED'

06-Dec-18 14:30:07.418 - NUDGELEFT mode=1 action #4 of 'FF_DOF,E403,-1'

06-Dec-18 14:30:07.499 - NUDGELEFT mode=1 action #5 of 'FF_B2S,B2SSTARTANIMATION,BALLY'

06-Dec-18 14:30:07.546 - SENSOR_77_TROUGH_2 mode=1 action #0 of 'FF_DOF,E416,-1'

06-Dec-18 14:30:08.341 - NUDGELEFT mode=2 action #0 of 'FF_DEV,DV_SH,250'

06-Dec-18 14:30:08.368 - NUDGELEFT mode=2 action #1 of 'FF_FLASHER,DV_FLOL,FL_OFF,1,1,100,RED'

06-Dec-18 14:30:08.376 - NUDGELEFT mode=2 action #2 of 'FF_FLASHER,DV_FLIL,FL_OFF,1,1,100,RED'

06-Dec-18 14:30:08.416 - SENSOR_77_TROUGH_2 mode=1 action #0 of 'FF_DOF,E416,-1'

06-Dec-18 14:30:08.488 - SENSOR_77_TROUGH_2 mode=1 action #0 of 'FF_DOF,E416,-1'

06-Dec-18 14:30:15.522 - NUDGEFORWARD mode=1 action #1 of 'FF_COLOUR,RED,RGB_TT,1500'

06-Dec-18 14:30:15.560 - NUDGEFORWARD mode=1 action #2 of 'FF_FLASHER,DV_FLCN,FL_ON,1,1,100,RED'

06-Dec-18 14:30:15.569 - NUDGEFORWARD mode=1 action #3 of 'FF_DOF,E405,-1'

06-Dec-18 14:30:15.598 - NUDGEFORWARD mode=1 action #4 of 'FF_B2S,B2SSTARTANIMATION,BALLY'

06-Dec-18 14:30:15.675 - There are no OFF actions for BALLIN_SENSOR

06-Dec-18 14:30:15.684 - SENSOR_77_TROUGH_2 mode=1 action #0 of 'FF_DOF,E416,-1'

06-Dec-18 14:30:15.708 - SENSOR_78_TROUGH_3 mode=1 action #0 of 'FF_FLASHER,DV_FLIL,FL_TT,1,200,100,YELLOW'

06-Dec-18 14:30:15.719 - SENSOR_78_TROUGH_3 mode=1 action #1 of 'FF_DOF,E411,-1'

06-Dec-18 14:30:15.749 - SENSOR_78_TROUGH_3 mode=1 action #2 of 'FF_B2S,B2SSTARTANIMATION,SHIP'

06-Dec-18 14:30:15.806 - NUDGEFORWARD mode=2 action #0 of 'FF_DEV,DV_SH,250'

06-Dec-18 14:30:15.839 - NUDGEFORWARD mode=2 action #1 of 'FF_FLASHER,DV_FLCN,FL_OFF,1,1,100,RED'

06-Dec-18 14:30:15.871 - NUDGEFORWARD mode=1 action #0 of 'FF_DEV,DV_SH,10000'

06-Dec-18 14:30:15.890 - NUDGEFORWARD mode=1 action #1 of 'FF_COLOUR,RED,RGB_TT,1500'

06-Dec-18 14:30:15.903 - NUDGEFORWARD mode=1 action #2 of 'FF_FLASHER,DV_FLCN,FL_ON,1,1,100,RED'

06-Dec-18 14:30:15.923 - NUDGEFORWARD mode=1 action #3 of 'FF_DOF,E405,-1'

06-Dec-18 14:30:15.932 - NUDGEFORWARD mode=1 action #4 of 'FF_B2S,B2SSTARTANIMATION,BALLY'

 

Edited by Tempest43528, 06 December 2018 - 07:50 PM.

[DDH69]

Point #1, this is still not perfect, and I am not a joystick expert, so please stick with me.

 

Party Zone already .... nice.

 

The "Get Offset" button is designed to read the resting state of your joystick.  I've only tried three myself and they all came back with -32767 so I left that in there as a default.  I expect that different joysticks would have different resting positions, if yours is 0 that should be OK.

 

In the test screen that you have screen shots of, you should be able to nudge your cabinet and read the maximum points that a nudge generates.  When you have a reasonable guess put that into the appropriate entry box for the nudge point.  You can then nudge again and next to that entry box it will tell you if you've triggered the nudge.  Once set, during play, DOFLinx will look at the difference between the offset and the nudge point, if that is exceeded, then a nudge event is generated.  A nudge event then stuffs a keystroke into the keyboard buffer causing FX3 to react as if a nudge key was pressed.  The trick here is that I can't stuff a L-Ctrl or R-Ctrl in there so it needs to be a real key like L or R  (that's what I'm using).  This requires a change to the FX3 nudge keys.  Then because you don't want to remap all emulators and actually leave your cabinet set as L / R-CTRL for nudge, DOFLinx is translating the FX_LEFT_NUDGE_INPUT to the FX_LEFT_NUDGE_KEY (and the same for right)  You will see this event if you are running in DEBUG.  You will not see any logging in DEBUG from the test / setup screen.

 

OK, so that's the logic, which bit do we think is not working?

[Tempest43528]

My thoughts are that it is not really detecting it as a joystick so the key presses aren't being passed to FX3.   I remapped the keys in FX3 to L, R and space for nudge.    When I hit them on the keyboard in FX3 I am seeing the nudge on the playfield.   DofLinx is outputing that nudgeleft, nudgeright, nudgeforward are being pressed. 

 

My issue is that when I go to Debug screen and Test Joy stick I am never seeing any values when I nudge the board, The first time I opened the Test Joystick it had 32767 is displayed with all the other values from the screen print.     I can shake the KL25Z and no values ever change.   I clicked on default and then the second screen print shows all the values set to 0 other the nudge point which stayed the same.    I can never get a nudge to register anything.

 

If I go to USB Game Controlers in Win10 and select Pinscale Controller and then go to properties the test tab shows all the nudging and things look good. 

 

I think things are 99% there aside from DofLinx seeing the game controller.   I confirmed Joy Stick input is enabled in the Pinscape config tool.     That one little hook seems to not be working.

 

This is the only "toy" I have enabled.  I have not yet added a plunger, leds or solenoids, etc.   I just wanted to get nudge going first and then keep adding from there.

[Tempest43528]

I also went through and changed JOY_PORT = 1 to 1-4 and retested with no luck.   I has hoping it was not 1 by default for some reason but same result.

[DDH69]

Let me have a look at my setup and the code over the weekend and get back to you.

[DDH69]

So it seems someone can't count 

 

I found this issue on my test rig, but my cabinet has been working ???  I'll get to the cabinet over the weekend and really work out why, but before then.

 

JOY_PORT=1 was not actually port 1.  Please try the attached and we'll learn more.

Attached Files

•  DOFLinx V6.53 Beta 1.zip   88.31KB   24 downloads

[Tempest43528]

That was the problem.   I am now getting values from the Test Joy stick when I nudge the pinscape.      Just fired up the FX3 and now I am seeing some nudging working.   Probably need to dial the offsets in better.

 

Thanks DDH69!   Appreciate the fast replies and the help.    I knew I had to be close and it not detecting the joy stick seems like the only reasonable explanation.

Edited by Tempest43528, 07 December 2018 - 10:53 AM.