38 replies to this topic

[Outhere]

  Future pinball is working just fine

Excellent work

Run DOFLinx 4.0

simple force feedback for Pinball FX2 is working

-

full force feedback for Pinball FX2 tables with memory mapped trigger files (FX2 files) NOT WORKING

Pinball FX2 Steam version --Yes

Cabinet mode enabled --Yes

full screen mode -- Yes

Back Glass is Turned on

-

23-Oct-16 21:41:10 - Activated by process name : Pinball FX2
23-Oct-16 21:41:15 - Game name = ''
23-Oct-16 21:41:15 - Named process detected and startup commenced
23-Oct-16 21:41:15 - 1 LEDWiz device(s) found
23-Oct-16 21:41:15 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
23-Oct-16 21:41:15 - DOFLinx device:1 LEDWiz setup with 32 outputs
23-Oct-16 21:41:16 - 1 FTDI (Sainsmart) device(s) found
23-Oct-16 21:41:16 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
23-Oct-16 21:41:16 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
23-Oct-16 21:41:16 - Using full colour palette
23-Oct-16 21:41:16 - Turning on fixed out Device=1 Output=1
23-Oct-16 21:41:28 - Left flipper pressed
23-Oct-16 21:41:28 - Key number #39 is activating device=1 output=27
23-Oct-16 21:41:29 - Left flipper lifted
23-Oct-16 21:41:29 - Key number #39 is de-activating device=1 output=27
23-Oct-16 21:41:29 - Left flipper pressed
23-Oct-16 21:41:29 - Key number #39 is activating device=1 output=27
23-Oct-16 21:41:30 - Left flipper lifted
23-Oct-16 21:41:30 - Key number #39 is de-activating device=1 output=27
23-Oct-16 21:41:31 - Left flipper pressed
23-Oct-16 21:41:31 - Key number #39 is activating device=1 output=27
23-Oct-16 21:41:31 - Left flipper lifted
23-Oct-16 21:41:31 - Key number #39 is de-activating device=1 output=27
23-Oct-16 21:41:43 - Right flipper pressed
23-Oct-16 21:41:43 - Key number #37 is activating device=1 output=22
23-Oct-16 21:41:43 - Right flipper lifted
23-Oct-16 21:41:43 - Key number #37 is de-activating device=1 output=22
23-Oct-16 21:41:51 - Left flipper pressed
23-Oct-16 21:41:51 - Key number #39 is activating device=1 output=27
23-Oct-16 21:41:51 - Left flipper lifted
23-Oct-16 21:41:51 - Key number #39 is de-activating device=1 output=27
23-Oct-16 21:41:57 - Activating process disappeared so stopping things
23-Oct-16 21:41:57 - Stopping DOF controllers due to 'Start Each Time' flag

-

####
# The config file for DOFLinx
# A mad idea by DDH69 to have some flipper sounds, RGB display and turn buttons on when playing Pinball FX2 via Steam
# Its grown a lot since that silly start!
# Note - this works with LEDWiz, PacLed64, KL25Z and Sainsmart (FTDI devices)
# Edit this file as you see fit, lines that start with a hash (#) or are blank are not processed.  This blurb and comments can be cut out if you want.
#
# Output devices outputs are entered in the format of
# device (D) and output number (#) in the format D##, so controller device 1 and output 3 is "103" without the quotes, controller board 2 output 23 is "223" without quotes
####

# location of your standard DOF outut configuration file.  Keep this as the first item in the file
DIRECTOUTPUTCONFIG=e:\DirectOutput\config\directoutputconfig.ini

# If you want to list the processes that will wake up DOFFX2, comment it out if you just want Pinball FX2
PROCESSES=Pinball FX2,Future Pinball
#,VPinball_9_9_1,VPPhysMod5
# Which DOF Controller output for the flipper solenoids / contactors
L_FLIPPER_OUTPUT=204
R_FLIPPER_OUTPUT=208
# The keyboard hex code for the key that is used for each flipper from https://msdn.microso...1(v=vs.85).aspx
# Left Shift = A0, Right Shift = A1
L_FLIPPER_KEY=27
R_FLIPPER_KEY=25
# Just in case things go wrong (ie no keyup signal is detected, flipper held down for a long time), what is the maximum time a flipper solenoid / contactor can be in in milliseconds
MAX_FLIPPER_ON=2000
# What LEDWiz output(s) are used for RGB devices.  Just enter the Red output number.  Multiples can be entered seperated by a comma
#RGB_OUTPUT=117,120,123,126
# Rainbow - cycle through the colours, Random - pick a random next colour, A colour name as it appears in the DirectOutputConfig.ini file
RGB_STYLE=RANDOM
# What changes the colour?  Time - set time period, Flipper = flipper press after the RGB_TRIGGER minimum time (to stop rapid colour changes)
RGB_TRIGGER=FLIPPER
# Dependent on trigger selection the period between changes or the minimum time for change between flipper flips
RGB_MIN_TIME=1000
PATH_FX2=E:\DirectOutput\DOFLinx_FX2\
# The button(s) to turn on when DOFLinx starts, ie the exit button LED
BUTTONS_ON=101
# Make the "1" (31) key (Start in VP) pulse LEDWiz 120 and "4" (34) to pulse controller/output 121
KEY_TO_OUTPUT=25 122 27 127
# Set a key to turn on a specific colour for your RGB.  The line below makes the Left Control (A2) and the Right Control (A3) turn my undercab RGB strip red.
# In Pinball FX2 this means when I nudge it all goes red.
#KEY_TO_COLOUR=A2 109 Red A3 109 Red
# Setting FORCE_ACTIVE=1 will cause DOFFX2 to not listen for processes and just run until you kill the process.  Handy for using it for things other than PinBall FX2
FORCE_ACTIVE=0
# If you want the program to stop when your named process stops then set this to 1.  If you want it to run in the background all the time leave it as 0
QUIT_AFTER_PROCESS=0
# Set to 1 to output the game name to the log regardless of the DEBUG flag setting.  Set to 0 to simply follow the DEBUG flag.
# Quite useful when you trying to get the FX2 window game name for setting game specific colours
OUTPUT_GAME_NAME=1

