Jump to content



Photo
* * * * * 1 votes

DOFLinx 8.01 not reading Path_FX


  • Please log in to reply
3 replies to this topic

#1 Everly

Everly

    Hobbyist

  • Members
  • PipPip
  • 32 posts

  • Flag: ---------

  • Favorite Pinball: Swords of Fury

Posted 27 April 2024 - 02:38 PM

Moving this issue into a specific thread, hopefully it will help anyone else with this issue.

 

I worked on getting my cab up to a 64 bit system.  I have my 64 bit DOF configuration working correctly.  I can launch a VPX table with either the 32 or 64 bit exe and my feedback solenoids and MX lighting effects all work so I know my 64 bit DOF is operational.

 

I've edited the DOFLinx.ini in location of C:\DirectOutputx86 to include the following parameters and they match my file structure

 

PATH_FX=C:\DirectOutputX86\FX\

 

PATH_FX_B2S=C:\DirectOutputX86\FX_B2S\

 

My process line looks like this...

 

PROCESSES=Pinball FX3,Pinball FX2,Future Pinball,mamelayplus,LaunchBingoGameRoom,PinballFX-Win64-Shipping

 

I placed the DOFLinxTrigger.dll in the folder with the PinballFX-Win64-Shipping.exe and confirmed it is unblocked.

 

I enabled DOFLinx within Pinball FX.

 

I'm using Sorcerer's Lair as my test table as I have it in both FX3 and FX.  The FX3 version is running correctly with all bumpers, flippers and lights active.  The FX version appears to be running in "Fall Back" mode simply activating the flipper contactors.  My Log shows a couple suspicious clues highlighted in BOLD.  The obvious one is why is the system running version 7.44?  For clarity, this DOFLinx.INI file is the one residing in C:\DirectOutputx86, where the DOFLinx.exe file is located as well.  I see there are Doflix.exe files in the 32 bit and 64 bit folders that were created in the DirectOutputx86 folder but I'm not sure what, if anything, I am supposed to do with those.

 

27-Apr-24 10:06:57.549 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
27-Apr-24 10:06:57.574 - Starting up - version 7.44
27-Apr-24 10:06:57.586 - For support come and visit the community here http://www.vpforums....p?showforum=104
27-Apr-24 10:06:57.599 - Pre-Reading DOFLinx.INI startup config file details
27-Apr-24 10:06:57.713 - DEBUG enabled with showing of window True
27-Apr-24 10:07:03.040 - Found Teensy controller named 'LEDStripController'
27-Apr-24 10:07:03.058 - Joystick # 1 detected : 32 buttons   Z-Axis
27-Apr-24 10:07:03.079 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
27-Apr-24 10:07:03.092 - DOFLinx device:1 Pinscape setup with 65 outputs
27-Apr-24 10:07:03.104 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=0
27-Apr-24 10:07:03.117 - DOFLinx device:2 LEDWiz setup with 32 outputs
27-Apr-24 10:07:03.133 - Reading DOFLinx.INI startup config file details
27-Apr-24 10:07:03.145 - Turning DEBUG off
27-Apr-24 10:07:03.205 - DEBUG enabled with showing of window True
27-Apr-24 10:07:03.209 - Reading DirectOutputConfig file named c:\DirectOutputX86\config\directoutputconfig30.ini
27-Apr-24 10:07:03.264 - The parameter 'PATH_FX' with data 'C:\DirectOutputX86\FX\' was not processed.  Realtime flag=False Process active flag=False
27-Apr-24 10:07:03.273 - The parameter 'PATH_FX_B2S' with data 'C:\DirectOutputX86\FX_B2S\' was not processed.  Realtime flag=False Process active flag=False

27-Apr-24 10:07:03.299 - Turning on checking for nudge during basic keybaord checking
27-Apr-24 10:07:03.583 - Set Debug Privilege = Set OK
27-Apr-24 10:07:05.041 - Stopping ROM
27-Apr-24 10:07:05.101 - DOFLinx device: 1 Initializing as Pinscape #1 with name=Pinscape Controller
27-Apr-24 10:07:05.105 - DOFLinx device:1 Pinscape setup with 65 outputs
27-Apr-24 10:07:05.119 - DOFLinx device: 2 Initializing as LEDWiz #1 with ID=0
27-Apr-24 10:07:05.135 - DOFLinx device:2 LEDWiz setup with 32 outputs
27-Apr-24 10:07:08.906 - Turning DEBUG off

 

