30 replies to this topic

[mrl72]

Hey guys

 

So I just got my Teensy controller and have setup my LEDs on my cab. All tests fine. I've configured DO and DOFLinx ini and config files but where I"m lost is what to put in the DOFLinx.INI file for each toy.

 

I have a simple setup for testing: One led strip on the left, one led strip at the back and one on the right. I have them all setup in cabinet.xml. I then went into the online config tool and under my account settings set Number of WS2811 Devices to 1 and everything else to zero (I don't currently have a LEDwiz etc.)

 

Next I went into Combine Toys and created 3 entries:

 

Combo1: RGB Adressable, toy1: PF Left Effects MX, toy2: PF Left Flashers MX

Combo2: RGB Adressable, toy1: PF Right Effects MX, toy2: PF Right Flashers MX

Combo3: RGB Adressable, toy1: PF Backt Effects MX, toy2: PF Back Strobe MX, toy3: PF Back Beacon MX, toy4: PF Back Flashers MX

 

I've no clue if that's right or not as I just selected anything to do with left, right, back.

 

I then went into Port Assignments and assigned:

 

Port 1 - Combo1 

Port 4 - Combo2

Port 7 - Combo3

 

Saved config then generated and saved. It created a zip and I unzipped it to my direct output/config folder. I then renamed the directouputconfig30.ini to directouputconfig.ini.

 

So here's where I'm stuck. What the heck do I put in the DOFLinx.INI file to tell it to use the right MX ports/devices? I can't find anything in any tutorial that talks about this. I don't have anything other than 3 addressable LED strips.

 

Appreciate any help!

 

I can't figure out how to attach files, so here's my DOFLinx.INI:

DIRECTOUTPUTCONFIG=F:\DirectOutput\config\directoutputconfig.ini
PROCESSES=Pinball FX3,Future Pinball,VPinball_9_9_1,Mame64
PATH_FX3=F:\DirectOutput\DOFLinx_FX3\
PATH_MAME=F:\MAME\
MAME_PROCESS=Mame64
QUIT_AFTER_PROCESS=1 
DEBUG=1
AUTO_MX=1

# Turn on the attempt to make a full connection to Future Pinball when it is detected as running
FP_ATTEMPT_LINK=1

# An over-ride to the default setting given this is just being used with Pinball FX3, not FX2, FP or other systems that may require the default delay
PROCESS_TO_ACTIVE_TIME=1

Edited by mrl72, 14 February 2020 - 01:58 AM.

[DDH69]

For DOFLinx the answer is simple, do nothing.  When its all working in DOF it will all flow through.  As you startup DOFLinx (with DEBUG=1) you will see that a Teensy setup has been recognised.  If it works in DOF then it will work for FP and FX via DOFLinx.

 

As you start DOFLinx you should see some action on your MX LEDs, to be precise MX Back Effects.

[mrl72]

For DOFLinx the answer is simple, do nothing.  When its all working in DOF it will all flow through.  As you startup DOFLinx (with DEBUG=1) you will see that a Teensy setup has been recognised.  If it works in DOF then it will work for FP and FX via DOFLinx.

 

As you start DOFLinx you should see some action on your MX LEDs, to be precise MX Back Effects.

 

I'm not getting anything though. Teensy tests fine (Basic test sketch). 

 

Here's what I'm seeing in the logs:

 

DirectOutput.log:

2020.02.14 00:00:31.843	Starting processes
2020.02.14 00:00:31.844	Initializing cabinet
2020.02.14 00:00:31.844	Debug: Initializing output controllers
2020.02.14 00:00:31.849	TeensyStripController LedStripController intialized and updater thread started.
2020.02.14 00:00:31.849	Debug: Output controllers initialized
2020.02.14 00:00:31.850	TeensyStripController LedStripController updater thread  started.
2020.02.14 00:00:31.852	Cabinet initialized
2020.02.14 00:00:31.855	Loading shape definition file: F:\DirectOutput\config\DirectOutputShapes.xml
2020.02.14 00:00:31.890	Framework initialized.
2020.02.14 00:00:31.890	Have fun! :)
2020.02.14 00:00:31.938	Initializing cabinet
2020.02.14 00:00:31.938	Debug: Initializing output controllers
2020.02.14 00:00:31.938	Debug: Output controllers initialized
2020.02.14 00:00:31.938	Cabinet initialized
2020.02.14 00:00:31.952	TeensyStripController LedStripController updater thread  has connected to TeensyStripController LedStripController.
2020.02.14 00:00:33.901	Finishing framework
2020.02.14 00:00:33.902	Finishing cabinet
2020.02.14 00:00:33.904	Debug: Finishing output controllers
2020.02.14 00:00:33.919	TeensyStripController LedStripController updater thread  has disconnected from TeensyStripController LedStripController and will terminate.
2020.02.14 00:00:33.920	TeensyStripController LedStripController finished and updater thread stopped.
2020.02.14 00:00:33.920	Debug: Output controllers finished
2020.02.14 00:00:33.920	Cabinet finished
2020.02.14 00:00:33.920	DirectOutput framework finished.
2020.02.14 00:00:33.920	Bye and thanks for using!
2020.02.14 00:00:33.920	Initializing cabinet
2020.02.14 00:00:33.920	Debug: Initializing output controllers
2020.02.14 00:00:33.920	Debug: Output controllers initialized
2020.02.14 00:00:33.920	Cabinet initialized