####
# Sample setup to enable the Future Pinball Link.  Edit the LINK_ items to be your ports and settings.
####
FP_ATTEMPT_LINK=1
LINK_LF=208,150,2000
#LINK_LF=120,50,1000
LINK_RF=204,150,2000
#LINK_RF=127,50,1000
LINK_LS=208,50,500
LINK_RS=204,50,500
LINK_ML=208,50,500
LINK_MC=204,50,500
LINK_MR=204,50,500
LINK_BL=208,50,500
LINK_BC=204,50,500
LINK_BR=204,50,500
LINK_SH=122,200,5000
#LINK_GR=126,150,1000
#LINK_KN=124,120,500
LINK_ST=102
#LINK_EX=
#LINK_CN=105
#LINK_EB=
LINK_LB=101
LINK_SR=103
#LINK_FR=
LINK_FLOL=117
LINK_FLIL=120
LINK_FLCN=123
LINK_FLOR=126
LINK_FLIR=124


####
# 0 = OFF (normal operation), 1 = ON - When ON a window will appear and a log file will be created in the EXE directory.
DEBUG=1
 

[DDH69]

OK, I can see a problem from the log, but not sure why.  Got to go pick up my son so I'll get back to this in about an hour.

 

The problem I see is where "Pinball FX2" activates DOFLinx, but DOFLinx does not get a Game Name.  This tends to indicate that it sees an activating process but for some reason doesn't think its Pinball FX2 ?

 

What FX2 game is the log from?  (presuming its one with an FX2 file)

 

If you get this before I get back to this, it would be worth temporarily commenting out the PROCESSES= parameter in your DOFLinx.INI file.  This will force only one valid process being Pinball FX2.  Interested to see what that yields.

[DDH69]

There is definitely a problem here, just still not sure exactly what it is.

 

Is the above LOG file a complete log file from a single run of DOFLinx or is it the section relating to the FX2 table in question cut from a larger file?  I'm trying to ascertain if another process has activated DOFLinx before the FX2 table that's not working.  Perhaps you could try the FX2 table with the memory map file as the first thing to activate DOFLinx after restarting it.

 

At present I can't see why DOFLinx hasn't triggered into the section to discover the table name.  I've added some more logging that I'll test a bit later.  I'd love to understand a bit more before sending you an update with just logging.

[DDH69]

OK, still looking at this.

 

One more possibility - after the Pinball FX2 process is detected DOFLinx waits a short while (5 seconds) for the various FX2 windows to open.  The game name is extracted from one of the open windows.  It is possible that the startup time for Pinball FX2 means that all the windows haven't opened before the 5 second wait time expires., thus no automatic game name and no loading of the FX2 file and reversion to the next mode of operation being keyboard monitoring.

 

It is possible to test this;

1. Quit DOFLinx   (DOFLinxMsg QUIT)

2. Run File Explorer

3. Start Pinball FX2 (via your front end if required or easier) with one of the games with a FX2 file

4. Alt-Tab to File Explorer

5. Start DOFLinx

6. Alt-Tab back to Pinball FX2

7. See if it works

 

OK, enough of me looking like a stalker, I'm moving on now until I hear back 

[Outhere]

OK, I can see a problem from the log, but not sure why.  Got to go pick up my son so I'll get back to this in about an hour.

 

The problem I see is where "Pinball FX2" activates DOFLinx, but DOFLinx does not get a Game Name.  This tends to indicate that it sees an activating process but for some reason doesn't think its Pinball FX2 ?

 

What FX2 game is the log from?  (presuming its one with an FX2 file)

 

If you get this before I get back to this, it would be worth temporarily commenting out the PROCESSES= parameter in your DOFLinx.INI file.  This will force only one valid process being Pinball FX2.  Interested to see what that y

BobsBurgersPinball

it would be worth temporarily commenting out the PROCESSES= parameter in your DOFLinx.INI file. ---   No difference

There is definitely a problem here, just still not sure exactly what it is.

 

Is the above LOG file a complete log file from a single run of DOFLinx or is it the section relating to the FX2 table in question cut from a larger file?  I'm trying to ascertain if another process has activated DOFLinx before the FX2 table that's not working.  Perhaps you could try the FX2 table with the memory map file as the first thing to activate DOFLinx after restarting it.

 

At present I can't see why DOFLinx hasn't triggered into the section to discover the table name.  I've added some more logging that I'll test a bit later.  I'd love to understand a bit more before sending you an update with just logging.

Is the above LOG file a complete log file from a single run of DOFLinx --Yes

OK, still looking at this.

 

One more possibility - after the Pinball FX2 process is detected DOFLinx waits a short while (5 seconds) for the various FX2 windows to open.  The game name is extracted from one of the open windows.  It is possible that the startup time for Pinball FX2 means that all the windows haven't opened before the 5 second wait time expires., thus no automatic game name and no loading of the FX2 file and reversion to the next mode of operation being keyboard monitoring.

 

It is possible to test this;

1. Quit DOFLinx   (DOFLinxMsg QUIT)

2. Run File Explorer

3. Start Pinball FX2 (via your front end if required or easier) with one of the games with a FX2 file

4. Alt-Tab to File Explorer

5. Start DOFLinx

