15 replies to this topic

[jogster]

Hey DDH69,

thank you for your post over at gopinball, I gave DOFLinx another effort on my own, but, obviously for lack of skills, I cannot really get the programme to work in connection with FP. Before I start with my troubles, let me say that I think you are doing a great job here with this tool, for it really provides the opportunity of a significant "bling" factor for FP. So, big thanks for you time and effort in this.

 

I am running a Future Pinball designated cabinet with LEDWiz support and real DMD. Frontend is PinballX. I am running my I5rig on a Win 7 Ultimate 64bit system. Everything, PinX, FP, BAM runs absolutely stable with LEDWiz support and Real DMD. When I ventured on gopinball for the occasional visit, I came across Terry's mod for Star Trek - and now Aliens - then saw your mods, and was absolutely stunned by and fascinated with the possilities of this nice add-on. I immediately wanted to install DOFLinx and give it a spin. After some talking with and help from Terry, this is where I am at.

 

I run Future Pinball via BAM. So, my Future Pinball.exe is a renamed FPLoader.exe that is provided via BAM. BAM works nicely without DOFLinx.

 

All files are run as administrator.

 

After some initial troubles, this is what I did:

 

1) installed VPX all in one installer (Visual Pinball 10) and setup the obligatory B2S Server in c:\visual pinball

2) installed Direct Output Framework R3 (DOF R3) (from your link) in c:\DirectOutput and the respective .ini in the subfolder \config

3) checked whether the directoutputconfig.ini is setup correctly via the PinballX plugin (this works, so I think the above steps were done correctly); I now have flasher signals while browsing tables in PinX.

4) installed DOFLinx 3.0.5 in c:\directoutput and put all the necessary files wherey the should go. When I start a DOFed table in FP without DOFLinx active, everything works, but, of course, no bling support for my flashers.

5) created my own DOFLinx.ini as follows (I only have 5 RGB flashers in my cab; forcefeedback to be added soonish)

 

This is what my .ini looks like:

####
# 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=c:\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=Future Pinball

# Which DOF Controller output for the flipper solenoids / contactors
# L_FLIPPER_OUTPUT=130
# R_FLIPPER_OUTPUT=125
# 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=A0
# R_FLIPPER_KEY=A1
# 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=5000
# 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=109
# 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
# The button(s) to turn on when DOFLinx starts, ie the exit button LED
# BUTTONS_ON=102 104
# Make the "1" (31) key (Start in VP) pulse LEDWiz 120 and "4" (34) to pulse controller/output 121
# KEY_TO_OUTPUT=32 101 35 106 36 105
# 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_FLOL=130,131,132
LINK_FLIL=124,125,126
LINK_FLCN=121,122,123
LINK_FLOR=127,128,129
LINK_FLIR=103,104,105

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

