Jump to content



Photo
* * * * * 2 votes

How Future Pinball "should" be setup for BAM, DOFLinx and Pinball X!

DOFLinx Future Pinball

  • Please log in to reply
32 replies to this topic

#21 DDH69

DDH69

    Pinball Wizard

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

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 15 July 2017 - 11:16 PM

Definitely move to the latest EXE available before we look too much further.  There was a FP memory fix in there that I believe addressed the sort of error you are seeing. 


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

#22 Baronir2d2

Baronir2d2

    Enthusiast

  • Members
  • PipPipPip
  • 52 posts

  • Flag: Brazil

  • Favorite Pinball: Family addams

  • 360 Gamer Tag: Baronimg

Posted 15 July 2017 - 11:28 PM

Ok, I just downloaded version 5.1, unzipped, unlocked the dll and put the .exe file as administrator, the error persists.
 
So I open the FPloader.exe error occurs ...
 
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.18063 built by: FX45RTMGDR
----------------------------------------
DOFLinx
    Assembly Version: 1.0.0.0
    Win32 Version: 5.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.34238 built by: FX452RTMGDR
----------------------------------------
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.18047 built by: FX45RTMGDR
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18021 built by: FX45RTMGDR
----------------------------------------
System.Runtime.Remoting
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.17929 built by: FX45RTMREL
----------------------------------------
DirectOutput
    Assembly Version: 0.9.5812.27024
    Win32 Version: 0.9.5812.27024
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.18060 built by: FX45RTMGDR
----------------------------------------
B2SBackglassServer
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
----------------------------------------
System.Web
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.34237 built by: FX452RTMGDR
----------------------------------------
 
************** 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.
 

Im Runing in Windows 7 Home premiun 64bits.



#23 DDH69

DDH69

    Pinball Wizard

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

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 15 July 2017 - 11:56 PM

OK, the full message jogged my memory .... I'm still asleep on this Sunday morning.

 

You need to update your .Net framework to the latest.  You are missing an essential .Net method for the memory scanning.


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

#24 Baronir2d2

Baronir2d2

    Enthusiast

  • Members
  • PipPipPip
  • 52 posts

  • Flag: Brazil

  • Favorite Pinball: Family addams

  • 360 Gamer Tag: Baronimg

Posted 16 July 2017 - 12:23 AM

OK!
 
I updated .net and is now running FP perfectly with DOFinx ..
 
Thank you so much...
 
 
Last thing, can I run my old ledwiz tables with doflinx active?


#25 DDH69

DDH69

    Pinball Wizard

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

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 16 July 2017 - 01:07 AM

 

Last thing, can I run my old ledwiz tables with doflinx active?

 

 

I've never tried.  Only one potential problem comes to mind, DOFLinx will determine that there is no FP link code and start into keyboard intercept mode.  You may have two things trying to fire your flipper toys.  This will not cause damage, but may be a bit weird.

 

You could of course assign L_FLIPPER_KEY and R_FLIPPER_KEY to unused keyboard keys thus effectively disabling keyboard intercept mode.  If this worked you could get fancy and have your front end do a Run Before and Run After message via DOFLinxMsg or similar to disable / enabale the keys.


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

#26 TerryRed

TerryRed

    Pinball Wizard

  • Silver Supporter
  • 2,000 posts

  • Flag: Canada

  • Favorite Pinball: Too many to choose...

Contributor

Posted 16 July 2017 - 08:56 AM

 

 

Last thing, can I run my old ledwiz tables with doflinx active?

 

 

I've never tried.  Only one potential problem comes to mind, DOFLinx will determine that there is no FP link code and start into keyboard intercept mode.  You may have two things trying to fire your flipper toys.  This will not cause damage, but may be a bit weird.

 

You could of course assign L_FLIPPER_KEY and R_FLIPPER_KEY to unused keyboard keys thus effectively disabling keyboard intercept mode.  If this worked you could get fancy and have your front end do a Run Before and Run After message via DOFLinxMsg or similar to disable / enabale the keys.

 

 

 

Yup.

 

When running both, FP Led-Wiz and DOFlinx will "take turns" and it can get goofy.

 