6. Alt-Tab back to Pinball FX2

7. See if it works

 

OK, enough of me looking like a stalker, I'm moving on now until I hear back 

This Works

-

24-Oct-16 10:37:24 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
24-Oct-16 10:37:24 - Starting up - version 4.0
24-Oct-16 10:37:24 - 1 LEDWiz device(s) found
24-Oct-16 10:37:24 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
24-Oct-16 10:37:24 - DOFLinx device:1 LEDWiz setup with 32 outputs
24-Oct-16 10:37:25 - 1 FTDI (Sainsmart) device(s) found
24-Oct-16 10:37:25 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
24-Oct-16 10:37:25 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
24-Oct-16 10:37:25 - Reading DOFLinx.INI startup config file details
24-Oct-16 10:37:25 - Reading DOF config file
24-Oct-16 10:37:28 - Activated by process name : Pinball FX2
24-Oct-16 10:37:33 - Game name = 'BobsBurgersPinball'
24-Oct-16 10:37:33 - Named process detected and startup commenced
24-Oct-16 10:37:33 - 1 LEDWiz device(s) found
24-Oct-16 10:37:34 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
24-Oct-16 10:37:34 - DOFLinx device:1 LEDWiz setup with 32 outputs
24-Oct-16 10:37:34 - 1 FTDI (Sainsmart) device(s) found
24-Oct-16 10:37:34 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
24-Oct-16 10:37:34 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
24-Oct-16 10:37:34 - Loading FX2 configuration file named E:\DirectOutput\DOFLinx_FX2\BobsBurgersPinball.FX2
24-Oct-16 10:37:34 - Loading FX2 configuration file E:\DirectOutput\DOFLinx_FX2\BobsBurgersPinball.FX2
24-Oct-16 10:37:34 - Process has administration rights
24-Oct-16 10:37:34 - FX2 full link active for game name=BobsBurgersPinball
24-Oct-16 10:37:34 - Building restricted colour palette for game name = BobsBurgersPinball
24-Oct-16 10:37:34 - Turning on fixed out Device=1 Output=1
24-Oct-16 10:37:34 - There are no OFF actions for GAMEMODE
24-Oct-16 10:37:35 - GAMEMODE mode=1 action #0 of 'FF_COLOUR,BLACK,RGB_DF,0'
24-Oct-16 10:37:36 - GAMEMODE mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_FD,6,750,50,ORANGE'
24-Oct-16 10:37:36 - GAMEMODE mode=1 action #2 of 'FF_FLASHER,DV_FLOR,FL_FD,6,750,50,ORANGE'
24-Oct-16 10:37:36 - GAMEMODE mode=1 action #3 of 'FF_FLASHER,DV_FLIL,FL_FD,6,750,50,YELLOW'
24-Oct-16 10:37:36 - GAMEMODE mode=1 action #4 of 'FF_FLASHER,DV_FLIR,FL_FD,6,750,50,YELLOW'
24-Oct-16 10:37:36 - GAMEMODE mode=1 action #5 of 'FF_FLASHER,DV_FLCN,FL_FD,6,750,50,ORANGE'
24-Oct-16 10:37:40 - There are no OFF actions for GAMEMODE
24-Oct-16 10:37:48 - Key number #37 is activating device=1 output=22
24-Oct-16 10:37:49 - Key number #37 is de-activating device=1 output=22
24-Oct-16 10:37:49 - GAMEMODE mode=1 action #0 of 'FF_COLOUR,BLACK,RGB_DF,0'
24-Oct-16 10:37:49 - GAMEMODE mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_FD,6,750,50,ORANGE'
24-Oct-16 10:37:49 - GAMEMODE mode=1 action #2 of 'FF_FLASHER,DV_FLOR,FL_FD,6,750,50,ORANGE'
24-Oct-16 10:37:49 - GAMEMODE mode=1 action #3 of 'FF_FLASHER,DV_FLIL,FL_FD,6,750,50,YELLOW'
24-Oct-16 10:37:49 - GAMEMODE mode=1 action #4 of 'FF_FLASHER,DV_FLIR,FL_FD,6,750,50,YELLOW'
24-Oct-16 10:37:49 - GAMEMODE mode=1 action #5 of 'FF_FLASHER,DV_FLCN,FL_FD,6,750,50,ORANGE'
24-Oct-16 10:37:51 - Key number #39 is activating device=1 output=27
24-Oct-16 10:37:51 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 10:37:51 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 10:37:51 - Key number #39 is de-activating device=1 output=27
24-Oct-16 10:37:51 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 10:37:51 - Link is turning off device #2
24-Oct-16 10:37:53 - Key number #37 is activating device=1 output=22
24-Oct-16 10:37:53 - LEFTFLIPPER mode=1 action #0 of 'FF_DEV,DV_LF,10000'
24-Oct-16 10:37:53 - Link is turning on device #1 for 2000 milliseconds
24-Oct-16 10:37:54 - Key number #37 is de-activating device=1 output=22
24-Oct-16 10:37:54 - LEFTFLIPPER mode=2 action #0 of 'FF_DEV,DV_LF,0'
24-Oct-16 10:37:54 - Link is turning off device #1
24-Oct-16 10:37:55 - Key number #39 is activating device=1 output=27
24-Oct-16 10:37:55 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 10:37:55 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 10:37:55 - Key number #39 is de-activating device=1 output=27
24-Oct-16 10:37:56 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 10:37:56 - Link is turning off device #2
24-Oct-16 10:37:56 - Key number #39 is activating device=1 output=27
24-Oct-16 10:37:57 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 10:37:57 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 10:37:57 - Key number #39 is de-activating device=1 output=27
24-Oct-16 10:37:57 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 10:37:57 - Link is turning off device #2
24-Oct-16 10:37:58 - LEFT_SLINGSHOT mode=1 action #0 of 'FF_DEV,DV_LS,-1'
24-Oct-16 10:37:58 - Link is turning on device #3 for 50 milliseconds
24-Oct-16 10:37:58 - LEFT_SLINGSHOT_FLASHER mode=1 action #0 of 'FF_COLOUR,YELLOW,RGB_TT,50'
24-Oct-16 10:37:58 - LEFT_SLINGSHOT_FLASHER mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_TT,1,50,100,YELLOW'
24-Oct-16 10:37:58 - There are no OFF actions for LEFT_SLINGSHOT
24-Oct-16 10:37:58 - There are no OFF actions for LEFT_SLINGSHOT_FLASHER
24-Oct-16 10:37:58 - Link is turning off device #3
24-Oct-16 10:37:59 - There are no OFF actions for GAMEMODE
24-Oct-16 10:38:04 - Key number #39 is activating device=1 output=27
24-Oct-16 10:38:04 - Key number #39 is de-activating device=1 output=27
24-Oct-16 10:38:11 - Activating process disappeared so stopping things
24-Oct-16 10:38:11 - Stopping DOF controllers due to 'Start Each Time' flag
24-Oct-16 10:38:17 - Shutting down
24-Oct-16 10:38:17 - Program close

