64 replies to this topic

[TerryRed]

"SLOW MOTION" text flashing at bottom of screen - FIX!

 

 

Looks like one last bug crept in!

 

Some users reported with previous updates, they would see text at the bottom of their screen that flashes "Slow Motion" on and off rapidly.

 

I didn't ever see this myself, until I tried removing my current BAM settings files and using brand new files generated from 1.5-405 or my BAM Setting files in the Essentials AIO package (which were made with the previous update)

 

 

It took me a while to figure it out. The problem seems to be related to the newer "Overlay Aspect Fix" feature.

 

 

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

 

 

FIX!

 

If you see the "Slow Motion" text at the bottom, the fix is easy!

 

Simply open the BAM menu (~ or Q), then goto REDEFINE KEYS. Then under "Overlay Aspect Fix" assign any key not being used (like O).

 

The problem should go away immediately. Close the BAM menu with ~ or Q. Close FP and reload the table to confirm the problem is still gone. If it is gone, then you can go back to REDEFINE KEYS and choose Reset to Defaults to remove the key assignment.

 

This only needs to be done once, as it gets save to the BAM.cfg file.

 

 

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

 

 

Do this until the next BAM update permanently fixes the issue.

 

Thanks to those who reported this before, so I knew what to look for!

Edited by TerryRed, 05 May 2026 - 12:43 AM.

[TerryRed]

3.5 update - May 2026

 

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

 

=== BAM v406 ===

 

- fix for "Slow Motion" text flashing on / off and HUD Overlays rapidly changing Aspect Ratio

 

=== 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)

 

 

 

Don't forget to update your GPU drivers if having any problems!

 

Thanks to ravarcade for such a fast turnaround.

 

 

Download link is on first post of this topic.

 

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

Edited by TerryRed, 05 May 2026 - 11:11 PM.

[GHOSTfaceKILLr7]

 

3.5 update - May 2026

 

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

 

=== BAM v406 ===

 

- fix for "Slow Motion" text flashing on / off and HUD Overlays rapidly changing Aspect Ratio

 

=== 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)

 

 

 

Don't forget to update your GPU drivers if having any problems!

 

Thanks to ravarcade for such a fast turnaround.

 

 

Download link is on first post of this topic.

 

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

 

I'm wondering if you can help me.

I'm using Direct Input "DInput" joysticks and buttons to play emulated games like Future Pinball, Visual Pinball, MAME, RetroArch, Dolphin, Flycast and so on.

I recently installed a few games that requires "XInput". I'm using a program called "XOutput" which emulates an Xbox 360 controller. XOutput basically maps inputs from my DInput controls to a virtual Xbox 360 controller (XInput).

My issue is after I close both XOutput and the game which requires XInput controls all of the emulators (Visual Pinball, MAME, RetroArch, Dolphin, Flycast) is still able to read my DInput controls except for Future Pinball. I have to restart my PC to get Future Pinball to read my DInput controls again.

I tried a program called HidHidden to hide my DInput controls while running XOutput but still Future Pinball stops reading my controls.

Unplugging/replugging controls don't work.

I tried writing a script (AutoHotkey, Autoit) to reset my controls but didn't fix the issue.

 

Is there something in Future Pinball that can be reset so it can read my controller again without having to restart my PC.

Any help would be greatly appreciated.

[TerryRed]

 

 

3.5 update - May 2026

 

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

 

=== BAM v406 ===

 

- fix for "Slow Motion" text flashing on / off and HUD Overlays rapidly changing Aspect Ratio

 

=== 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)

 

 

 

Don't forget to update your GPU drivers if having any problems!

 

Thanks to ravarcade for such a fast turnaround.

 

 

Download link is on first post of this topic.

 

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

 

I'm wondering if you can help me.

I'm using Direct Input "DInput" joysticks and buttons to play emulated games like Future Pinball, Visual Pinball, MAME, RetroArch, Dolphin, Flycast and so on.

I recently installed a few games that requires "XInput". I'm using a program called "XOutput" which emulates an Xbox 360 controller. XOutput basically maps inputs from my DInput controls to a virtual Xbox 360 controller (XInput).

My issue is after I close both XOutput and the game which requires XInput controls all of the emulators (Visual Pinball, MAME, RetroArch, Dolphin, Flycast) is still able to read my DInput controls except for Future Pinball. I have to restart my PC to get Future Pinball to read my DInput controls again.

I tried a program called HidHidden to hide my DInput controls while running XOutput but still Future Pinball stops reading my controls.

Unplugging/replugging controls don't work.

I tried writing a script (AutoHotkey, Autoit) to reset my controls but didn't fix the issue.

 

Is there something in Future Pinball that can be reset so it can read my controller again without having to restart my PC.

Any help would be greatly appreciated.

 

 

 

FP has always been able to use DINPUT or XINPUT controllers directly. No extra apps were needed.

 

The problem seems to come from the use of the XOUTPUT app possibly. I know of nothing on the FP end that can be changed to accommodate those issues.

[TerryRed]

3.6 update - May 2026

 

 

=== BAM v408 ===

 

- fix for crashes related to using BAM Model stop commands

 

 

Download link is on first post of this topic.

 

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