#####
# Game specific colours in the formnat of a CSV of Game Name,Colour#1,Colour#2 - colours as they appear in your directoutputconfig
# Thanks to Vizzini here is a great starting list for Pinball FX2
#####
GAME_COLOUR=Alien:IsolationPinball,Medium_Blue,Lime,Dodger_Blue,Lime_Green
GAME_COLOUR=Alien vs. Predator Pinball,Medium_Blue,Lime_Green,Dodger_Blue,Yellow_Green
GAME_COLOUR=AliensPinball,Medium_Blue,Dark_Golden_Rod,Dodger_Blue
GAME_COLOUR=American Dad! Pinball,Medium_Blue,Lime_Green,Dodger_Blue,Yellow_Green
GAME_COLOUR=Marvel's Ant-Man,Medium_Blue,Dark_Red,Dodger_Blue
GAME_COLOUR=Archer Pinball,Medium_Blue,Yellow,Dodger_Blue,Blue_Violet
GAME_COLOUR=Marvel's The Avengers,Blue,Dark_Red,Dodger_Blue,Gold
GAME_COLOUR=Marvel's Avengers: Age of Ultron,Dark_Red,Dodger_Blue,Lime_Green,Light_Salmon,Cyan
GAME_COLOUR=Biolab,Dark_Red,Lime,Blue,Cyan,Blue_Violet,Yellow
GAME_COLOUR=Blade,Blue,Blue_Violet,Salmon
GAME_COLOUR=Boba Fett,Lime,Golden_Rod,Blue_Violet
GAME_COLOUR=Bob'sBurgers Pinball,Medium_Blue,Lime_Green,Dark_Red,Dodger_Blue,Yellow_Green
GAME_COLOUR=Captain America,Blue,Dark_Red,Dodger_Blue,Gold
GAME_COLOUR=CastleStorm,Blue,Gold,Lime,Dodger_Blue,Orange,Lime_Green
GAME_COLOUR=Civil War,Blue,Dark_Red,Dodger_Blue,Light_Salmon
GAME_COLOUR=STAR WARS: DARTH VADER,Light_sky_blue,Dark_Red,Cyan
GAME_COLOUR=Deadpool,Dark_Red,Blue,Medium_slate_blue,Dodger_Blue
GAME_COLOUR=Doctor Strange,Dark_Red,Blue,Gold,Lime_Green,Dark_Violet,Orange,Dodger_Blue,Lime,Medium_Slate_Blue
GAME_COLOUR=Star Wars Pinball: Droids,Medium_Blue,Yellow,Orange,Navy,Gold,Orange_Red
GAME_COLOUR=Earth Defense,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime
GAME_COLOUR=El Dorado,Orange,Lime_Green,Yellow,Coral,Lime,Yellow_Green,Cyan
GAME_COLOUR=Epic Quest,Lime_Green,Dodger_Blue,Yellow_Green,Cyan
GAME_COLOUR=Star Wars Pinball: Episode IV A New Hope,Cyan,Golden_Rod,Dodger_Blue,Yellow
GAME_COLOUR=Star Wars: Episode V The Empire Strikes Back,Medium_Blue,Yellow,Dark_Red,Dodger_Blue
GAME_COLOUR=Star Wars: Episode VI Return of the Jedi,Slate_Blue,Golden_Rod,Medium_Blue,Lime_Green,Dodger_Blue,Yellow
GAME_COLOUR=Excalibur,Dark_Red,Blue,Lime,Dodger_Blue,Cyan
GAME_COLOUR=Family Guy Pinball,Dodger_Blue,Lime_Green,Salmon,Dark_Violet,Yellow_Green
GAME_COLOUR=Fantastic Four,Blue,Yellow,Dodger_Blue,Orange_Red
GAME_COLOUR=FearItself,Dark_Red,Blue,Yellow,Lime,Dark_Violet,Orange
GAME_COLOUR=Super League - Zen Studios F.C.,Lime_Green,Orange,Lime,Yellow,Red
GAME_COLOUR=Ghost Rider,Dodger_Blue,White,Yellow,Light_Salmon,Orange_Red
GAME_COLOUR=Guardians of the Galaxy,Dodger_Blue,Orange,Medium_Purple
GAME_COLOUR=Star Wars Pinball: Han Solo,Dodger_Blue,Royal_Blue,Antique_White
GAME_COLOUR=IRON MAN,Blue,Dark_Red,Dodger_Blue,Gold
GAME_COLOUR=Mars,Blue,Yellow,Deep_sky_blue,Gold
GAME_COLOUR=Star Wars Pinball: Masters of the Force,Medium_Blue,Salmon,Dodger_Blue,Purple,Cyan,Dark_Red
GAME_COLOUR=Star Wars Pinball: Might of the First Order,Light_sky_blue,Dodger_Blue,Dark_Red,Cyan
GAME_COLOUR=Moon Knight,Dodger_Blue,Blue,Cyan,Royal_Blue
GAME_COLOUR=Ms.SplosionMan,Dodger_Blue,Pink,Medium_Blue,Purple,Royal_Blue
GAME_COLOUR=Paranormal,Lime_Green,Dodger_Blue,Yellow_Green
GAME_COLOUR=Pasha,Dark_Violet,Golden_Rod,Dodger_Blue
GAME_COLOUR=Plants VS. Zombies,Lime_Green,Yellow_Green,Dodger_Blue
GAME_COLOUR=Portal,Dodger_Blue,Yellow_Green,Medium_Blue,Yellow
GAME_COLOUR=Star Wars Pinball: Star Wars Rebels,Medium_Blue,Yellow,Royal_Blue,Orange_Red,Purple,Lime_Green
GAME_COLOUR=Rome,Dark_Red,Gold,Dodger_Blue,Light_Salmon,Yellow_Green,Orange
GAME_COLOUR=Secrets of the Deep,Blue,Yellow,Dodger_Blue
GAME_COLOUR=Shaman,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime
GAME_COLOUR=Sorcerer's Lair,Blue,Blue_Violet,Dodger_Blue,Slate_Blue
GAME_COLOUR=South Park: Butters' Very Own Pinball Game,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime_Green
GAME_COLOUR=South Park: Super Sweet Pinball,Dark_Red,Lime,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime_Green,Yellow_Green
GAME_COLOUR=Spider-Man,Dark_Red,Lime,Blue,Gold,Dark_Violet,Orange
GAME_COLOUR=StarWars: StarfighterAssault,Medium_Blue,Dodger_Blue,Dark_Red
GAME_COLOUR=Tesla,Lime_Green,Yellow_Green,Dodger_Blue,Golden_Rod
GAME_COLOUR=Star Wars: The Clone Wars,Dark_Red,Pink,Medium_Blue,Medium_Turquoise,Lime,Lime_Green
GAME_COLOUR=Star Wars Pinball: The Force Awakens,Dark_Red,Medium_Blue,Blue_Violet
GAME_COLOUR=The Infinity Gauntlet,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime
GAME_COLOUR=The Walking Dead,Lime_Green,Royal_Blue,Yellow_Green
GAME_COLOUR=Thor,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue,Lime
GAME_COLOUR=V12,Dark_Red,Blue,Gold,Dark_Violet,Orange,Dodger_Blue
GAME_COLOUR=Venom,Dark_Red,Blue,Dark_Violet,Dodger_Blue
GAME_COLOUR=Wild West Rampage,Yellow_Green,Dodger_Blue,Royal_Blue
GAME_COLOUR=Wolverine,Dark_Red,Medium_Blue,Yellow,Dark_Violet
GAME_COLOUR=World War Hulk,Lime_Green,Yellow_Green,Dodger_Blue,Lime,Yellow
GAME_COLOUR=X-Men,Blue,Blue_Violet,Gold,Dodger_Blue,Slate_Blue,Orange
 

