90 replies to this topic

[Outhere]

This is what I did for doflinx

 

@echo off
CD /d %~dp0
START "" "%~dp0DOFLinx.exe"

 

See here

Auto Starting Popper with Windows Startup
http://www.nailbuste...?id=other_setup

[captaincroutons]

That perfectly did the trick! Thanks so much for the help! You guys are awesome! Is there any way I can support this project? Thanks again!

[Adm56]

A bit intimidated about trying this but might have to.

I previously had a V3 Virtuapin plunger. I was able to get the nudge where I wanted it (very little movement of the cabinet required to trigger it...I don't find pounding the table fun) in FX3 by adjusting the settings in the Virtuapin tool and usung pretty much the default settings in x360ce.

But I didn't like the plunger. So I installed Pinscape and a DIY potentiometer plunger. Now I LOVE the Plunger (other than FX3 still only uses half of it's range for some reason) but now nudge only works by cranking the sensitivity on the left analog to Max in x360ce and only if you REALLY body the table.

Pinscape is awesome but I'm really surprised it has no means to amplify it's output like Virtuapin did.

[Outhere]

Is the plunger setup you have?

https://www.vpforums...=36108&p=413506

[Adm56]

Pretty much. 3D printed frame for the plunger. Potentiometer. Pinscape KL25Z. I didn't wire buttons into Pinscape since I already had a ipac2. X360ce used to get Pinscape devices and FX3 talking.

It all works but plunger reaches full power in FX3 over 50% of it's physical travel and I REALLY have to bang on the table to get FX3 to register a nudge. If Pinscape allowed me to boost the signal like VirtuaPin did I'd be good to go.

[cherg]

I'm currently running two Zebs boards and DOFLinx has been working frin with FX3. I just installed a Pinscape for nudging purposes and am having issues... DOFLinx is recognizing it as another LEDWIZ and all of my port assignments get messed up when using DOFLinx in FX3. If I disconnect the Pinscape, everything works fine. My log is below... if anyone has any suggestions, I'd apprecite it.

 

20-Oct-19 11:03:56.113 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
20-Oct-19 11:03:56.123 - Starting up - version 6.84
20-Oct-19 11:03:56.128 - For support come and visit the community here http://www.vpforums....p?showforum=104
20-Oct-19 11:03:56.135 - Pre-Reading DOFLinx.INI startup config file details
20-Oct-19 11:03:56.176 - DEBUG enabled with showing of window False
20-Oct-19 11:03:57.350 - Found Teensy controller named 'TeensyStripController'
20-Oct-19 11:03:57.371 - Joystick # 1 detected : 16 buttons   DPAD
20-Oct-19 11:03:57.378 - Joystick # 2 detected : 0 buttons 
20-Oct-19 11:03:57.385 - Joystick # 3 detected : 32 buttons   Z-Axis
20-Oct-19 11:03:57.392 - 1 Pinscape device(s) found
20-Oct-19 11:03:57.398 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
20-Oct-19 11:03:57.404 - DOFLinx device:1 Pinscape setup with 22 outputs
20-Oct-19 11:03:57.409 - 3 LEDWiz device(s) found
20-Oct-19 11:03:57.414 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=1
20-Oct-19 11:03:57.419 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Oct-19 11:03:57.425 - DOFLinx device: 3 Initializing as LEDWiz #2 with ID=0
20-Oct-19 11:03:57.431 - DOFLinx device:3 LEDWiz setup with 32 outputs
20-Oct-19 11:03:57.436 - DOFLinx device: 4 Initializing as LEDWiz #8 with ID=2
20-Oct-19 11:03:57.442 - DOFLinx device:4 LEDWiz setup with 32 outputs
20-Oct-19 11:03:57.447 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one
20-Oct-19 11:03:57.454 - 0 FTDI (Sainsmart) device(s) found
20-Oct-19 11:03:57.461 - 0 PacLED64 device(s) found
20-Oct-19 11:03:57.466 - 0 Ultimate IO device(s) found
20-Oct-19 11:03:57.472 - Reading DOFLinx.INI startup config file details
20-Oct-19 11:03:57.478 - Turning DEBUG off
20-Oct-19 11:03:57.483 - DEBUG enabled with showing of window False
20-Oct-19 11:03:57.489 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini
20-Oct-19 11:03:59.415 - 1 Pinscape device(s) found
20-Oct-19 11:03:59.423 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
20-Oct-19 11:03:59.429 - DOFLinx device:1 Pinscape setup with 22 outputs
20-Oct-19 11:03:59.439 - 3 LEDWiz device(s) found
20-Oct-19 11:03:59.445 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=1
20-Oct-19 11:03:59.454 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Oct-19 11:03:59.460 - DOFLinx device: 3 Initializing as LEDWiz #2 with ID=0
20-Oct-19 11:03:59.467 - DOFLinx device:3 LEDWiz setup with 32 outputs
20-Oct-19 11:03:59.476 - DOFLinx device: 4 Initializing as LEDWiz #8 with ID=2
20-Oct-19 11:03:59.486 - DOFLinx device:4 LEDWiz setup with 32 outputs
20-Oct-19 11:03:59.492 - This device is probably a PinScape emulating a LEDWiz, if it is, then it is better to assign toys to the Pinscape device not this one
20-Oct-19 11:03:59.498 - 0 FTDI (Sainsmart) device(s) found
20-Oct-19 11:03:59.504 - 0 PacLED64 device(s) found
20-Oct-19 11:03:59.510 - 0 Ultimate IO device(s) found
 