Then I load up a DOFLinx supported table in FP, and I watch debug:

14-Feb-20 00:00:29.956 - Starting up - version 7.04
14-Feb-20 00:00:29.963 - For support come and visit the community here http://www.vpforums.org/index.php?showforum=104
14-Feb-20 00:00:29.972 - Pre-Reading DOFLinx.INI startup config file details
14-Feb-20 00:00:30.087 - DEBUG enabled with showing of window True
14-Feb-20 00:00:31.890 - Found Teensy controller named 'LedStripController'
14-Feb-20 00:00:31.912 - Joystick # 1 detected : 12 buttons   DPAD Z-Axis
14-Feb-20 00:00:31.920 - Joystick # 2 detected : 12 buttons   DPAD Z-Axis
14-Feb-20 00:00:31.929 - Joystick # 3 detected : 12 buttons   DPAD Z-Axis
14-Feb-20 00:00:31.940 - !!! No valid output devices for DOFLinx were found ...... sorry about that !!!
14-Feb-20 00:00:31.949 - Reading DOFLinx.INI startup config file details
14-Feb-20 00:00:31.957 - Reading DirectOutputConfig file named F:\DirectOutput\config\directoutputconfig.ini
14-Feb-20 00:00:31.984 - Turning DEBUG off
14-Feb-20 00:00:32.020 - DEBUG enabled with showing of window True
14-Feb-20 00:00:32.038 - Set Debug Privilege = Running as administrator so no action taken
14-Feb-20 00:00:33.061 - Found valid process name of 'Future Pinball'
14-Feb-20 00:00:33.076 - Setting Future Pinball process ID to :5204
14-Feb-20 00:00:33.093 - Activated by process name : 'Future Pinball'
14-Feb-20 00:00:33.104 - Named process detected and startup commenced
14-Feb-20 00:00:33.113 - 64 bit OS detected
14-Feb-20 00:00:33.165 - FP full name=F:\Future Pinball\Future Pinball.exe Size=28547584 bytes, Dated 12/31/2010 1:23:32 PM
14-Feb-20 00:00:33.175 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:00:33.920 - !!! No valid output devices for DOFLinx were found ...... sorry about that !!!
14-Feb-20 00:00:37.001 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:00:39.001 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:00:41.001 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:00:43.001 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:00:46.001 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:00:50.001 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:00:54.001 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:00:59.002 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:01:03.001 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:01:07.001 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:01:11.001 - Starting scan of FP process for DOFLinx code
14-Feb-20 00:01:15.139 - Failed to find a FP table running DOFLinx code and establish a link, checking other methods
14-Feb-20 00:01:15.152 - Using full colour palette
14-Feb-20 00:01:15.164 - 122 colours added to the palette
14-Feb-20 00:01:59.405 - Activating process disappeared so stopping things
14-Feb-20 00:03:41.939 - Shutting down
14-Feb-20 00:03:41.954 - Program clos

Also tested with FX3 but it crashes back to my desktop with:

************** Exception Text **************

System.NullReferenceException: Object variable or With block variable not set.

   at Microsoft.VisualBasic.CompilerServices.Symbols.Container..ctor(Object Instance)

   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateCall(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, Boolean IgnoreReturn)

   at DOFLinx.MainForm.ProcFFB2S(String TheCommand, String TheParams)

   at DOFLinx.MainForm.ProcessAction(Int32 ActNum, Byte ActMode)

   at DOFLinx.MainForm.CheckFX3MemoryTriggers()

   at DOFLinx.MainForm.TimerKeyCheck_Tick(Object sender, EventArgs e)

   at System.Windows.Forms.Timer.OnTick(EventArgs e)

   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Log:

14-Feb-20 00:16:25.600 - Found valid process name of 'Pinball FX3'
14-Feb-20 00:16:25.610 - Setting FX3 process ID to :13468
14-Feb-20 00:16:25.628 - Activated by process name : 'Pinball FX3'
14-Feb-20 00:16:25.638 - Named process detected and startup commenced
14-Feb-20 00:16:26.167 - FX3 EXE name=F:\SteamLibrary\steamapps\common\Pinball FX3\Pinball FX3.exe Size=11022480 bytes, Dated 2/5/2020 2:55:07 PM
14-Feb-20 00:16:26.178 - Applying memory offsets for FX3 version circa 10/12/19
14-Feb-20 00:16:26.190 - FX3 full link active
14-Feb-20 00:16:26.201 - Using full colour palette
14-Feb-20 00:16:26.211 - 122 colours added to the palette
14-Feb-20 00:16:44.220 - Loading FX3 configuration file F:\DirectOutput\DOFLinx_FX3\ALL_PRE.FX3
14-Feb-20 00:16:44.237 - Loading FX3 configuration file F:\DirectOutput\DOFLinx_FX3\Jaws.FX3
14-Feb-20 00:16:45.789 - Loading FX3 configuration file F:\DirectOutput\DOFLinx_FX3\ALL_POST.FX3
14-Feb-20 00:16:45.796 - B2S file not found : Jaws
14-Feb-20 00:16:45.816 - Building restricted colour palette for game name = Jaws
14-Feb-20 00:16:45.824 - 8 colours added to the palette
14-Feb-20 00:16:45.831 - Cabinet Mode = 0   Backglass Mode = 0
14-Feb-20 00:16:45.853 - There are no OFF actions for GAMEMODE
14-Feb-20 00:16:47.356 - GAMEMODE mode=1 action #0 of 'FF_COLOUR,BLACK,RGB_DF,0'
14-Feb-20 00:16:47.365 - GAMEMODE mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_FD,6,750,100,TEAL'
14-Feb-20 00:16:47.375 - GAMEMODE mode=1 action #2 of 'FF_FLASHER,DV_FLOR,FL_FD,6,750,100,DODGER_BLUE'
14-Feb-20 00:16:47.381 - GAMEMODE mode=1 action #3 of 'FF_FLASHER,DV_FLIL,FL_FD,6,750,100,TEAL'
14-Feb-20 00:16:47.389 - GAMEMODE mode=1 action #4 of 'FF_FLASHER,DV_FLIR,FL_FD,6,750,100,DODGER_BLUE'
14-Feb-20 00:16:47.398 - GAMEMODE mode=1 action #5 of 'FF_FLASHER,DV_FLCN,FL_FD,6,750,100,WHITE'
14-Feb-20 00:16:47.407 - GAMEMODE mode=1 action #6 of 'FF_DOF,E424,-1'
14-Feb-20 00:16:47.418 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'
14-Feb-20 00:16:47.428 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'
14-Feb-20 00:16:47.970 - There are no ON actions for LAUNCHBALL
14-Feb-20 00:16:48.095 - LAUNCHBALL mode=2 action #0 of 'FF_DEV,DV_MR,-1'
14-Feb-20 00:16:48.103 - LAUNCHBALL mode=2 action #1 of 'FF_DOF,E132,-1'
14-Feb-20 00:16:48.110 - LAUNCHBALL mode=2 action #2 of 'FF_B2S,B2SSTARTANIMATION,TITLE'
14-Feb-20 00:16:48.868 - There are no OFF actions for GAMEMODE
14-Feb-20 00:17:53.466 - Shutting down
14-Feb-20 00:17:53.488 - Program close

And... when exiting FP DOFLinx crashes with:

 

See the end of this message for details on invoking 

just-in-time (JIT) debugging instead of this dialog box.

 

************** Exception Text **************

System.NullReferenceException: Object variable or With block variable not set.

   at Microsoft.VisualBasic.CompilerServices.Symbols.Container..ctor(Object Instance)

   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateCall(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, Boolean IgnoreReturn)

   at DOFLinx.MainForm.DoStop()

   at DOFLinx.MainForm.SteamTimer_Tick(Object sender, EventArgs e)

   at System.Windows.Forms.Timer.OnTick(EventArgs e)

   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

 

************** Loaded Assemblies **************