6) When I start DOFLinx, it commences without troubles. As soon as I start Future Pinball, the following error appears and DOFLinx needs to be shut down:

 

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.MissingMethodException: Method not found: 'Int32 System.Runtime.InteropServices.Marshal.SizeOf(!!0)'.
   at DOFLinx.MainForm.Search_Memory(Process TheProcess)
   at DOFLinx.MainForm.DoStartup()
   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.0.30319.17929 built by: FX45RTMREL

----------------------------------------
DOFLinx
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0

----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 11.0.50709.17929 built by: FX45RTMREL

----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

----------------------------------------
DirectOutput
    Assembly Version: 0.9.5818.37242
    Win32 Version: 0.9.5818.37242

----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

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

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I am no very computer-savvy person. What I gathered from my rudimentary understanding is that the "handshake" between DOFLinx and FP doesn't work correctly for whatever reason. When I set FP_ATTEMPT_LINK=1 to FP_ATTEMPT_LINK=0, both programms work, but nothing happends RGB flasher-wise; because, obviously, there is no connection between FP and DOFLinx established - at least, this is what I guessed.

Also, when I set FP_ATTEMPT_LINK=0, I have my FROR LED lighting up in an eearie green - which is slightly odd and a little bit confusing. But maybe I did something wrong somewhere along the lines.

 

I have done several clean installs of the programms above, but I cannot get DOFLinx to work, unfortunately. Since I am at a total loss, though having the feeling that I missed some obvious step or did some stupid mistake; I thought I post my issue here and hope that you might help me out. I would be really happy if I could get this to work.

 

Thank you so much for your time and effort. I really appreciate it. If you need more info from me, please, let me know. I am happy to provide.

Best, Josh

Edited by jogster, 22 October 2016 - 08:26 PM.

[Outhere]

Go in and Clear your  DOFLinx.log and try it again and then post your log

[TerryRed]

"I run Future Pinball via BAM. So, my Future Pinball.exe is a renamed FPLoader.exe that is provided via BAM. BAM works nicely without DOFLinx."

 

When using BAM, you don't need to modify or rename ANY of Future Pinball's files. So you should have your Future Pinball directory with the original "Future Pinball.exe", and in the BAM folder, you should have the original BAM FPLoader.exe file.  You use FPLoader in Pinball X to launch your FP tables. Is that what you are doing?

 

DOFLinx needs to "see" Future Pinball, and I'm not sure that renaming your files will cause an issue with that.

 

Do you have DOFLinx installed in your DirectOutput folder?

 

Do you have EVERY .exe set to "Run As Administrator" in your Future Pinball, BAM, and DirectOutput folder?

 

Did you install DOF R3, not R2 as DOFLinx requires R3.

 

I'm not sure if Win 7 "blocks" *.dll files like Win 8 or Win 10 does... all *.exe and *.dll files need to be "unblocked".

[jogster]

Thanks for your first replies. I will clear the log and post the new log entry shortly.

 

Regarding BAM. I've been around for a really long time, since the beginning of BAM, aso., and the issue of renaming Rav`s FPLoader.exe to Future Pinball.exe is not my own idea, but a recommendation from Rav himself, when he released BAM all along. There are no other files changed in the Future Pinball Directory. It's just the FPLoader. This works perfectly fine and absolutely stable. This has never been an issue before. But I can give it a try. But I am sure that this is not the issue.

 