[Outhere]

If you add hardware is very likely that things will get changed around you have to go in and change the port numbers

[cherg]

Where exactly should I change port numbers? Below is my log without the Pinscape connected.

 

20-Oct-19 13:36:38.807 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
20-Oct-19 13:36:38.819 - Starting up - version 6.84
20-Oct-19 13:36:38.828 - For support come and visit the community here http://www.vpforums....p?showforum=104
20-Oct-19 13:36:38.838 - Pre-Reading DOFLinx.INI startup config file details
20-Oct-19 13:36:38.915 - DEBUG enabled with showing of window True
20-Oct-19 13:36:40.165 - Found Teensy controller named 'TeensyStripController'
20-Oct-19 13:36:40.187 - Joystick # 1 detected : 16 buttons   DPAD
20-Oct-19 13:36:40.200 - Joystick # 2 detected : 0 buttons 
20-Oct-19 13:36:40.222 - 0 Pinscape device(s) found
20-Oct-19 13:36:40.234 - 2 LEDWiz device(s) found
20-Oct-19 13:36:40.244 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=1
20-Oct-19 13:36:40.253 - DOFLinx device:1 LEDWiz setup with 32 outputs
20-Oct-19 13:36:40.266 - DOFLinx device: 2 Initializing as LEDWiz #2 with ID=0
20-Oct-19 13:36:40.276 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Oct-19 13:36:40.289 - 0 FTDI (Sainsmart) device(s) found
20-Oct-19 13:36:40.300 - 0 PacLED64 device(s) found
20-Oct-19 13:36:40.313 - 0 Ultimate IO device(s) found
20-Oct-19 13:36:40.325 - Reading DOFLinx.INI startup config file details
20-Oct-19 13:36:40.339 - Turning DEBUG off
20-Oct-19 13:36:40.375 - DEBUG enabled with showing of window True
20-Oct-19 13:36:40.390 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini
20-Oct-19 13:36:42.220 - 0 Pinscape device(s) found
20-Oct-19 13:36:42.244 - 2 LEDWiz device(s) found
20-Oct-19 13:36:42.256 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=1
20-Oct-19 13:36:42.269 - DOFLinx device:1 LEDWiz setup with 32 outputs
20-Oct-19 13:36:42.281 - DOFLinx device: 2 Initializing as LEDWiz #2 with ID=0
20-Oct-19 13:36:42.293 - DOFLinx device:2 LEDWiz setup with 32 outputs
20-Oct-19 13:36:42.304 - 0 FTDI (Sainsmart) device(s) found
20-Oct-19 13:36:42.317 - 0 PacLED64 device(s) found
20-Oct-19 13:36:42.330 - 0 Ultimate IO device(s) found
20-Oct-19 13:36:49.966 - Shutting down
20-Oct-19 13:36:50.007 - Program close

