64 replies to this topic

[tcb19]

*** Meditation Error of "Object Required: fso" after updating ***
 
If 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 again

 
I got this error when this setting was on Paranoid. This plug-in uses its own settings file, so a reinstall of BAM settings won't change it, nor will installing / updating BAM overtop of your files.
 
I saw a couple other people get this error before, but it wasn't until now I knew exactly what may have caused it.

Hello Terry what happens when the plugin options in bam und plugins option it says no plugins
Hello Terry what happens when the plugin options in bam und plugins option it says no plugins

[TerryRed]

 

*** Meditation Error of "Object Required: fso" after updating ***
 
If 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 again

 
I got this error when this setting was on Paranoid. This plug-in uses its own settings file, so a reinstall of BAM settings won't change it, nor will installing / updating BAM overtop of your files.
 
I saw a couple other people get this error before, but it wasn't until now I knew exactly what may have caused it.

Hello Terry what happens when the plugin options in bam und plugins option it says no plugins
Hello Terry what happens when the plugin options in bam und plugins option it says no plugins

 

 

It means you didn't follow the Install Guide and install the required Visual C++ packages that are included. Some plug-ins won't show up until this is done.

[TerryRed]

The Future Pinball and Bam Essentials AIO package

 

NEW v2.8 update! (Feb 2026)

 

Some of the main updates are:

 

- BAM and BAM-OpenVR updated to 1.5-396

- DMDExt updated to 2.4.0

- most of the Guides have been updated

- BAM Settings files all updated (desktop, cabinet, vr)

 

This update is not "yet" required for any of the tables out there (if you have 2.7 installed), but future table updates (by me) and new tables (in the future) WILL require this update!

 

Either way... update dammit... its friggin easy.

 

======================================================================

 

BAM 1.5-396 highlights:

 

New Overlay Aspect Fix feature

 

- FP's HUD Overlay (used by single screen players) was always fixed to a 16x10 ratio

- this resulted in DMDs,EM Reels,Gas Segments, being squished or stretched in any resolution that was not 16x10

- BAM's new Overlay Aspect Fix option corrects this in ALL modes

- this means that all score items can now look correct in any resolution

- this means single screen cabinet view players can FINALLY use the HUD Overlay (before it was stretched horribly)

- note, that Overlays made to accommodate the old ratio issue will look incorrect with this feature enabled (until they are corrected on the table), but the DMD,Reels,Gas Segment displays will all look correct

- simply try enabling / disabling the feature to see which works better for you (it can be global or per table)

- open BAM menu (~ or Q). The Overlay Aspect Fix can be found under Addons

- you can also assign a key / button to toggle the feature

 

Snapshots

 

- added options to save snapshots as JPG

- fixed broken snapshot if horizontal screen resolution is not a multiple of 4

 

Bug fixes

 

- memory leak when xBAM.GetTexture was used in script and object animations are played (used alot with MOTU CE)

- fixed incorrect mini-playfield positioning when table is rerun

 

Ball/flipper shadows are now by default rendered before table glass (if enabled)

xBAM.DrawShadowsWithSurface can be used to control, when shadows are rendered

 

...and many more things as described here:

 

https://pinballnirva...v1-5-395.23944/

 

 

======================================================================

 

Guides

 

The following guides have been updated with new info, new BAM features, some changes, new help in the FAQ

 

- Install Guide

- Info Guide

- BAM OpenVR Guide

- DMDExt Guide

- FAQ and Help Guide

 

======================================================================

 

BAM Settings files

 

- these have all been updated to be consistent with new BAM features for all modes (desktop, cabinet, vr)

- these are essential to use to have BAM setup correctly by default

- the VR Settings files in particular are now updated correctly (now includes OpenVR.cfg updated)

- "BAM settings - VR - Reset and Install.bat" has been updated to install the new files

 

======================================================================

 

HOW TO USE:

 

- this package can be installed into ANY current install of Future Pinball to get you up to date

- download zip file, and ensure it is NOT blocked by Windows BEFORE extracting it (check it dammit)

 

If you are simply updating from a previous FP and BAM Essentials AIO install:

 

- from your current install, run "BACKUP - important files and folders for FP-BAM.bat"

- copy the contents from the new update into your exiting install

- overwrite ALL files!

- VR users should run the "BAM settings - VR - Reset and Install.bat" (follow its instructions). Note this will erase any CFG files for your VR tables (not your normal BAM CFG files) to ensure they work correctly with the new VR updates. You can always back them up first, just in case, and try using them again afterward, if needed

- desktop and cabinet users are still recommended to run the new "BAM Settings" bat file for their setup

- front-end users: continue as before, no changes needed in your front end

- everyone else: use the "Start FP" bat files to load FP with the correct settings for the mode / features you use

 

If you are doing a complete new install:

 

- follow the included Install Guide

 