Edited by Outhere, 24 October 2016 - 03:52 PM.

[DDH69]

OK then, I know what it is.  We'll have it fixed later today.

 

About to go and test some changes, which may take a while as another member from this forum is coming to visit this morning and see a full cabinet in operation.

[DDH69]

V4.01 with what should be the fix to this has been uploaded.  Please let me know if this is in fact solved.

[Outhere]

Its a no go

Same as before

 

24-Oct-16 20:51:06 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
24-Oct-16 20:51:06 - Starting up - version 4.01
24-Oct-16 20:51:06 - 1 LEDWiz device(s) found
24-Oct-16 20:51:06 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
24-Oct-16 20:51:06 - DOFLinx device:1 LEDWiz setup with 32 outputs
24-Oct-16 20:51:06 - 1 FTDI (Sainsmart) device(s) found
24-Oct-16 20:51:06 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
24-Oct-16 20:51:06 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
24-Oct-16 20:51:06 - Reading DOFLinx.INI startup config file details
24-Oct-16 20:51:07 - Reading DOF config file
24-Oct-16 20:52:23 - Found valid process name of 'Pinball FX2'
24-Oct-16 20:52:23 - Setting FX2 process ID to :6396
24-Oct-16 20:52:25 - Activated by process name : 'Pinball FX2'
24-Oct-16 20:52:25 - Serching for FX2 game name
24-Oct-16 20:52:35 - Game name = ''
24-Oct-16 20:52:35 - Named process detected and startup commenced
24-Oct-16 20:52:35 - 1 LEDWiz device(s) found
24-Oct-16 20:52:35 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
24-Oct-16 20:52:35 - DOFLinx device:1 LEDWiz setup with 32 outputs
24-Oct-16 20:52:35 - 1 FTDI (Sainsmart) device(s) found
24-Oct-16 20:52:35 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
24-Oct-16 20:52:35 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
24-Oct-16 20:52:35 - Using full colour palette
24-Oct-16 20:52:35 - Turning on fixed out Device=1 Output=1
24-Oct-16 20:52:35 - Setting fixed RGB style of 'RANDOM' to colour to index=9999 with name=Random
24-Oct-16 20:52:53 - Right flipper pressed
24-Oct-16 20:52:53 - Key number #37 is activating device=1 output=22
24-Oct-16 20:52:54 - Right flipper lifted
24-Oct-16 20:52:54 - Key number #37 is de-activating device=1 output=22
24-Oct-16 20:53:18 - Right flipper pressed
24-Oct-16 20:53:18 - Key number #37 is activating device=1 output=22
24-Oct-16 20:53:18 - Right flipper lifted
24-Oct-16 20:53:18 - Key number #37 is de-activating device=1 output=22
24-Oct-16 20:53:27 - Activating process disappeared so stopping things
24-Oct-16 20:53:27 - Stopping DOF controllers due to 'Start Each Time' flag

 

Works if I do this

 

It is possible to test this;

1. Quit DOFLinx   (DOFLinxMsg QUIT)

2. Run File Explorer

3. Start Pinball FX2 (via your front end if required or easier) with one of the games with a FX2 file

4. Alt-Tab to File Explorer

5. Start DOFLinx

6. Alt-Tab back to Pinball FX2

7. See if it works