This seems to be the same issue BJenkins68 is having, but I have confirmed the parameters I've added are in the DOFLinx.INI file in C:\DirectOutputX86.

 

Thanks in advance for the help.


Edited by Everly, 27 April 2024 - 04:18 PM.

May your Kickbacks always be active


#2 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,078 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 27 April 2024 - 10:17 PM

You have identified the correct issue from the first highlighted line in the log

 

27-Apr-24 10:06:57.574 - Starting up - version 7.44

 

You have not managed to update DOFLinx.EXE to the latest version and are still running V7.44

 

Do you have DOFLinx in more than one folder?  Perhaps do a search on your drive for DOFLinx.exe


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here

#3 Everly

Everly

    Hobbyist

  • Members
  • PipPip
  • 32 posts

  • Flag: ---------

  • Favorite Pinball: Swords of Fury

Posted 28 April 2024 - 02:11 PM

So that was a weird one.  I followed the directions (copied the contents of the 64 bit folder over my Doflinx platform in C:\DirectOutputx86) but something must not have copied right.  So I went thru the process a second time and now the log shows me running V8.01 and it is processing Path_FX correctly.  I have flippers, bumpers, and lights on Sorcerer's Lair running in PinballFX now.  :tup:

 

I ran How to Train your Dragon and got similar results, so that is a win.  A couple quick questions...

 

1.  I ran Swords of Fury and I had flippers and bumpers, but no lights.  I know we are just getting off of the ground on FX files, but wanted to ask is that would be expected with certain tables.

 

2.  On FX3 my plunger works but it isn't on FX, I need to use my launch button to launch the ball.  Is that also to be expected at this point of the game?

 

I remember reading that FX files would be in plain text so we can customize them.  Is there a guide somewhere about how to write them?  If so I'll try my hand at adding lights to Swords of Fury.

 

Thanks again for all of your help and work setting up DOFXLinx...see what I did there? 


Edited by Everly, 28 April 2024 - 02:12 PM.

May your Kickbacks always be active


#4 DDH69

DDH69

    Pinball Wizard

  • Platinum Supporter
  • 3,078 posts
  • Location:DOFLinx HQ, Adelaide

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 29 April 2024 - 09:01 AM

So that was a weird one.  I followed the directions (copied the contents of the 64 bit folder over my Doflinx platform in C:\DirectOutputx86) but something must not have copied right.  So I went thru the process a second time and now the log shows me running V8.01 and it is processing Path_FX correctly.  I have flippers, bumpers, and lights on Sorcerer's Lair running in PinballFX now.  :tup:

 

I ran How to Train your Dragon and got similar results, so that is a win.  A couple quick questions...

 

1.  I ran Swords of Fury and I had flippers and bumpers, but no lights.  I know we are just getting off of the ground on FX files, but wanted to ask is that would be expected with certain tables.

 

2.  On FX3 my plunger works but it isn't on FX, I need to use my launch button to launch the ball.  Is that also to be expected at this point of the game?

 

I remember reading that FX files would be in plain text so we can customize them.  Is there a guide somewhere about how to write them?  If so I'll try my hand at adding lights to Swords of Fury.

 

Thanks again for all of your help and work setting up DOFXLinx...see what I did there? 

 

Good to hear that you're getting going.  In answer to your questions;

1. Yes, expected with some tables.  The All_Pre.fx should get most of the essentials running, but some tables differ and this will be sorted out with the table.fx file

2. Oh shit  :facepalm: clean forgot to write that part!  I'll get V8.02 out for the SSF and look at that over the next week'ish

3.Yes table.fx will be plain text.  The real problem is that I don't have all the table events from Zen yet (still coming), and that's why I haven't done many table.fx files.  You are welcome to write one for yourself, but I think you might struggle for now.  Once the event info comes through I'l be happy to get the help, but until then there are only so many I want to revisit.


DOFLinx
Contributions for equipment to help with ongoing DOFLinx development can be made here