======================================================================

 

 

Download link is on the first post of this topic.

Edited by TerryRed, 22 February 2026 - 09:50 AM.

[TerryRed]

New Overlay Aspect Fix feature in BAM 1.5-396 (Future Pinball)

 

FP's HUD Overlay (used by single screen players) was always fixed to a 16x10 ratio. This resulted in DMDs,EM Reels,Gas Segments, being squished or stretched in any resolution that was not 16x10.

 

BAM's new Overlay Aspect Fix option corrects this in ALL modes. This means that all score items can now look correct in any resolution.

 

It also means single screen cabinet view players can FINALLY use the HUD Overlay (before it was stretched horribly).

 

Note, that Overlays made to accommodate the old ratio issue will look incorrect with this feature enabled (until they are corrected on the table), but the DMD,Reels,Gas Segment displays will all look correct.

 

Simply try enabling / disabling the feature to see which works better for you.

 

Open the BAM menu (~ or Q).

 

The Overlay Aspect Fix can be found in the Addons section (and set globally or per table). You can also assign a key / button to toggle the feature (in the Keys section)

 

=================================

 

Single screen users who want to play in a vertical cabinet view, and now want to use the HUD properly will need to enable the HUD Overlay first.

 

If "Hide Overlays" (also in Addons section of the BAM menu) was set to Always (and you couldn't see the HUD at all on the table), then you need to set that to OFF and reload the table to see them.

 

Now you can try the Overlay Aspect Fix and see if that works better for you (per table or globally).

 

If you want to set these changes as your new default, then goto the main section of the BAM menu and choose "Save as Default".

 

 

 

 

 

 

Edited by TerryRed, 22 February 2026 - 02:07 PM.

[TerryRed]

It's been reported that the BAM 1.5-396 update seems the cause the Pumpkin ball in Halloween BBB, and the Sonic ball in Sonic Pinball Mania to show up as a while ball instead of their textured ball.

 

I can confirm this is happening to me as well.

 

For now, a workaround is to set those tables to use the normal chrome ball in TABLE OPTIONS at the top of the table script.

 

 

Other tables that also use BAM Custom balls (MOTU CE, Star Wars DSA GE, Silent Hill wip) seem to work fine however. Not sure what the difference is yet.

 

I have passed this issue on to ravarcade.

[TerryRed]

Future Pinball and Bam Essentials AIO

 

NEW v2.9 update! (Feb 2026)

 

Some of the main updates are:

 

- BAM and BAM-OpenVR updated to 1.5-398

- bug fix for "Overlay Aspect Fix" that caused green bars for volume to be hidden / offset

- "state" of "Overlay Aspect Fix" is now correctly saved. Previously was always set to "use global" after table load

- incorrect "white ball" textures on some tables is fixed

 

======================================================================

 

Download link:

 

https://www.vpforums...showtopic=51600

[TerryRed]

3.0 update (Mar 2026)

 

- PinEvent V2 Guide updated (new info regarding pup v2.0, ssf)

- Popper and Baller Installer Guide updated (new info regarding pup v2.0, ssf, PinUPDater)

- AIO Example Table and Tutorial updated to 3.30.05 (new PUP SSF v2.0 features and FP_PUP_X2_SSF pup-pack)

 

======================================================================

 

Download link:

 

https://www.vpforums...showtopic=51600

[fourbanks]

all good terry on windows builds 10 and 11 with 

Version 2.0 (x64 = no VLC = New Engine) (Beta release)

and 

 

March 8, 2026 Beta 20: https://nailbuster.c..._x64_beta20.zip

[TerryRed]

3.1 update (Mar 2026)

 

- AIO Example Table and Tutorial updated to 3.30.06 (minor bug fix and new additions)

 

======================================================================

 

Download link:

 

https://www.vpforums...showtopic=51600

[TerryRed]

3.2 update (Mar 2026)

 

Updated AIO Example Table and Tutorial to 3.30.07

- renamed Sub Stop_All_BR_Sounds to Sub Clear_All_BR_Sounds (this is a more accurate description of what it does)
- I updated Ball Rolling code to support new function to not apply ball rolling sounds to specific balls (xBAM.ball.extInt3 = br_no)
- examples of xBAM.ball.extInt3 = br_ commands are now used directly in the _Hit subs

 

 

Download link:

 

https://www.vpforums...showtopic=51600

[TerryRed]

3.3 update (April 2026)

 

=== BAM Beta v401 (FAST BAM Loading!) ===

 

- big BAM update that uses new system to handle BAM related items on startup

- loads and process all BAM related stuff (models, gifs, shadowmaps, etc) a lot faster

- BAM related stuff is handled once the table fully loads and is about to start (after FP loading screen is done)

- this means that larger tables with lots of BAM related things (Star Wars DSA GE, MOTU CE) will load MUCH faster

- fixes for possible shadowmap bugs

- fixes for some tables that may have crashed at "Compiling Script"

 

=========================================

 

Important notes about Model Importer:

 

- there is a new "renderingengine.dll". It is required for the new BAM.dll (v401)

- this version currently can't import all 3d models with Model Importer app

- this is only a concern for table creators that use Model Importer

- this will be updated in the future

 

I have uploaded a separate "Model Importer" zip that has the older compatible files. This can be used by itself. This is only intended for any table creator that needs it.

 

DO NOT install files from "Model Importer.zip" into "ANY" BAM folder! You will break the BAM v401 update!

 

=========================================

 

https://www.vpforums...showtopic=51600

[TT11]

With the 3.3 update (April 2026)

No need to run the 4GB patch ??

[TerryRed]

With the 3.3 update (April 2026)

No need to run the 4GB patch ??

 

 

No need. When installing the FP and BAM Essentials AIO, you NEVER need to apply the 4 GB patch, because that has already been done to the files you are installing.

[TerryRed]

PSA - The BAM 401 beta in "FP and BAM Essentials AIO 3.3" update does NOT currently work with "BAM Tracker" for VPX.

 

(solution below)

 

 

I myself don't use headtracking (haven't for many years), and have never used BAM's BAM-Tracker.exe with VPX. Therefor I can never test this with any BAM updates.

 