DDH69 is on the money. either set your default "key to output" Flippers to not work at the same time (this doesn't effect your DOFLinx enabled FP or PFX2 tables), or setup another "system" in PBX called something like "FP Led-Wiz only" and have it send a MSG or use a SUP file with DOFLinx that disables the flippers for only these tables,etc...

 

A few ways it can be done.



#27 Chaffee1921

Chaffee1921

    Hobbyist

  • Members
  • PipPip
  • 14 posts

  • Flag: United States of America

  • Favorite Pinball: Adam's Family, Whitewater, LOTR

  • PS3 Gamer Tag: Snakeyes19
  • 360 Gamer Tag: TheProfessor19

Posted 12 January 2018 - 04:17 PM

If I don't have any toys in my pinball cabinet, am I able to install DOFLinx in order to play the DOFLinx tables or will I mess up my system?



#28 Outhere

Outhere

    Pinball Wizard

  • Platinum Supporter
  • 4,807 posts

  • Flag: United States of America

  • Favorite Pinball: M M

Posted 12 January 2018 - 05:25 PM

I don't believe you need DOFLinx to use the modded games...

if you have nothing in your setup (hardware) for DOFLinx to detect it will not work anyway



#29 DDH69

DDH69

    Pinball Wizard

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

  • Flag: Australia

  • Favorite Pinball: Monster Bash

Posted 12 January 2018 - 10:37 PM

If I don't have any toys in my pinball cabinet, am I able to install DOFLinx in order to play the DOFLinx tables or will I mess up my system?

 

As per the other thread where you asked this, just install the DOFLinx.vbs file into FP and all will be well.


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

#30 Chaffee1921

Chaffee1921

    Hobbyist

  • Members
  • PipPip
  • 14 posts

  • Flag: United States of America

  • Favorite Pinball: Adam's Family, Whitewater, LOTR

  • PS3 Gamer Tag: Snakeyes19
  • 360 Gamer Tag: TheProfessor19

Posted 24 February 2018 - 09:20 PM

So I posted on this topic earlier about installing DofLinx and I went ahead and installed DofLinx and made sure I had a copy of the VBS Script placed into a Scripts Folder in the Future Pinball Folder. This enabled me to have some of the previous FP tables open through Pinball X that were getting an error message before, but everything was running really slow and the ball was huge on the playfield. Basically the physics were off. I realized that I was not running FP 2.7 physics so I downloaded and replaced my FP.exe and now the tables are failing to load again. They just get stuck, no error message. When I tried to open one directly in Future Pinball, the positioning was way off and I had to turn off Arcade Mode in the Rendering settings to even get the table to load properly. The physics are correct but I'm basically viewing a desktop version of the table and it's just not the same. Any suggestions on what I'm doing wrong? I followed Terry's original post to the letter. The only thing I haven't been able to do is configure my DofLinx.ini, but it may be set up correctly already (there was a note about having it always run in the background with Pinball X). 

 

There were also two tables (Adam's Family Gold & Pirates of the Carribean/both SLAMt1lt's creations) that still didn't load after getting the DofLinx.vbs into a scripts folder. Any ideas why these two were different than the rest? 

 

Sorry for the long reply. I'm a noob at all this but trying really hard to get some nice tables working on my cabinet. 



#31 latin625

latin625

    Hobbyist

  • Members
  • PipPip
  • 45 posts
  • Location:Atlantic City, NJ

  • Flag: United States of America

  • Favorite Pinball: Avatar

Posted 18 January 2020 - 08:32 AM

Thanks,

 I had to rebuild my machine and I can not remember how I got Future pinball to close with PBX.  does any one have a solution?  I tried AHK to send mapped key , but it does not work.  Only pressing on the keyboard escape key works.



#32 scampa123

scampa123

    Enthusiast

  • Platinum Supporter
  • 174 posts

  • Flag: United States of America

  • Favorite Pinball: Gorgar

Posted 16 August 2020 - 01:34 PM

@TerryRed how do you start DOFLinx at startup?

 

are you doing something in the PinupPopper emulator script?

 

are you starting/stopping DOFLinx each time Future Pinball is launched and exited?

 

Thank you!



#33 scampa123

scampa123

    Enthusiast

  • Platinum Supporter
  • 174 posts

  • Flag: United States of America

  • Favorite Pinball: Gorgar

Posted 16 August 2020 - 03:34 PM

Wait...I got it.... I was having issues because DOFLinx actually differently for me if I run Future Pinball tables outside of the PinupPopper front end...

 

outside of a front end it seemed as though I had to exit DOFLinx and reload Bam and Future pinball and DOFLinx to get everything to work

 

if I launch DOFLinx before launching my Popper front end, all works well.  My leds light for the front end, VisPinX, Future Pinball tables....it just works!







Also tagged with one or more of these keywords: DOFLinx, Future Pinball