24-Oct-16 21:01:09 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
24-Oct-16 21:01:09 - Starting up - version 4.01
24-Oct-16 21:01:09 - 1 LEDWiz device(s) found
24-Oct-16 21:01:09 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
24-Oct-16 21:01:09 - DOFLinx device:1 LEDWiz setup with 32 outputs
24-Oct-16 21:01:09 - 1 FTDI (Sainsmart) device(s) found
24-Oct-16 21:01:09 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
24-Oct-16 21:01:09 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
24-Oct-16 21:01:09 - Reading DOFLinx.INI startup config file details
24-Oct-16 21:01:09 - Reading DOF config file
24-Oct-16 21:01:10 - Found valid process name of 'Pinball FX2'
24-Oct-16 21:01:10 - Setting FX2 process ID to :7392
24-Oct-16 21:01:12 - Activated by process name : 'Pinball FX2'
24-Oct-16 21:01:12 - Serching for FX2 game name
24-Oct-16 21:01:13 - FX2 window with game name found .... extracting from 'Pinball FX2 - Bob's Burgers Pinball'
24-Oct-16 21:01:13 - Game name = 'BobsBurgersPinball'
24-Oct-16 21:01:13 - Named process detected and startup commenced
24-Oct-16 21:01:13 - 1 LEDWiz device(s) found
24-Oct-16 21:01:13 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
24-Oct-16 21:01:13 - DOFLinx device:1 LEDWiz setup with 32 outputs
24-Oct-16 21:01:13 - 1 FTDI (Sainsmart) device(s) found
24-Oct-16 21:01:13 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
24-Oct-16 21:01:13 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
24-Oct-16 21:01:13 - Loading FX2 configuration file named E:\DirectOutput\DOFLinx_FX2\BobsBurgersPinball.FX2
24-Oct-16 21:01:13 - Loading FX2 configuration file E:\DirectOutput\DOFLinx_FX2\BobsBurgersPinball.FX2
24-Oct-16 21:01:13 - Process has administration rights
24-Oct-16 21:01:13 - FX2 full link active for game name=BobsBurgersPinball
24-Oct-16 21:01:13 - Building restricted colour palette for game name = BobsBurgersPinball
24-Oct-16 21:01:13 - Turning on fixed out Device=1 Output=1
24-Oct-16 21:01:13 - There are no OFF actions for GAMEMODE
24-Oct-16 21:01:14 - GAMEMODE mode=1 action #0 of 'FF_COLOUR,BLACK,RGB_DF,0'
24-Oct-16 21:01:14 - Setting fixed RGB style of 'RANDOM' to colour to index=9999 with name=Random
24-Oct-16 21:01:15 - GAMEMODE mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_FD,6,750,50,ORANGE'
24-Oct-16 21:01:15 - GAMEMODE mode=1 action #2 of 'FF_FLASHER,DV_FLOR,FL_FD,6,750,50,ORANGE'
24-Oct-16 21:01:15 - GAMEMODE mode=1 action #3 of 'FF_FLASHER,DV_FLIL,FL_FD,6,750,50,YELLOW'
24-Oct-16 21:01:15 - GAMEMODE mode=1 action #4 of 'FF_FLASHER,DV_FLIR,FL_FD,6,750,50,YELLOW'
24-Oct-16 21:01:15 - GAMEMODE mode=1 action #5 of 'FF_FLASHER,DV_FLCN,FL_FD,6,750,50,ORANGE'
24-Oct-16 21:01:27 - There are no OFF actions for GAMEMODE
24-Oct-16 21:01:34 - GAMEMODE mode=1 action #0 of 'FF_COLOUR,BLACK,RGB_DF,0'
24-Oct-16 21:01:34 - Setting fixed RGB style of 'RANDOM' to colour to index=9999 with name=Random
24-Oct-16 21:01:34 - GAMEMODE mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_FD,6,750,50,ORANGE'
24-Oct-16 21:01:34 - GAMEMODE mode=1 action #2 of 'FF_FLASHER,DV_FLOR,FL_FD,6,750,50,ORANGE'
24-Oct-16 21:01:34 - GAMEMODE mode=1 action #3 of 'FF_FLASHER,DV_FLIL,FL_FD,6,750,50,YELLOW'
24-Oct-16 21:01:34 - GAMEMODE mode=1 action #4 of 'FF_FLASHER,DV_FLIR,FL_FD,6,750,50,YELLOW'
24-Oct-16 21:01:34 - GAMEMODE mode=1 action #5 of 'FF_FLASHER,DV_FLCN,FL_FD,6,750,50,ORANGE'
24-Oct-16 21:01:34 - LAUNCHMODE mode=2 action #0 of 'FF_BUTTON,BUT_LB,BA_OFF,0,0'
24-Oct-16 21:01:35 - Key number #37 is activating device=1 output=22
24-Oct-16 21:01:35 - LEFTFLIPPER mode=1 action #0 of 'FF_DEV,DV_LF,10000'
24-Oct-16 21:01:35 - Link is turning on device #1 for 2000 milliseconds
24-Oct-16 21:01:35 - Key number #37 is de-activating device=1 output=22
24-Oct-16 21:01:36 - LEFTFLIPPER mode=2 action #0 of 'FF_DEV,DV_LF,0'
24-Oct-16 21:01:36 - Link is turning off device #1
24-Oct-16 21:01:38 - Key number #39 is activating device=1 output=27
24-Oct-16 21:01:38 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 21:01:38 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 21:01:38 - Key number #39 is de-activating device=1 output=27
24-Oct-16 21:01:38 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 21:01:38 - Link is turning off device #2
24-Oct-16 21:01:39 - Key number #39 is activating device=1 output=27
24-Oct-16 21:01:39 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 21:01:40 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 21:01:40 - Key number #39 is de-activating device=1 output=27
24-Oct-16 21:01:40 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 21:01:40 - Link is turning off device #2
24-Oct-16 21:01:40 - Key number #39 is activating device=1 output=27
24-Oct-16 21:01:40 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 21:01:41 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 21:01:41 - Key number #39 is de-activating device=1 output=27
24-Oct-16 21:01:41 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 21:01:41 - Link is turning off device #2
24-Oct-16 21:01:42 - Key number #39 is activating device=1 output=27
24-Oct-16 21:01:42 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 21:01:42 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 21:01:42 - RIGHT_SLINGSHOT mode=1 action #0 of 'FF_DEV,DV_RS,-1'
24-Oct-16 21:01:42 - Link is turning on device #4 for 50 milliseconds
24-Oct-16 21:01:43 - RIGHT_SLINGSHOT_FLASHER mode=1 action #0 of 'FF_COLOUR,YELLOW,RGB_TT,50'
24-Oct-16 21:01:43 - RIGHT_SLINGSHOT_FLASHER mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_TT,1,50,100,YELLOW'
24-Oct-16 21:01:43 - There are no OFF actions for RIGHT_SLINGSHOT
24-Oct-16 21:01:43 - Link is turning off device #4
24-Oct-16 21:01:43 - There are no OFF actions for RIGHT_SLINGSHOT_FLASHER
24-Oct-16 21:01:43 - Key number #39 is de-activating device=1 output=27
24-Oct-16 21:01:43 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 21:01:43 - Link is turning off device #2
24-Oct-16 21:01:45 - Key number #39 is activating device=1 output=27
24-Oct-16 21:01:45 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 21:01:45 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 21:01:46 - Key number #39 is de-activating device=1 output=27
24-Oct-16 21:01:46 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 21:01:46 - Link is turning off device #2
24-Oct-16 21:01:46 - Key number #39 is activating device=1 output=27
24-Oct-16 21:01:46 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 21:01:46 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 21:01:46 - Key number #39 is de-activating device=1 output=27
24-Oct-16 21:01:46 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 21:01:46 - Link is turning off device #2
24-Oct-16 21:01:49 - Key number #39 is activating device=1 output=27
24-Oct-16 21:01:49 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 21:01:49 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 21:01:49 - Key number #39 is de-activating device=1 output=27
24-Oct-16 21:01:49 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 21:01:49 - Link is turning off device #2
24-Oct-16 21:01:50 - Key number #37 is activating device=1 output=22
24-Oct-16 21:01:50 - LEFTFLIPPER mode=1 action #0 of 'FF_DEV,DV_LF,10000'
24-Oct-16 21:01:50 - Link is turning on device #1 for 2000 milliseconds
24-Oct-16 21:01:50 - Key number #37 is de-activating device=1 output=22
24-Oct-16 21:01:50 - LEFTFLIPPER mode=2 action #0 of 'FF_DEV,DV_LF,0'
24-Oct-16 21:01:50 - Link is turning off device #1
24-Oct-16 21:01:52 - Key number #39 is activating device=1 output=27
24-Oct-16 21:01:52 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 21:01:52 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 21:01:52 - Key number #39 is de-activating device=1 output=27
24-Oct-16 21:01:52 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 21:01:52 - Link is turning off device #2
24-Oct-16 21:01:55 - Key number #37 is activating device=1 output=22
24-Oct-16 21:01:55 - LEFTFLIPPER mode=1 action #0 of 'FF_DEV,DV_LF,10000'
24-Oct-16 21:01:55 - Link is turning on device #1 for 2000 milliseconds
24-Oct-16 21:01:55 - Key number #37 is de-activating device=1 output=22
24-Oct-16 21:01:55 - LEFTFLIPPER mode=2 action #0 of 'FF_DEV,DV_LF,0'
24-Oct-16 21:01:55 - Link is turning off device #1
24-Oct-16 21:01:56 - Key number #39 is activating device=1 output=27
24-Oct-16 21:01:56 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 21:01:56 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 21:01:57 - LEFT_SLINGSHOT mode=1 action #0 of 'FF_DEV,DV_LS,-1'
24-Oct-16 21:01:57 - Link is turning on device #3 for 50 milliseconds
24-Oct-16 21:01:57 - LEFT_SLINGSHOT_FLASHER mode=1 action #0 of 'FF_COLOUR,YELLOW,RGB_TT,50'
24-Oct-16 21:01:57 - LEFT_SLINGSHOT_FLASHER mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_TT,1,50,100,YELLOW'
24-Oct-16 21:01:57 - Key number #39 is de-activating device=1 output=27
24-Oct-16 21:01:57 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 21:01:57 - There are no OFF actions for LEFT_SLINGSHOT
24-Oct-16 21:01:57 - Link is turning off device #2
24-Oct-16 21:01:57 - Link is turning off device #3
24-Oct-16 21:01:57 - There are no OFF actions for LEFT_SLINGSHOT_FLASHER
24-Oct-16 21:01:58 - Key number #39 is activating device=1 output=27
24-Oct-16 21:01:58 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
24-Oct-16 21:01:58 - Link is turning on device #2 for 2000 milliseconds
24-Oct-16 21:01:58 - Key number #39 is de-activating device=1 output=27
24-Oct-16 21:01:58 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
24-Oct-16 21:01:58 - Link is turning off device #2
24-Oct-16 21:01:58 - LEFT_SLINGSHOT mode=1 action #0 of 'FF_DEV,DV_LS,-1'
24-Oct-16 21:01:58 - Link is turning on device #3 for 50 milliseconds
24-Oct-16 21:01:58 - LEFT_SLINGSHOT_FLASHER mode=1 action #0 of 'FF_COLOUR,YELLOW,RGB_TT,50'
24-Oct-16 21:01:58 - LEFT_SLINGSHOT_FLASHER mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_TT,1,50,100,YELLOW'
24-Oct-16 21:01:58 - There are no OFF actions for LEFT_SLINGSHOT
24-Oct-16 21:01:58 - Link is turning off device #3
24-Oct-16 21:01:58 - There are no OFF actions for LEFT_SLINGSHOT_FLASHER
24-Oct-16 21:01:58 - RIGHT_SLINGSHOT_FLASHER mode=1 action #0 of 'FF_COLOUR,YELLOW,RGB_TT,50'
24-Oct-16 21:01:58 - RIGHT_SLINGSHOT_FLASHER mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_TT,1,50,100,YELLOW'
24-Oct-16 21:01:58 - RIGHT_SLINGSHOT mode=1 action #0 of 'FF_DEV,DV_RS,-1'
24-Oct-16 21:01:59 - Link is turning on device #4 for 50 milliseconds
24-Oct-16 21:01:59 - There are no OFF actions for RIGHT_SLINGSHOT
24-Oct-16 21:01:59 - There are no OFF actions for RIGHT_SLINGSHOT_FLASHER
24-Oct-16 21:01:59 - Link is turning off device #4
24-Oct-16 21:02:00 - There are no OFF actions for GAMEMODE
24-Oct-16 21:02:03 - Key number #39 is activating device=1 output=27
24-Oct-16 21:02:04 - Key number #39 is de-activating device=1 output=27
24-Oct-16 21:02:18 - Activating process disappeared so stopping things
24-Oct-16 21:02:18 - Stopping DOF controllers due to 'Start Each Time' flag