mscorlib

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4121.0 built by: NET48REL1LAST_C

 

----------------------------------------

DOFLinx

    Assembly Version: 1.0.0.0

    Win32 Version: 5.0.0.0

 

----------------------------------------

Microsoft.VisualBasic

    Assembly Version: 10.0.0.0

    Win32 Version: 14.8.3761.0 built by: NET48REL1

 

----------------------------------------

System

    Assembly Version: 4.0.0.0

    Win32 Version: 4.8.4001.0 built by: NET48REL1LAST_C

 

----------------------------------------

System.Core

Edited by mrl72, 14 February 2020 - 05:20 AM.

[mrl72]

FYI, I do get the LEDs lighting up when starting DOFLinx.

 

For FP, I was able to get it to recognize one table (Flash Gordon), but most DOFLinx tables I've downloaded aren't recognized. However, just as the table loads it crashes out again with the same error I posted above.

Edited by mrl72, 14 February 2020 - 05:47 AM.

[Outhere]

All the lighting works in Visual Pinball games?

 

Lots of info for FP
https://www.vpforums...=38170&p=381730

[mrl72]

All the lighting works in Visual Pinball games?

 

Lots of info for FP
https://www.vpforums...=38170&p=381730

 

Couldn't tell you, I don't have it installed. I tried installing it once and got so many errors, missing rom files, memory errors and what not I gave up.

Edited by mrl72, 14 February 2020 - 01:15 PM.

[Outhere]

Post your DOFLinx.ini file but don't need the way bottom

[mrl72]

Here you go:

 

(Note, I just installed VPX and no lights). And quitting out of VPX results in same crash message "Object variable or With block variable not set".

DIRECTOUTPUTCONFIG=F:\DirectOutput\config\directoutputconfig.ini
DIRECTOUTPUTGLOBAL=F:\DirectOutput\config\GlobalConfig_b2sServer.xml
PROCESSES=Pinball FX3,Future Pinball,VPinball_9_9_1,Mame64,VPinballX
PATH_FX3=F:\DirectOutput\DOFLinx_FX3\
PATH_MAME=F:\MAME\
MAME_PROCESS=Mame64
QUIT_AFTER_PROCESS=1 
DEBUG=1
AUTO_MX=1

# Turn on the attempt to make a full connection to Future Pinball when it is detected as running
FP_ATTEMPT_LINK=1

# An over-ride to the default setting given this is just being used with Pinball FX3, not FX2, FP or other systems that may require the default delay
PROCESS_TO_ACTIVE_TIME=1

(everything below is GAME_COLOR stuff)

Edited by mrl72, 14 February 2020 - 02:56 PM.

[Outhere]

I would say get VP running 1st

Is this a complete new set up or you have been running this computer for a while?
What version of windows are you using?
 

[mrl72]

I would say get VP running 1st

Is this a complete new set up or you have been running this computer for a while?
What version of windows are you using?
 

 

New "clean" setup using all the recent versions...

 

Windows 10.

DirectOutput Version 3.1.7011.27968, built 2019.03.13 15:32.

DOFLinx version 7.04.

Latest .NET framework.

Teensy 3.2 with Octoboard (tested).

FP 1.9.1.

BAM_Version: BAM v1.5-275 (1 13 2020)  renderer: GeForce GTX 1070/PCIe/SSE2.

VPX10.6.0 Final.

Pinball FX3.

Edited by mrl72, 14 February 2020 - 04:20 PM.

[Outhere]

For being a brand new Set up I have to wonder why It's crashing

Almost sounds like something didn't Load right - or

If you have anti virus running you may have to turn it off or put in exclusions for certain folders

[mrl72]

For being a brand new Set up I have to wonder why It's crashing

Almost sounds like something didn't Load right - or

If you have anti virus running you may have to turn it off or put in exclusions for certain folders

 

I'm all out of ideas. The fact that it crashes non-stop means something isn't right and I don't think my installation is any different than in the tutorials. I also have all relevant folders added to my virus scanner exception list.

 

This is the crash that happens as soon as the ball is launched from either FX3 or FP. Maybe DDH69 can figure out what this means.

 