[Outhere]

Add DEBUG=0 change to 1 to your DOFLinx.ini file

https://www.vpforums...=43013&p=436839

[DDH69]

Pinscape boards can be set to emulate a LEDWiz or appear as a Pinscape in the Pinscape setup tool.  I suggest setting it to appear as a Pinscape board (not an emulated LEDWiz) unless you need that for some other purpose.  With it appearing as a native Pinscape its easier to get settings, etc.

 

Also, as Outhere said, the device numbers for DOFLinx may change when you add new hardware.  This is due to the board detection order.  Determine the LEDWiz emulation question and setting first, then get your new device numbers from the DEBUG.LOG file.  Pinscape's are detected first, so if your flipper solenoid was 105 previously, its likely now 205.

[cherg]

Thanks folks, I got it sorted out. Now working on getting nudging going in FX3.

[cherg]

Question on setting up nudge - when I run the test joystick option and select Get Offset, I'm able to observe the NUDGE responses in the app when nudging however the only values that change are X/Y Relative Position and the X Min/Max and Y Min/Max. What values should I be inputting into L/R/F Nudge Points? It looks like the defaults are -2500, 2500 and 2500 respectively. I get the NUDGE response in the test app but nothing occurs in FX3.

Edited by cherg, 20 October 2019 - 11:36 PM.

[DDH69]

https://www.vpforums.org/index.php?showtopic=42325

[cherg]

Thanks but the link is for this thread. I'm not finding the info I need... Where do the values for L/R/F Nudge Points come from? 

[DDH69]

The values for the nudge points are your own.  The reason for the test screen that you've mentioned earlier is to determine what values you wish to use.  You can then of course adjust those values if they are not giving you the result you want.

 

So the values are the point at which you need to bump the cabinet to make the accelerometer reach, which is reported to the Windows as a joystick X / Y position.

 

Bang away with the test screen running, reset every now and again, jot down on a piece of paper what you think the values might be for you, then bump your machine and see if your happy with how much / little effort it takes to get to that nudge point.

[cherg]

Thanks for clarifying. Got everything going. Thanks for all the help.

Edited by cherg, 21 October 2019 - 11:40 AM.

[Bartosaurio]

DOFLinx can be used to take analogue nudge and turn it into digital nudge.  This means that an input device for analogue nudge, such as the PinScape with an accelerometer that presents as a joystick, can run in your cabinet, and when it hits limits that you set, push the digital nudge keyboard beys for emulators like FX3.

 

So how does this work?  Well firstly you setup DOFLinx to know about your analogue nudge device, that is the joystick port and some other key values.  Then when running, if your nudge goes over the preset value, a key stroke is sent to your emulating application.  You can also optionally still have your cabinet manual nudge keys (often magna-save buttons) enabled as well.  DOFLinx does this by cascading the nudge keys.  Really it is as easy as that!

 

I have never been able to get DOFLinx to send L-Crtl and R-Ctrl to FX3 which are the default keys.  As such, I use the “L” and “R” letter keys for left and right nudge while leaving “Space” as the default forward nudge.  A small pain, but quite workable.

 

Prerequisites:

1. DOFLinx installed and running
2. A working analogue nudge device presenting to your PC as a joystick
3. An emulator that only takes nudge via keystrokes

 

Setting up:

1. Run DOFLinx with DEBUG=1
2. Right click and select the “Test Joy Stick” option
3. Work through the “Joystick #” until you find the one that changes values when you nudge.  There is most likely only one active joystick in your cabinet.
4. With the cabinet still, press the “Get Offset” button to get the first values
5. Now nudge your cabinet and see what values in the “X Nudge Point” allow the “NUDGE” word to come up when you think you’ve pushed the cabinet hard enough.  Be brutal, cabinets love to be shoved!
6. Take note of all of the settings, or leave it on the screen as you do the next step.
7. Edit your DOFLinx.INI file, JOY_PORT= the “Joystick #”, JOY_X_OFFSET = “X Offset”, JOY_Y_OFFSET = “Y Offset”, NUDGE_LEFT_POINT = “L Nudge Point”, NUDGE_RIGHT_POINT = “R Nudge Point”, NUDGE_FORWARD_POINT = “F Nudge Point”
8. Next tell DOFLinx which keys you are using in your emulator from the standard keycodes – found here https://docs.microso...rtual-key-codes
9. If you have set FX3 to “L”, “R” letter and “Space” keys then set NUDGE_LEFT_KEY=4C, NUDGE_RIGHT_KEY=52, NUDGE_FORWARD_KEY=20
10. Now if you optionally want existing cabinet nudge keys to still work when you have analogue nudge setup, then configure the key codes currently set for those.  If your magna-save keys were used for left and right nudge and were set to the traditional L-Ctrl and R-Ctrl then you would set NUDGE_LEFT_INPUT=A2, NUDGE_RIGHT_INPUT=A3.  If you didn’t want to cascade manual nudge keys then simply leave these two parameters out of your DOFLinx.INI file
11. Now set DEBUG=0, restart DOFLinx and give it a try.

 

 

In your DOFLinx.INI file you will need to setup the following parameters for nudge:

 

JOY_PORT=

JOY_X_OFFSET=

JOY_Y_OFFSET=

NUDGE_LEFT_POINT=-

NUDGE_RIGHT_POINT=

NUDGE_FORWARD_POINT=

NUDGE_LEFT_KEY=

NUDGE_RIGHT_KEY=

NUDGE_FORWARD_KEY=

NUDGE_LEFT_INPUT=

NUDGE_RIGHT_INPUT=

 

Here is my configuration where my PinScape presents as joystick #2, FX3 uses “L” and “R” letter and “Space” keys for nudge, and my cabinet has “L-Ctrl” and “R-Ctrl” as manual nudge keys that I cascade (ie still work with manual nudge)

JOY_PORT=2

JOY_X_OFFSET=32767

JOY_Y_OFFSET=32767

NUDGE_LEFT_POINT=-5500

NUDGE_RIGHT_POINT=5500

NUDGE_FORWARD_POINT=4000

NUDGE_LEFT_KEY=4C

NUDGE_RIGHT_KEY=52

NUDGE_FORWARD_KEY=20

NUDGE_LEFT_INPUT=A2

NUDGE_RIGHT_INPUT=A3

 

Good morning  guys,

 

I just did all this as instructed. So in order to test it I added Notepad to the processes line. Also set debug to 1.

When I open notepad, the debug window shows that Notepad was detected.

 

When I push some buttons, notepad shows them as characters; combining the flippers buttons with the start button shows the admitation, but nothing is displayed in notepad when I bump the machine... I was expecting the R and L coming up...

 

Any idea why?

 

The JOY_PORT is the correct one and the “Test Joy Stick” option is detecting it and "Nudge" word comes up when is bump the machine.

 

I am starting with the simplest ini as shown:

 

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

DEBUG=1

PROCESSES=Pinball FX2,Pinball FX3,Notepad

 

JOY_PORT=1

JOY_X_OFFSET=32784

JOY_Y_OFFSET=32759

NUDGE_LEFT_POINT=-1500

NUDGE_RIGHT_POINT=1500

NUDGE_FORWARD_POINT=1000

NUDGE_LEFT_KEY=4C

NUDGE_RIGHT_KEY=52

NUDGE_FORWARD_KEY=20

[DDH69]

Your expectation of "L" and "R" is correct.  I can't see anything obviously wrong, so now we start looking harder.

 

Can you post a screen shot of when you're testing the NUDGE in the DOFLinx test joystick screen.

 

Also, post a DEBUG.LOG from when you're testing with Notepad along with a description of what keys / nudging you did.

 

The answer should be in there somewhere.

[Bartosaurio]

Thank you for your reply.

 

This is the test Joystick screen: (I bumped the cabinet to take the pic)

 

 