[DDH69]

Hmm, this is getting interesting!  Its all about timing I believe.  Interestingly this implies that its taking your machine >10 seconds to startup FX2.  Does this seem right?  At present I don't think so, but I will remain alert to the fact that it may be something else too.

 

The reason the second method works is because the FX2 process and windows are already established when DOFLinx is started, so the first time it checks for processes and windows they are already there.

 

Anyway, in 4.01 I didn't just change the logic, I also made the time delays adjustable just in case 

 

So from your log with a couple of markers added....

 

24-Oct-16 20:52:23 - Found valid process name of 'Pinball FX2'

24-Oct-16 20:52:23 - Setting FX2 process ID to :6396

POINT A

24-Oct-16 20:52:25 - Activated by process name : 'Pinball FX2'

24-Oct-16 20:52:25 - Serching for FX2 game name

POINT B

24-Oct-16 20:52:35 - Game name = ''

 

At point A DOFLinx waits 2000 milliseconds to give things a chance to startup.  It does this for all detected processes, not just FX2.  You can adjust this with PROCESS_TO_ACTIVE_TIME=  Increasing this is a fairly blunt instrument to sort out this problem as its purely a wait time, no checking takes place while waiting.

 

At point B DOFLinx circles around every 500 milliseconds for 10000 milliseconds looking for a Pinball FX2 windows with the game name in it.  You can adjust the total wait time with FX2_WINDOW_WAIT_TIME=

 