System.NullReferenceException: Object variable or With block variable not set.

   at Microsoft.VisualBasic.CompilerServices.Symbols.Container..ctor(Object Instance)

   at Microsoft.VisualBasic.CompilerServices.NewLateBinding.LateCall(Object Instance, Type Type, String MemberName, Object[] Arguments, String[] ArgumentNames, Type[] TypeArguments, Boolean[] CopyBack, Boolean IgnoreReturn)

   at DOFLinx.MainForm.ProcFFB2S(String TheCommand, String TheParams)

   at DOFLinx.MainForm.ProcessAction(Int32 ActNum, Byte ActMode)

   at DOFLinx.MainForm.CheckFX3MemoryTriggers()

   at DOFLinx.MainForm.TimerKeyCheck_Tick(Object sender, EventArgs e)

   at System.Windows.Forms.Timer.OnTick(EventArgs e)

   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

 

And the last few entries in the log when this happens (was playing FX3 Jaws):

 

14-Feb-20 14:34:33.318 - GAMEMODE mode=1 action #0 of 'FF_COLOUR,BLACK,RGB_DF,0'

14-Feb-20 14:34:33.322 - GAMEMODE mode=1 action #1 of 'FF_FLASHER,DV_FLOL,FL_FD,6,750,100,TEAL'

14-Feb-20 14:34:33.324 - GAMEMODE mode=1 action #2 of 'FF_FLASHER,DV_FLOR,FL_FD,6,750,100,DODGER_BLUE'

14-Feb-20 14:34:33.325 - GAMEMODE mode=1 action #3 of 'FF_FLASHER,DV_FLIL,FL_FD,6,750,100,TEAL'

14-Feb-20 14:34:33.326 - GAMEMODE mode=1 action #4 of 'FF_FLASHER,DV_FLIR,FL_FD,6,750,100,DODGER_BLUE'

14-Feb-20 14:34:33.329 - GAMEMODE mode=1 action #5 of 'FF_FLASHER,DV_FLCN,FL_FD,6,750,100,WHITE'

14-Feb-20 14:34:33.330 - GAMEMODE mode=1 action #6 of 'FF_DOF,E424,-1'

14-Feb-20 14:34:34.143 - LAUNCHMODE mode=1 action #0 of 'FF_BUTTON,BUT_LB,BA_FL,10000,500'

14-Feb-20 14:34:34.146 - LAUNCHMODE mode=1 action #1 of 'FF_DOF,E310,-1'

14-Feb-20 14:34:34.401 - SENSOR_LOOP_SHIP_RIGHT mode=1 action #0 of 'FF_B2S,B2SSTARTANIMATION,JACKPOT'

 

And not sure if this gives any clues, but right-clicking in the debug window and selecting Test Device throws this error:

 

************** Exception Text **************

System.InvalidOperationException: An error occurred creating the form. See Exception.InnerException for details.  The error is: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object.

   at DOFLinx.TestDevice.UpdatePorts()

   at DOFLinx.TestDevice.TheDevice_ValueChanged(Object sender, EventArgs e)

   at System.Windows.Forms.NumericUpDown.OnValueChanged(EventArgs e)

   at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)

   at System.Windows.Forms.NumericUpDown.set_Minimum(Decimal value)

   at DOFLinx.TestDevice.InitializeComponent()

   at DOFLinx.TestDevice..ctor()

   --- End of inner exception stack trace ---

   at DOFLinx.My.MyProject.MyForms.Create__Instance__[T](T Instance)

   at DOFLinx.My.MyProject.MyForms.get_TestDevice()

   at DOFLinx.MainForm.PopTestDevice_Click(Object sender, EventArgs e)

   at System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)

   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)

   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)

   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)

   at System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)

   at System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)

   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)

   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)

   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)

   at System.Windows.Forms.Control.WndProc(Message& m)

   at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

   at System.Windows.Forms.ToolStrip.WndProc(Message& m)

   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Edited by mrl72, 14 February 2020 - 08:19 PM.

[Outhere]

I'm far from an expert but maybe you have to Reformat the hard and start over

[mrl72]

I've tried running off both my system C drive and a different internal SSD drive. Same crashes.

 

When running FP it only crashes on exit, so I can at least open a table and play. From the log:

 

14-Feb-20 16:01:35.770 - Setting Future Pinball process ID to :10148

14-Feb-20 16:01:35.784 - Activated by process name : 'Future Pinball'

14-Feb-20 16:01:35.790 - Named process detected and startup commenced

14-Feb-20 16:01:35.794 - 64 bit OS detected

14-Feb-20 16:01:35.827 - FP full name=F:\Future Pinball\Future Pinball.exe Size=28547584 bytes, Dated 12/31/2010 1:23:32 PM

14-Feb-20 16:01:35.831 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:01:37.002 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:01:37.020 - !!! No valid output devices for DOFLinx were found ...... sorry about that !!!

