28 replies to this topic

[lukpcn]

Sorry, missed your post from yesterday.

 

There is still nothing coming to mind for me.  Can you post a DEBUG.LOG and describe when the issue started / stopped during play for that log.  I have no idea what I'm looking for, but then, lets look anyway.

 

I've played for almost half an hour without problems and suddenly

at 05-lis-19 18:16:28.538 - Link is turning off device #1:

and after that there was couple of seconds without the doflinx reporting and triggering any devices.

and it returned to normal at:

05-lis-19 18:16:34.466 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'

 

05-lis-19 18:16:23.419 - LEFTFLIPPER mode=1 action #0 of 'FF_DEV,DV_LF,10000'
05-lis-19 18:16:23.428 - Link is turning on device #1 for 10000 milliseconds
05-lis-19 18:16:23.439 - LEFTFLIPPER mode=1 action #1 of 'FF_DOF,E101,-1'
05-lis-19 18:16:23.470 - LEFTFLIPPER mode=2 action #0 of 'FF_DEV,DV_LF,0'
05-lis-19 18:16:23.485 - LEFTFLIPPER mode=2 action #1 of 'FF_DOF,E101,0'
05-lis-19 18:16:23.502 - Link is turning off device #1
05-lis-19 18:16:23.857 - LEFTFLIPPER mode=1 action #0 of 'FF_DEV,DV_LF,10000'
05-lis-19 18:16:23.866 - Link is turning on device #1 for 10000 milliseconds
05-lis-19 18:16:23.885 - LEFTFLIPPER mode=1 action #1 of 'FF_DOF,E101,-1'
05-lis-19 18:16:24.013 - LEFTFLIPPER mode=2 action #0 of 'FF_DEV,DV_LF,0'
05-lis-19 18:16:24.022 - LEFTFLIPPER mode=2 action #1 of 'FF_DOF,E101,0'
05-lis-19 18:16:24.035 - Link is turning off device #1
05-lis-19 18:16:26.546 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
05-lis-19 18:16:26.555 - Link is turning on device #2 for 10000 milliseconds
05-lis-19 18:16:26.571 - RIGHTFLIPPER mode=1 action #1 of 'FF_DOF,E102,-1'
05-lis-19 18:16:26.688 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
05-lis-19 18:16:26.696 - RIGHTFLIPPER mode=2 action #1 of 'FF_DOF,E102,0'
05-lis-19 18:16:26.707 - Link is turning off device #2
05-lis-19 18:16:28.375 - LEFTFLIPPER mode=1 action #0 of 'FF_DEV,DV_LF,10000'
05-lis-19 18:16:28.384 - Link is turning on device #1 for 10000 milliseconds
05-lis-19 18:16:28.394 - LEFTFLIPPER mode=1 action #1 of 'FF_DOF,E101,-1'
05-lis-19 18:16:28.420 - LEFTFLIPPER mode=2 action #0 of 'FF_DEV,DV_LF,0'
05-lis-19 18:16:28.429 - LEFTFLIPPER mode=2 action #1 of 'FF_DOF,E101,0'
05-lis-19 18:16:28.440 - Link is turning off device #1
05-lis-19 18:16:28.465 - LEFTFLIPPER mode=1 action #0 of 'FF_DEV,DV_LF,10000'
05-lis-19 18:16:28.474 - Link is turning on device #1 for 10000 milliseconds
05-lis-19 18:16:28.489 - LEFTFLIPPER mode=1 action #1 of 'FF_DOF,E101,-1'
05-lis-19 18:16:28.514 - LEFTFLIPPER mode=2 action #0 of 'FF_DEV,DV_LF,0'
05-lis-19 18:16:28.524 - LEFTFLIPPER mode=2 action #1 of 'FF_DOF,E101,0'
05-lis-19 18:16:28.538 - Link is turning off device #1
05-lis-19 18:16:34.466 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
05-lis-19 18:16:34.475 - Link is turning on device #2 for 10000 milliseconds
05-lis-19 18:16:34.494 - RIGHTFLIPPER mode=1 action #1 of 'FF_DOF,E102,-1'
05-lis-19 18:16:34.529 - LEFTFLIPPER mode=1 action #0 of 'FF_DEV,DV_LF,10000'
05-lis-19 18:16:34.537 - Link is turning on device #1 for 10000 milliseconds
05-lis-19 18:16:34.549 - LEFTFLIPPER mode=1 action #1 of 'FF_DOF,E101,-1'
05-lis-19 18:16:34.562 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
05-lis-19 18:16:34.577 - RIGHTFLIPPER mode=2 action #1 of 'FF_DOF,E102,0'
05-lis-19 18:16:34.595 - Link is turning off device #2
05-lis-19 18:16:34.623 - LEFTFLIPPER mode=2 action #0 of 'FF_DEV,DV_LF,0'
05-lis-19 18:16:34.633 - LEFTFLIPPER mode=2 action #1 of 'FF_DOF,E101,0'
05-lis-19 18:16:34.646 - RIGHTFLIPPER mode=1 action #0 of 'FF_DEV,DV_RF,10000'
05-lis-19 18:16:34.661 - Link is turning on device #2 for 10000 milliseconds
05-lis-19 18:16:34.677 - RIGHTFLIPPER mode=1 action #1 of 'FF_DOF,E102,-1'
05-lis-19 18:16:34.695 - Link is turning off device #1
05-lis-19 18:16:34.733 - BALLIN_SENSOR mode=1 action #0 of 'FF_DEV,DV_MC,-1'
05-lis-19 18:16:34.744 - Link is turning on device #6 for 50 milliseconds
05-lis-19 18:16:34.761 - BALLIN_SENSOR mode=1 action #1 of 'FF_DOF,E311,-1'
05-lis-19 18:16:34.778 - RIGHTFLIPPER mode=2 action #0 of 'FF_DEV,DV_RF,0'
05-lis-19 18:16:34.794 - RIGHTFLIPPER mode=2 action #1 of 'FF_DOF,E102,0'
05-lis-19 18:16:34.811 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
05-lis-19 18:16:34.828 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
05-lis-19 18:16:34.844 - Link is turning off device #2
05-lis-19 18:16:34.861 - Link is turning off device #6
05-lis-19 18:16:34.889 - LEFTFLIPPER mode=1 action #0 of 'FF_DEV,DV_LF,10000'
05-lis-19 18:16:34.898 - Link is turning on device #1 for 10000 milliseconds
05-lis-19 18:16:34.910 - LEFTFLIPPER mode=1 action #1 of 'FF_DOF,E101,-1'
05-lis-19 18:16:34.927 - LAUNCHMODE mode=2 action #0 of 'FF_BUTTON,BUT_LB,BA_OFF,0,0'
05-lis-19 18:16:34.943 - LAUNCHMODE mode=2 action #1 of 'FF_DOF,E310,0'
05-lis-19 18:16:34.968 - LEFTFLIPPER mode=2 action #0 of 'FF_DEV,DV_LF,0'
05-lis-19 18:16:34.976 - LEFTFLIPPER mode=2 action #1 of 'FF_DOF,E101,0'
05-lis-19 18:16:34.993 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
05-lis-19 18:16:35.010 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
05-lis-19 18:16:35.027 - Link is turning off device #1
05-lis-19 18:16:35.137 - There are no OFF actions for BALLIN_SENSOR
05-lis-19 18:16:35.557 - There are no OFF actions for GAMEMODE
05-lis-19 18:17:02.565 - Activating process disappeared so stopping things
05-lis-19 18:17:02.609 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
05-lis-19 18:17:02.618 - DOFLinx device:1 Pinscape setup with 22 outputs
05-lis-19 18:17:02.636 - DOFLinx device: 2 Initializing as LEDWiz #8 with ID=0
05-lis-19 18:17:02.650 - DOFLinx device:2 LEDWiz setup with 32 outputs
05-lis-19 18:17:02.660 - 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
 