According to reports from some VPX users, the new BAM 401 beta (included with the 3.3 update) is currently NOT compatible with BAM-Tracker.exe for VPX. (this may change in the future)

 

 

Solution:

 

A solution for VPX users is simple. Download an older zip file of BAM from ravarcade's site and install that to a SEPARATE folder (NOT in the FP folder). You can get that here (using 1.5-395 and older should be fine)

 

https://www.ravarcad...ownload/archive

 

 

Installing this to a separate folder means it can be used only for VPX. Call it something like "BAM for VPX". Then run BAM-Tracker.exe from this new folder for VPX headtracking.

 

This will ensure you can update FP-BAM with the newest FP and BAM Essentials AIO updates without concern for VPX headtracking being affected.

Edited by TerryRed, 25 April 2026 - 09:12 PM.

[TerryRed]

Anyone else who had issues with BAM-tracker.exe on VPX...

 

You can try using this latest BAM 404 beta update which should fix the issue. I can't test it myself, since I don't use headtracking (VPX or FP).

 

You can download the beta files here:

 

https://ravarcade.pl/beta/BAM_v404.zip

 

Just extract the files and copy them into each BAM folder from your FP and BAM Essentials AIO 3.3 install and overwrite all files.

[TerryRed]

For anyone who had the issue of the FP Backbox screen closing shortly after the table was loaded (and it only happened using a front-end with the newer BAM 401 update)... I can recreate the issue.

 

I tested with a simple BAT file... no Popper or other front-end.

 

REG ADD "HKCU\Software\Future Pinball\GamePlayer" /v "ArcadeMode" /t REG_DWORD /d 1 /f
REG ADD "HKCU\Software\Future Pinball\GamePlayer" /v "SecondMonitorEnable" /t REG_DWORD /d 1 /f
cd e:
cd "E:\Emulators\vPinball\FuturePinball"
START "" "E:\Emulators\vPinball\FuturePinball\BAM\FPLoader.exe" /open "E:\Emulators\vPinball\FuturePinball\Tables\ABraCaDaBra_FizX33_V110.fpt" /play /exit /arcaderender /STAYINRAM

 

The issue seems to come from using /play in the command line. If you remove that, and click play from the editor after the table is loaded, then the backbox screen stays on correctly.

 

I'll pass the info on to ravarcade (creator of BAM)

 

Its not a popper issue.

 

I haven't used Popper in a long time (as my cabinet is not currently up and running), so I don't use a command line normally to launch a table directly. So I never would have seen this if others didn't pass this along. Thanks to those who tested and shared their issues!

Edited by TerryRed, 27 April 2026 - 03:57 PM.

[GHOSTfaceKILLr7]

I figured it out.

Edited by GHOSTfaceKILLr7, 03 May 2026 - 05:30 AM.

[digitalarts]

OK... and the solution is???

[fourbanks]

New version:

https://ravarcade.pl/beta/BAM_v405.zip

Release candidate.

[TerryRed]

3.4 update - May 4 2026

 

=== BAM v405 ===

 

- fix for some tables crashing after loading

- fix for some tables crashing when paused

- fix for Bam Tracker (now works with VPX again)

- fix for Backbox screen closing after table was loaded (only when using /play from a front-end)

- fix for Model Importer (now works with new renderingengine.dll)

 

This is considered a release candidate, and no longer a beta

 

 

Download link on main post:

 

https://www.vpforums...=51600&p=520783

Edited by TerryRed, 04 May 2026 - 07:29 PM.