14-Feb-20 16:01:38.002 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:01:40.001 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:01:43.001 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:01:47.001 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:01:52.001 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:01:57.001 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:02:02.001 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:02:07.001 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:02:12.001 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:02:17.002 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:02:22.002 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:02:27.002 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:02:32.002 - Starting scan of FP process for DOFLinx code

14-Feb-20 16:02:35.955 - FP table running DOFLinx code found and link established

14-Feb-20 16:02:38.762 - Using full colour palette

14-Feb-20 16:02:38.762 - 122 colours added to the palette

 

So it's finding the DOFLinx supported table, but I'm getting no activity on the LED strips.

 

From the directoutput.log at the same timestamp:

 

2020.02.14 16:02:38.761 Framework initialized.

2020.02.14 16:02:38.761 Have fun!

2020.02.14 16:02:38.832 TeensyStripController TeensyStripController updater thread  has connected to TeensyStripController TeensyStripController.

Edited by mrl72, 14 February 2020 - 09:07 PM.

[DDH69]

FYI, I do get the LEDs lighting up when starting DOFLinx.

 

For FP, I was able to get it to recognize one table (Flash Gordon), but most DOFLinx tables I've downloaded aren't recognized. However, just as the table loads it crashes out again with the same error I posted above.

 

LEDs lighting up as DOFLinx started = good.  This means that DOFLinx can access the necessary parts of DOF and load the "DOFLinx" ROM and run effect #99.  We want all of this.

 

Recognising a table for FP is good.  Not recognising any others, not so good.  Probably worth having a tinker with FP_LINK_WAIT_TIME=  Have a read in the guide, but as a start the default is 40000 (40 seconds from when DOFLinx sees FP start), perhaps try FP_LINK_WAIT_TIME=80000 and see if more tables get detected.  This parameter is there because FP takes different amounts of time to load tables on different cabinets (CPU speed, HDD speed, other stuff)

 

I noticed this

!!! No valid output devices for DOFLinx were found ...... sorry about that !!!

 

What output devices do you have in your setup?  Obviously you have a Teensy for addressable LEDs, what do you have for the toys?  DOFLinx will run with no output devices or at least one supported output device and a Teensy for addressable LEDs.

[mrl72]

I'm currently using FP_LINK_WAIT_TIME=120000 but I also tried 46000. Is it the time it takes to load up in the editor or the time it takes to render the table properly? If the latter, it takes about 35 seconds for the few I've been testing.

 

With VP I can load tables fine but aside from seeing "Activated by process name: VPinballX" in the debug, nothing else is happening with the LEDs. I'm kinda new to VP so not sure if you have to enabled DOF somewhere else. I did see some configurable options in VP's preferences screen so I turned them all on. Didn't see anything for addressables though.

 

I have no toys, just the addressable LED strips. Are you saying I need at least one toy in addition to the strips? I thought I had read in one of the guides it works without any toys?

Edited by mrl72, 15 February 2020 - 12:17 AM.

[DDH69]

The time starts from when the FP process is first detected.  So if you are loading and running a table manually this is very hard.  Its really designed for a table to be loaded from a front end like PinballX so the time from the FP process to table being loaded is as short as it can be.  Of course you can blow the time way out to try and cover the starting of FP, manual selection of a table, then the actual load itself.

 

Yes you can run no toys by adding DISABLEDOF=YES to the command line when starting DOFLinx, but of course addressable LEDs are a toy, so this will allow you to use active back glasses in FX, but will stop addressable LEDs.  I think the key for you is what output device you have other than a Teensy.  If there is no supported output device for a toy, then the only way to run DOFLinx includes with no addressable LED support.

[mrl72]

Thanks. Wish I knew that beforehand. Most of the addressable LED tutorials didnt mention this.

Since I dont have any other toys it seems the fastest and cheapest approach is to go with a LEDWiz clone using a flashed Arduino. I do have some LED buttons on my cab so I guess this is as good a time as any to get a proper LED controller in there!

Cheers.

Edited by mrl72, 15 February 2020 - 02:15 AM.

[DDH69]

I'm not familiar with using Arduino LEDWiz clones.  Sounds like its not presenting to DOF as  LEDWiz, rather an Arduino that has LEDWiz equivalent options.

 

A KL25Z setup as a Pinscape is cheap and wonderful.  Lots of options with that.

[mrl72]

Thanks Ill check that out. BTW Im assuming the crashes are due to it not having any outputs/toys defined and its crashing because it cant find them?