This is the LOG, After open Notepad, I pushed start, left flipper + start, coin, right flipper + coin, enter and bumped the cabinet left and right.

 

Only output in notepad was: 1!5% (and enter)

 

05-Nov-19 09:47:17.346 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

05-Nov-19 09:47:17.362 - Starting up - version 6.82

05-Nov-19 09:47:17.362 - For support come and visit the community here http://www.vpforums....p?showforum=104

05-Nov-19 09:47:17.378 - Pre-Reading DOFLinx.INI startup config file details

05-Nov-19 09:47:17.440 - DEBUG enabled with showing of window True

05-Nov-19 09:47:17.456 - No DOF Global Config file supplied

05-Nov-19 09:47:17.487 - Joystick # 1 detected : 32 buttons   Z-Axis

05-Nov-19 09:47:17.518 - 1 Pinscape device(s) found

05-Nov-19 09:47:17.518 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller

05-Nov-19 09:47:17.550 - DOFLinx device:1 Pinscape setup with 22 outputs

05-Nov-19 09:47:17.565 - 1 LEDWiz device(s) found

05-Nov-19 09:47:17.581 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=0

05-Nov-19 09:47:17.581 - DOFLinx device:2 LEDWiz setup with 32 outputs

05-Nov-19 09:47:17.596 - 0 FTDI (Sainsmart) device(s) found

05-Nov-19 09:47:17.612 - 0 PacLED64 device(s) found

05-Nov-19 09:47:17.612 - 0 Ultimate IO device(s) found

05-Nov-19 09:47:17.628 - Reading DOFLinx.INI startup config file details

05-Nov-19 09:47:17.628 - Reading DirectOutputConfig file named c:\DirectOutput\config\directoutputconfig.ini

05-Nov-19 09:47:17.643 - Turning DEBUG off

05-Nov-19 09:47:17.659 - DEBUG enabled with showing of window True

05-Nov-19 09:47:19.487 - 1 Pinscape device(s) found

05-Nov-19 09:47:19.503 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller

05-Nov-19 09:47:19.519 - DOFLinx device:1 Pinscape setup with 22 outputs

05-Nov-19 09:47:19.534 - 1 LEDWiz device(s) found

05-Nov-19 09:47:19.550 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=0

05-Nov-19 09:47:19.565 - DOFLinx device:2 LEDWiz setup with 32 outputs

05-Nov-19 09:47:19.581 - 0 FTDI (Sainsmart) device(s) found

05-Nov-19 09:47:19.597 - 0 PacLED64 device(s) found

05-Nov-19 09:47:19.597 - 0 Ultimate IO device(s) found

05-Nov-19 09:47:35.862 - Found valid process name of 'Notepad'

05-Nov-19 09:47:37.909 - Activated by process name : 'Notepad'

05-Nov-19 09:47:37.940 - Named process detected and startup commenced

05-Nov-19 09:47:37.956 - Using full colour palette

05-Nov-19 09:47:37.972 - 122 colours added to the palette

05-Nov-19 09:48:16.270 - Activating process disappeared so stopping things

05-Nov-19 09:48:16.286 - 1 Pinscape device(s) found

05-Nov-19 09:48:16.301 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller

05-Nov-19 09:48:16.317 - DOFLinx device:1 Pinscape setup with 22 outputs

05-Nov-19 09:48:16.333 - 1 LEDWiz device(s) found

05-Nov-19 09:48:16.348 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=0

05-Nov-19 09:48:16.348 - DOFLinx device:2 LEDWiz setup with 32 outputs

05-Nov-19 09:48:16.364 - 0 FTDI (Sainsmart) device(s) found

05-Nov-19 09:48:16.379 - 0 PacLED64 device(s) found

05-Nov-19 09:48:16.395 - 0 Ultimate IO device(s) found

05-Nov-19 09:48:25.270 - Shutting down

05-Nov-19 09:48:25.317 - Program close

[DDH69]

Hmmmm, still not sure.  I will run parallel tests on my cabinet tonight and see what I can come up with.