








....and here's a video comparison of the 2009 table to my BAM Edition update.

Edited by TerryRed, 24 December 2021 - 06:59 AM.
Posted 23 December 2021 - 04:50 PM









....and here's a video comparison of the 2009 table to my BAM Edition update.

Edited by TerryRed, 24 December 2021 - 06:59 AM.
Posted 24 December 2021 - 06:58 AM
....and here's a video comparison of the 2009 table to my BAM Edition update.

Edited by TerryRed, 24 December 2021 - 06:58 AM.
Posted 24 December 2021 - 06:55 PM
UPDATE: Table is now released! Get it here (after it's approved):
https://www.vpforums...&showfile=16350
Happy Holidays everyone!
Enjoy!
Edited by TerryRed, 24 December 2021 - 06:56 PM.
Posted 16 July 2023 - 09:19 PM
I was playing this today and got a Pinball Meditation Error - Line 10518, Object Required: FSO
Have I misinstalled something or is there an actual bug?
Posted 16 July 2023 - 09:24 PM
I was playing this today and got a Pinball Meditation Error - Line 10518, Object Required: FSO
Have I misinstalled something or is there an actual bug?That bug normally means that bam/future pinball is not up-to-date?
Hmmm. I copied all the files from the Future Pinball and BAM Essentials AIO - 1.2. I've gone through and followed the instructions, so far as I know.
Fixed the problem. Thanks, Terry! And thanks for all your great work!
I was playing this today and got a Pinball Meditation Error - Line 10518, Object Required: FSO
Have I misinstalled something or is there an actual bug?
PSA: Future Pinball - BAMIf you get a Meditation Error of "Object Required: fso" when trying to start a Future Pinball table, do the following:
open the BAM menu while playing (~ or Q) goto plugins iCOM change the setting to Safe (disable blacklisted) exit BAM menu, then close FP completely, and try againI got this error when this setting was on Paranoid. This plug-in uses its own settings file, so a reinstall of BAM settings wont change it, nor will installing / updating BAM overtop of your files.I had a power outage, and was getting this error all of a sudden, so my guess was that the outage made BAM reset the cfg file for this plugin as a safety precaution.I saw a couple other people get this error before, but it wasn't until now I knew exactly what may have caused it.