Current suggestion, add FX2_WINDOWS_WAIT_TIME= to your DOFLinx.INI (or send it as a message if you want).  Change it to 20000 and test, then 30000, then 40000, then 50000, 60000 - if it takes more than a minute then I think we've got another issue.  You could make it 120000 or 180000 just to test as well.

 

Let me know how you get on.

[Outhere]

That should do it
Thanks a lot great little program really appreciate all your hard work
I will add that to the DOFLinx.INI And report back tomorrow

I still use nuke launcher with pinball X.... That way it stops at the screen where you can select multiple players, but loads the old-fashion way with the splash screen which takes a while unless you know how to get around the splash screen and still stop at number of players

[DDH69]

OK, that explains the longer load time and makes more sense.  Thanks for explaining.  I feel confident!

[Outhere]

What it's doing now is when you load FX2 it automatically picks the first game in the layout instead of initializing when you pick the game

[DDH69]

What it's doing now is when you load FX2 it automatically picks the first game in the layout instead of initializing when you pick the game

 

Do you mean Pinball FX2 is picking the first game from the grid (1x1), or DOFLinx is detecting the first game in the list as being played when in fact you've chosen a different game?

 

I haven't played around with FX2 selecting a game any way except from PinballX, I suppose I thought its behaviour would be much the same regardless of how you selected the game.  Seems like I'm about to learn!

[DDH69]

OK, I've run up FX2 without the PinballX front end and I see what you mean.  This is caused by the FX2 process being active and FX2 changing its window name each tie you hover over a game before selecting it.

 

I'm looking to see if there is a way to address this.

[Outhere]

DOFLinx is detecting the first game in the list "grid (1x1)"

"grid (1x1)" Is automatically highlighted so that's the game DOFLinx loads

 

25-Oct-16 22:10:57 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
25-Oct-16 22:10:57 - Starting up - version 4.01
25-Oct-16 22:10:57 - 1 LEDWiz device(s) found
25-Oct-16 22:10:58 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
25-Oct-16 22:10:58 - DOFLinx device:1 LEDWiz setup with 32 outputs
25-Oct-16 22:10:58 - 1 FTDI (Sainsmart) device(s) found
25-Oct-16 22:10:58 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
25-Oct-16 22:10:58 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
25-Oct-16 22:10:58 - Reading DOFLinx.INI startup config file details
25-Oct-16 22:10:58 - Reading DOF config file
25-Oct-16 22:11:06 - Found valid process name of 'Pinball FX2'
25-Oct-16 22:11:06 - Setting FX2 process ID to :3788
25-Oct-16 22:11:08 - Activated by process name : 'Pinball FX2'
25-Oct-16 22:11:08 - Serching for FX2 game name
25-Oct-16 22:11:28 - FX2 window with game name found .... extracting from 'Pinball FX2 - The Walking Dead'
25-Oct-16 22:11:28 - Game name = 'TheWalkingDead'
25-Oct-16 22:11:28 - Named process detected and startup commenced
25-Oct-16 22:11:28 - 1 LEDWiz device(s) found
25-Oct-16 22:11:28 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
25-Oct-16 22:11:28 - DOFLinx device:1 LEDWiz setup with 32 outputs
25-Oct-16 22:11:28 - 1 FTDI (Sainsmart) device(s) found
25-Oct-16 22:11:28 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # AH035EZ9
25-Oct-16 22:11:28 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs
25-Oct-16 22:11:28 - Failed to find FX2 configuration file TheWalkingDead.FX2
25-Oct-16 22:11:28 - This process does not have administration rights so can not establish a full FX2 link
25-Oct-16 22:11:28 - Building restricted colour palette for game name = TheWalkingDead
25-Oct-16 22:11:28 - Turning on fixed out Device=1 Output=1
25-Oct-16 22:11:28 - Setting fixed RGB style of 'RANDOM' to colour to index=9999 with name=Random
25-Oct-16 22:11:30 - Right flipper pressed
25-Oct-16 22:11:30 - Key number #37 is activating device=1 output=22
25-Oct-16 22:11:30 - Right flipper lifted
25-Oct-16 22:11:31 - Key number #37 is de-activating device=1 output=22
25-Oct-16 22:11:48 - Activating process disappeared so stopping things
25-Oct-16 22:11:48 - Stopping DOF controllers due to 'Start Each Time' flag
 