DOFLinx therefore can "See" FP running nicely. There are no changes whatsoever in FP itself.

 

DOFLinx is installed in the directoutput folder.

 

Every Exe is running as "Administrator". BAM, Future Pinball, PinX, B2Server, DOFLinx, etc. Everything doulbe and tripple checked.

 

I have installed DOF R3, as suggested by DDH69.

 

Win7 doesn't block any .dll files; but this is also what I checked, because it was highlighted over at DOF.

 

I will install DOFLinx 4.0 now and then post the "new" results in a moment.

 

Again, thanks for your early feedback.

[jogster]

Okay, same results with DOFLinx 4.0. I again checked all the exe files being run as administrator. all good. Used the FPLoader.exe as original file in BAM, not renaming it to Future Pinball.exe. Same results.

 

Here is the -rather short- DOFLinx log file:

22-Okt-16 21:17:00 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
22-Okt-16 21:17:00 - Starting up - version 4.0
22-Okt-16 21:17:00 - 1 LEDWiz device(s) found
22-Okt-16 21:17:00 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
22-Okt-16 21:17:00 - DOFLinx device:1 LEDWiz setup with 32 outputs
22-Okt-16 21:17:00 - 0 FTDI (Sainsmart) device(s) found
22-Okt-16 21:17:00 - Reading DOFLinx.INI startup config file details
22-Okt-16 21:17:00 - Reading DOF config file

 

Unfortunately, this doesn't mean anything to me

[TerryRed]

Your log shows Future Pinball isn't detected...or DOFLinx has crashed for you.

 

Try enabling DEBUG=1, so you can see what's going on as it happens.

 

 

 

Try loading Future Pinball and your table first. Then try loading DOFLinx after.

 

You shouldn't get any crashing at this point...but you do need to get your table running withing about 40 sec (by default) or the link won't establish.

 

Try running the original Future Pinball.exe instead of BAM and see if you get different results.

 

 

 

With DEBUG=1, you can also right-click on the Debug window to try the "test" menu to see if DOFLinx will at least turn on and off your Flashers.

Edited by TerryRed, 22 October 2016 - 09:00 PM.

[jogster]

Hey Terry. I tried starting FP First, Loading the table, starting doflinx and then launching the table. Same result. Doflinx crashes with the same Error. This also happens when I run the table in pinx. Bam vs Original FP also doesn't Change anything.

[jogster]

Okay, I ran DOFLinx again in Debug mode. I could test my flashers. Almost any port worked nicely, but ports 31 and 32 crashed DOFLinx. The others worked though.

Here is the log file in debug mode. Maybe it sheds more light on my issue:

22-Okt-16 22:27:48 - DOF Linx for Pinball Emulators - DOFLinx by DDH69
22-Okt-16 22:27:48 - Starting up - version 4.0
22-Okt-16 22:27:48 - 1 LEDWiz device(s) found
22-Okt-16 22:27:48 - DOFLinx device: 1 Initializing as LEDWiz #1 with ID=0
22-Okt-16 22:27:48 - DOFLinx device:1 LEDWiz setup with 32 outputs
22-Okt-16 22:27:48 - 0 FTDI (Sainsmart) device(s) found
22-Okt-16 22:27:48 - Reading DOFLinx.INI startup config file details
22-Okt-16 22:27:48 - Reading DOF config file
22-Okt-16 22:27:51 - Activated by process name : Future Pinball
22-Okt-16 22:27:51 - Game name = ''
22-Okt-16 22:27:51 - Named process detected and startup commenced
22-Okt-16 22:27:51 - Process has administration rights
22-Okt-16 22:27:51 - 64 bit OS detected
22-Okt-16 22:27:51 - FP full name=C:\Future Pinball\Future Pinball.exe Size=28547584 bytes, Dated 31.12.2010 13:23:32
22-Okt-16 22:27:59 - Shutting down
 

[DDH69]

First thoughts, two things;

 

1. You have this in your DOFLinx.INI

FP_ATTEMPT_LINK=1
LINK_FLOL=130,131,132
LINK_FLIL=124,125,126
LINK_FLCN=121,122,123
LINK_FLOR=127,128,129
LINK_FLIR=103,104,105

I suspect you want

FP_ATTEMPT_LINK=1
LINK_FLOL=130
LINK_FLIL=124
LINK_FLCN=121
LINK_FLOR=127
LINK_FLIR=103