[DDH69]

At present I have no further suggestions.  While I do not doubt your observations and analysis, I cannot see how it could possibly run then pause, then run again.  I have no theories, nor can I reproduce it.  I will leave this thread open in a tab and continue to think about it.  Sometimes I get a thought in the days following. 

[lukpcn]

At present I have no further suggestions.  While I do not doubt your observations and analysis, I cannot see how it could possibly run then pause, then run again.  I have no theories, nor can I reproduce it.  I will leave this thread open in a tab and continue to think about it.  Sometimes I get a thought in the days following. 

 

Let me know if You'll have some news for me please.

[DDH69]

I certainly will, also let me know if you find any further information, pattern, etc.

[Spitfire]

So have updated to the latest doflinx version and am usings pinballX frontend to play FX2 and now have added FX 3.
However I cant get doflinx to work for fx3 only fx2 works. Is there something different i should be doing to get fx3 working?
I am launching doflinx in pinballX and killing the process after you exit.
Please help?
Thx Joe

[Outhere]

When posting large items like a LOG or ini files

After you paste - highlight it, Then click on this symbol above <> then post

 

Have this ( DEBUG=1 ) in your doflinx.inI file 

Clear you log, then run a game then

Post  your doflinx.inI file and log

Edited by Outhere, 26 November 2019 - 04:53 AM.

[DDH69]

@Spitfire, you will need the FX3 configuration items setup in your DOFLinx.INI file, so

PROCESSES= needs to have FX3 added

There are a couple of paths that need to be setup

Ensure you have loaded the *.FX3 as per one of the paths mentioned above.

[Spitfire]

@DDH69 so i have attached my doflinx.ini and my pinballX settings for FX2 and FX3. Not sure why FX2 works perfectly all solenoids and LEDs and DOFLinx open and closes correctly however FX3 does nothing and DOFLinx stays open on exit. Any thoughts?
Thx Joe

SOLVED thx for the help

Attached Files

•  9ECD2118-C59F-420E-9925-D3CF1CB352DE.jpeg   149.51KB   0 downloads
•  647B4948-D9F9-473C-A110-2548814FDD9D.jpeg   123.96KB   0 downloads
•  B549A9DA-48BA-4753-B777-AF38313003C1.jpeg   144.13KB   0 downloads
•  C4CBCC45-57FD-4AA0-981A-4512206C3E6D.jpeg   244.15KB   0 downloads
•  100BE264-FCE8-4349-A4A0-0F329502BC66.jpeg   89.44KB   0 downloads
•  DB05F8BD-96B0-4358-8D48-05EE010D7C16.jpeg   227.28KB   0 downloads

Edited by Spitfire, 26 November 2019 - 10:31 AM.

[DDH69]

In the first screen shot I can see that you have the PROCESSES= line commented out.  This means that DOFLinx add ones default process to detect being FX2.  You need to tell DOFLinx what processes to monitor for.