[DDH69]

Hmm, not an easy one.  I've tried a number of things for the last couple of hours.  Without some serious surgery this is tough to properly fix.  DOFLinx was designed to handle one game at a time and entry straight to that game from the front end menu.

 

There is one possible work-around.

1. Time how long it takes to get to your single / multi-player setup (I believe the game is selected by this time)

2. Set the PROCESS_TO_ACTIVE_TIME= to the time you came up with plus 5 seconds in milliseconds

 

This will simply pause after the FX2 process is detected for the time you set.  So for the short time while the correct grid position is selected for the game you want, DOFLinx will not be looking for the game name in the window.  If it works it is a real fix to the issue.  Let me know if this provides any joy.  

[Outhere]

That appears to work just fine but it affects all the all systems being detected by the Dof.....
can you make a separate timer for FX 2

[ronaldvg]

For me it still does not work. Hereby log of 3 started games, 2 x BobsBurgers and once Captain America. I set up my process_to_active_time to 20000. 

 

No output for Bobsburgers and only flipperoutput in Captain America after 10 seconds in the game (wait 20000 is too long I guess). Also the trick with alt-tabbing to the File explorer does not work.

 

Log:

 

26-okt-16 20:43:41 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

26-okt-16 20:43:41 - Starting up - version 4.01

26-okt-16 20:43:41 - 1 LEDWiz device(s) found

26-okt-16 20:43:41 - DOFLinx device: 1 Initializing as LEDWiz #8 with ID=0

26-okt-16 20:43:41 - DOFLinx device:1 LEDWiz setup with 32 outputs

26-okt-16 20:43:41 - 1 FTDI (Sainsmart) device(s) found

26-okt-16 20:43:41 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # A6007LGJ

26-okt-16 20:43:41 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs

26-okt-16 20:43:41 - Reading DOFLinx.INI startup config file details

26-okt-16 20:43:41 - Reading DOF config file

26-okt-16 20:44:03 - Game name = 'BobsBurgersPinball'

26-okt-16 20:46:18 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

26-okt-16 20:46:18 - Starting up - version 4.01

26-okt-16 20:46:18 - 1 LEDWiz device(s) found

26-okt-16 20:46:18 - DOFLinx device: 1 Initializing as LEDWiz #8 with ID=0

26-okt-16 20:46:18 - DOFLinx device:1 LEDWiz setup with 32 outputs

26-okt-16 20:46:19 - 1 FTDI (Sainsmart) device(s) found

26-okt-16 20:46:19 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # A6007LGJ

26-okt-16 20:46:19 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs

26-okt-16 20:46:19 - Reading DOFLinx.INI startup config file details

26-okt-16 20:46:19 - Reading DOF config file

26-okt-16 20:46:40 - Game name = 'BobsBurgersPinball'

26-okt-16 20:46:51 - DOF Linx for Pinball Emulators - DOFLinx by DDH69

26-okt-16 20:46:51 - Starting up - version 4.01

26-okt-16 20:46:51 - 1 LEDWiz device(s) found

26-okt-16 20:46:51 - DOFLinx device: 1 Initializing as LEDWiz #8 with ID=0

26-okt-16 20:46:51 - DOFLinx device:1 LEDWiz setup with 32 outputs

26-okt-16 20:46:51 - 1 FTDI (Sainsmart) device(s) found

26-okt-16 20:46:51 - DOFLinx Device: 2 Initializing as FTDI (Sainsmart) #1 serial # A6007LGJ

26-okt-16 20:46:51 - DOFLinx device:2 FTDI (Sainsmart) setup with 8 outputs

26-okt-16 20:46:51 - Reading DOFLinx.INI startup config file details

26-okt-16 20:46:51 - Reading DOF config file

26-okt-16 20:47:12 - Game name = 'CaptainAmerica'

Edited by ronaldvg, 26 October 2016 - 07:14 PM.

[ronaldvg]

Regarding my problem, it is fully solved. I downloaded the configuration files from the DOF configtool again and presto it works. Maybe useful if someone else has this problem.

 

Thanks for your help and double thanks for making this. It just adds so much to the experience of the games.

[DDH69]

That appears to work just fine but it affects all the all systems being detected by the Dof.....
can you make a separate timer for FX 2

 

Yes you are correct it will impact all systems monitored.

 

You could use a SUP_INI file or a message ("DOFLinxMsg PROCESS_TO_ACTIVE_TIME=xxxx" for before and "DOFLinxMsg PROCESS_TO_ACTIVE_TIME=2000" for after) using your 'Launch Before' and 'Launch After' options.  The effect being set this parameter for PinBall FX2 and set it back to default as you leave PinBall FX2 ready for any other DOFLinx monitored system.

Regarding my problem, it is fully solved. I downloaded the configuration files from the DOF configtool again and presto it works. Maybe useful if someone else has this problem.

 

Thanks for your help and double thanks for making this. It just adds so much to the experience of the games.

 

Glad to hear you are up and working.