You only specify the RED port, DOFLinx then assumes GREEN = RED+1 and BLUE= RED+2.  With your original config above DOFLinx would read it as three output devices  for each flasher.  The LINK_FLOL=130,131,132 would break things as a RGB flasher on port 131 or 132 would need Ledwiz ports 33 and 34 (RED=132 + 2) which clearly do not exist, hence crash.

 

2. You have

# L_FLIPPER_KEY=A0
# R_FLIPPER_KEY=A1

Remove the # comment marker and set these to your flipper keys (The above is Left and Right shift)  Despite not being needed in the mode you are using, I'm still not sure things will behave well without them.  Its on my list to look into, but setting them will avoid any potential issue.

 

There may be other issues, but these would be a "show stopper", fix it and give it another try and report back.  Keep DEBUG=1, and post the section of the log file for the run you do.

 

BTW - you definitely have a "Future Pinball.EXE" file as found by DOFLInx and as shown in the log.  This is the EXE running FP when DOFLinx runs.  DOFLinx back-tracks from the running process to the initiating EXE file so that it can report.

22-Okt-16 22:27:51 - FP full name=C:\Future Pinball\Future Pinball.exe Size=28547584 bytes, Dated 31.12.2010 13:23:32

[jogster]

Good morning DDH69,

thanks for joining the rescue party. I changed the ini to

 

FP_ATTEMPT_LINK=1
LINK_FLOL=130
LINK_FLIL=124
LINK_FLCN=121
LINK_FLOR=127
LINK_FLIR=103

 

as you suggested. Earlier on I had these settings but thought they would cause the error. Thus I added the extra ports. My mistake; should have taken the guide more seriously.

Unfortunately, the changes don't help.

 

I also activated the flipper input.

 

L_FLIPPER_KEY=A0
R_FLIPPER_KEY=A1

 

If I do this, however, now also the debug mode crashes when I test the RGB flashers.

 

When I launch DOFLinx with the suggested changes and then start FP, DOFLinx crashes with the exact same error message as indicated above. The logfile is also exactly as posted above.

I am sorry. This didn't solve the issue.

[DDH69]

OK, step #1, don't worry, we'll find this 

 

Based on the crash message you posted (partially copied below)

************** Exception Text **************
System.MissingMethodException: Method not found: 'Int32 System.Runtime.InteropServices.Marshal.SizeOf(!!0)'.

************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL

I wonder if you've got a suitable version of the .NET framework loaded.  The first line of the exception is actually reporting that the program can't find a function it needs that would be in the .NET framework.  Here is a link from MS on how to check what you've got.  I've followed this and have 4.6.01586.  Can you have a look and let me know what you've got.

 

My current suspicion is an older .NET framework version and that the other errors are important, but a distraction too.

[jogster]

Thank for your Optimizm. I Really appreciate your help. Thus is driving me nuts.
Regarding .net Framework: according to the Registry I am Running 4.5.50709
Should i Upgrade?

[DDH69]

I do not know if this is definitely the problem.  It is currently still my highest suspicion as the error is reporting the inability to find a required function.

 

I would suggest backing up and taking whatever precautions you would normally take before upgrading, then upgrade the .NET framework via the Microsoft site and try again.  Please keep in mind, while I can help with DOFLinx, any decisions you make to update Windows are yours and at your risk.

[jogster]

Hey ddh69
Since i don't have my cabinet hooked up to the Internet, Updates and such are Not Easy. But i will try to Update net Framework to 4.6.2.

Edited by jogster, 23 October 2016 - 12:53 PM.

[jogster]

Ddh69
You are a Genius,man. I did a Step by Step Upgrade from net Framework 4.5.5 to 4.6.0. Since 4.6.0 doflinx runs stable and gets a successful Connection to FP. I Can successfully Launch, run and Play dofed FP Tables Now. I tried it with star Trek and have Working flasher animation.
This is so great. Thank you so much for your help.
I get the occasional crash of doflinx upon exiting FP. But for now i am set.
Again, a big Thanks into your direction. This made my day.

Edited by jogster, 23 October 2016 - 02:32 PM.

[DDH69]

Ddh69
You are a Genius,man. I did a Step by Step Upgrade from net Framework 4.5.5 to 4.6.0. Since 4.6.0 doflinx runs stable and gets a successful Connection to FP. I Can successfully Launch, run and Play dofed FP Tables Now. I tried it with star Trek and have Working flasher animation.
This is so great. Thank you so much for your help.
I get the occasional crash of doflinx upon exiting FP. But for now i am set.
Again, a big Thanks into your direction. This made my day.

 

Very glad to hear its working.

 

I'm always interested to get details of any crash if you can capture it.  Ideally the error message details, LOG file and INI file - thanks.