November 25, 2016 at 11:07 pm #42163
This is a “simple” setup guide for anyone who wants to setup a clean install of Future Pinball, BAM (Better Arcade Mode), and Pinball X for use in their cabinet.
How Future Pinball “should” be setup with a new clean install for a cabinet:
-install Future Pinball from the setup file you get from the Future Pinball site
-copy your FP tables (*.fpt) to the Tables folder (NOT in their own self-named sub folders!)
-if your table needs a different version of physics (2.4,2.5,2.6,2.7, Zed, Custom, etc), then just copy the needed .XML (*.zip for Zed) to your Tables folder and rename it the same as your table
-copy any table Library files (*.fpl) to the Libraries folder
-install BAM (Better Arcade Mode), it should be in the “Future Pinball \ BAM” folder
-don’t change or rename any files in BAM folder!
-you can replace the Future Pinball.exe in the “Future Pinball” folder with another version if you want. I use SLAMT1LT’s version from his site as it does default to 2.7 physics and has no watermark. Keep the original for backup.
-unblock ALL *.exe and *.DLL files within Future Pinball, BAM, and Pinball X (Win 8 , Win 10)
-Future Pinball.exe and FPLoader.exe are set to “Run as Administrator”
-launch your FP tables with FPLoader.exe in the BAM folder
-setup Pinball X to launch FP tables with FPLoader.exe
Configure Future Pinball with these settings. This is a MUST, for complete compatibility with all tables and BAM / Cabinet use! Use these EXACT settings. (You can your change screen resolution and anti-aliasing if you want, and rotation to 0 if you have your playfield screen set to Portrait in Windows.) Also don’t forget to set your Backbox resolution.
-make sure you have “Load Image Into Table Editor” disabled (unchecked) in the “Preferences \ Editor Options” menu. This is important as you will get crashes and other strange things happen when you launch some tables!
-when running a table from the FP Editor directly (no frontend), ALWAYS load only one table at a time, and ALWAYS close FP and re-open it after exiting a table! This won’t be an issue when launching a table from a frontend like Pinball X.
By doing the above, you will have Pinball X use BAM to launch your FP tables, and BAM will use the appropriate physics file for your table if there is one…otherwise BAM will default to whatever the “Future Pinball.exe” uses (in my case, SLAMT1LT’s 2.7 physics).
Then when the table loads, press “Q” and you can adjust the size, layout, render type, etc of each table to your liking. BAM is simply amazing!
-New Renderer (Light System) is the nicest looking for lighting, etc….but is also more graphically demanding. Change to “FP Original” if a table runs slow for you
-new version of BAM fixed reflection limitations with FP, but also makes the ball look wierd with “FP Original” when in a rotated “cabinet” view. It looks fine in desktop view though.
-ambient occlusion can really kill your fps. You’re probably better off disabling it.
DOFLinx: (Future Pinball specific stuff)
My setup for my cabinet with DOFLinx:
-install the VPX all in one installer. (Installs the B2S server and all needed files. Yes it installs Visual Pinball 10 too, but you don’t have to use it. This saves you some work)
-install DOF R3 and confirm it’s working
-I install DOFLinx in the DirectOuput folder. This will allow DOFLinx to see DOFLinx.ini automatically. You can install to a different location, but you must configure DOFLinx to see where your DOFLinx.ini is located,etc…
-copy the DOFLinx.vbs file to the “Future Pinball \ Scripts” folder. Create one if doesn’t exist.
-configure the DOFLinx.ini for your cabinet setup! (consult the DOFLinx guide for more info)
-unblock ALL *.exe and *.DLL files within the DirectOutput folder or wherever you installed DOFLinx (Win 8 , Win 10)
-all *.exe files are set to “Run as Administrator” within the DirectOuput folder, and all DOFLinx *.exe files as well
-I have DOFLinx always running in the background with the startup of Pinball X. I HIGHLY recommend that you do this as it’s how DOFLinx was designed to run, and it will save you alot of headaches. You have been warned!
Sections of interest (in the DOFLinx.ini file) for Future Pinball tables modded to work with full cabinet support. (Consult the DOFLinx guide to configure your entire DOFLinx.ini file! Not just these sections)
– add this “FP_LINK_WAIT_TIME=50000” if it’s not there. This is the max time DOFLinx tries to establish a link (FP Link) with your FP DOFLinx modded table, before it defaults to its “key to output” type function. You change the time to a higher value if your computer takes longer to load some tables.
-this is needed if you want DOFLinx to attempt to establish the FP Link with FP DOFLinx modded tables
The following is your cabinet toys setup. Anything with a # in front of it will be ignored. Make sure you put a # in front of any device you don’t have in your cabinet. (I don’t have a shaker or gear motor)
Consult the DOFLinx guide for more info on how to configure this section.
These are the solenoids for flippers, bumpers, etc. Make sure they are configured for your particular setup, device, ports, etc.
This is the blower fan, shaker, and gear motor. (Note, I don’t have a shaker or gear motor)
Strobes and Beacon
Start, Launch, Fire button (you can add coin, exit, etc)
RGB Flashers. These are configured with the Red port of each RGB flasher.
This section deals with RGB_OUTPUT devices. As far as Future Pinball DOFLinx modded tables are concerned, this is the RGB under cabinet lighting. Note: if you have any RGB_OUTPUT device configured the same as a RGB flasher, then the RGB flasher will be used when a FP DOFLinx modded table is launched!
-I use my flashers for other programs, not just Future Pinball and Pinball FX2, so that’s why my RGB_OUTPUTS are configured the same as my RGB flasher ports.
-RGB_STYLE, RGB_TRIGGER, RGB_MIN_TIME all effect the RGB_OUTPUT….but for FP DOFLinx modded tables this will only have any effect if the table modder chose to use these features.
All of the above cabinet toys settings are also used for the Pinball FX 2 full cabinet support features of DOFLinx as well (correct me if I’m wrong DDH69!).
That about wraps it up as far as DOFLinx and Future Pinball modded tables are concerned. This doesn’t cover the other sections of the DOFLinx.ini, or all the other numerous features that DOFLinx has…. but it should help to answer A LOT of the questions I get.
Some users who have liked this topic:November 26, 2016 at 7:45 am #42188randrKeymasterNovember 26, 2016 at 10:41 am #42205
Others may not know how BAM works with XML files, they may not have Future Pinball graphics setup correctly for SLAM’S tables (disable GameRoom) and also what’s needed for FutureDMD, etc…
Also, some people setup BAM by having the FPLoader.exe renamed to Future Pinball.exe. (this was recommended at some point long ago, but is not necessary for BAM)
This can cause issues for programs like DOFLinx that need to “detect” Future Pinball.exe properly. DDH69 posted about someone having this issue, so I figured this is a good time to do a “simple”, right to the point guide.November 26, 2016 at 4:07 pm #42217Dr.TomParticipant
Thanks Terry for putting this guide together. I might have been “that guy” having the fploader issue. So, I was thinking of posting the solution, but as always, not only did you beat me to it, but did far more than I would have done. Thanks for doing this.
November 26, 2016 at 10:22 pm #42239November 27, 2016 at 12:56 am #42258rotraxParticipantNovember 28, 2016 at 10:46 pm #42427AlParticipant
- This reply was modified 1 month, 3 weeks ago by Dr.Tom.
Thanks Terry, following win7 deciding that I was no longer using a legit copy ( it was admittedly a long series of upgrade CDs from XP through Vista to Win7 and I couldn’t be bothered going through all that again .. ) I’ve splurged and upgraded to win 10, and now I have it freshly installed, I’m just about to embark on the FP install to see what it’s like, so your timing for me is impeccable !
Some users who have liked this topic:
You must be logged in to reply to this topic.