Jump to content



Photo
- - - - -

slow motion setting going ON OFF


  • Please log in to reply
2 replies to this topic

#1 Energetics79

Energetics79

    Hobbyist

  • Gold Supporter
  • 47 posts
  • Favorite Pinball: Genie

Posted 19 March 2026 - 12:54 PM

after setting up kinect I all of a sudden have a "slow motion" on off setting going on/off like crazy (like a pressed button or slider-connection) but i cannot find where to set this.... so all tables run in slowmo....HELP


Edited by Energetics79, 19 March 2026 - 12:54 PM.


#2 TerryRed

TerryRed

    Pinball Fan

  • Silver Supporter
  • 1,989 posts

  • Flag: Canada

  • Favorite Pinball: Too many to choose...

Contributor

Posted 09 April 2026 - 05:49 AM

Someone in a discord had this issue. They solved it by installing the latest FP and BAM Essentials AIO, and manually installing my BAM Settings files (instead of using the "BAM Settings Files - Reset and Install" bat.



#3 TerryRed

TerryRed

    Pinball Fan

  • Silver Supporter
  • 1,989 posts

  • Flag: Canada

  • Favorite Pinball: Too many to choose...

Contributor

Posted 11 May 2026 - 01:19 AM

It took me a while to figure this issue out, as I finally saw it for myself recently. 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.

 

 

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

 

 

The latest BAM update included with FP and BAM Essentials AIO 3.5 or higher seems to have fixed this issue... BUT... if you see this problem again, then just do the same fix I outlined above.