
Edited by TerryRed, 02 January 2023 - 09:46 PM.
Posted 02 January 2023 - 09:24 PM

Edited by TerryRed, 02 January 2023 - 09:46 PM.
Posted 03 January 2023 - 07:26 AM

Posted 03 January 2023 - 10:21 AM

Posted 04 January 2023 - 04:11 PM

Posted 06 January 2023 - 11:38 AM
All In One Example Table - BIG UPDATE!
Table version: 1.2 (Jan 6 - 2023)
FizX: v2.00
CHANGELOG
1.2 (Jan 6 - 2023)
- updated to JLou's newest FizX v2.0 code
- added JLou's bug fix for ball falling into 2nd or 3rd set of flippers
- new FizX code no longer requires flipper Swing Angle to be specified in the FizX Flipper settings!
- FizX slingshots, drop targets, rubbers are now set in the FizX General Settings section (not in a FizX Profile)
- FizX XML_FPS is now set in its own section
- updated FizX Profiles to only change FizX Flipper settings
- there are no longer FizX Profiles used for different physics xml settings
- any settings needed for a different PHYSICS XML FPS is now set in the FizX FPS settings section
Anyone who used the AIO Example table 1.0 or 1.1, should use all the new code from 1.2! This bug fixes are essential!
More detailed info on the update can be seen here:
https://pinballnirva...e-3#post-140663
The updated All In One Example table and Tutorial can be found here:
https://pinballnirva...y-to-add.21983/
Posted 23 January 2023 - 04:36 AM








Posted 14 June 2023 - 06:17 AM

Posted 17 June 2023 - 08:55 AM

Posted 21 November 2023 - 02:43 AM
FizX Physics System for Future Pinball - new updates for v3.2
There is no excuses now dudes! FizX 3.2 now has ALL FP rubbers and targets working with FizX physics automatically! No need to add anything new or do extra work for "complete" FizX 3.2 physics.
You still have the options as before to add new FP rubber posts or FizX rubber bands (recommended on slings) for more custom control if you wish. This would still allow you more flexibility and control over "every" item on the table.... but it's NOT a requirement anymore.
AIO Example Table and Tutorial updated to v3.20.07
This tutorial assumes you have a basic understanding of how Future Pinball - BAM works, and how to use the Future Pinball Editor.
Please take the time to read through the entire tutorial, so you know all the steps needed, and all the options you have. Many things have changed.
This tutorial is designed to be followed in order, step by step. I have split it into sections. The first sections are REQUIRED for FizX. The later sections are OPTIONAL.
REQUIRED SECTIONS
SECTION 1 – Prepare your table
SECTION 2 – Install files
SECTION 3 – Add required items to your table
SECTION 4 – Update the table for FizX physics
SECTION 5 – Disable features you won’t use or support
OPTIONAL SECTIONS
SECTION 6 – Optional FizX updates and features
SECTION 7 – Optional PinMechSound support
Table version: 3.20.07 (Nov 20 - 2023)
FizX: v3.20
CHANGELOG
3.20.07 (Nov 20 - 2023)
- updated table for all new FizX v3.2 code and features
- new FizX code no longer requires rubber posts, rubber bands, drop target walls to be added
- Tweaker Tool is now optional, and not required (table won't give an error if its not added)
FAQ (Frequently Asked Questions)
I just want to add FizX physics to a table. Will this tutorial and example code be easy to use?
Yes! Adding FizX in its entirety takes little time!
The “optional” extra steps for PinMechSound (which add DOF and PUP support) are NOT required! You are not creating any more work for yourself using this tutorial, or the example table’s code if you just want FizX physics.
FizX is much more than just “better flippers”. It’s a “complete” physics update for Future Pinball.
I don’t want to enable or use the Ball Rolling methods with this example code. Can I disable it and use my own?
Yes! Simply set BallRolling_Sound_Enabled = false in the “Ball Rolling Sound Settings” section
I don’t want to add any support for PinMechSound or PUP or DOF. I just want the table to be like other FP tables.
Easy! Set DOF_enabled = false, and PUP_SSF_enabled = false (be sure to note that they must not be changed).
You can remove the “MECHANICAL SOUNDS AND FEEDBACK” section if you wish. DO NOT remove the Sub PinMechSound section!
Do I need to remove my previous rubber or target items from FizX 3.0?
No. You can choose to keep what you had previously as long as it was part of FizX 3.0 (the names of the items are the same).
What is REQUIRED?
- the All in One Example table zip file's content
- BAM 1.5-365 or higher
Yes.... the newest BAM 1.5-365 is REQUIRED!
New updated Video Tutorial - Part 1: FizX 3.2, Fleep & Ball Rolling sounds
This video shows how to use the All in One Example Table (along with the written Tutorial) to easily update a Future Pinball table to support "all" these new features. It is broken into chapters so you can go at your own pace, and easily pick up where you left off.
It does not... I repeat... does not take multiple hours just to add "complete" FizX physics, (if that is all you want to add) using the AIO Example table and tutorial. Large portions of the video are me "explaining" everything, and testing.
This video is Part 1 which covers adding what is needed for FizX and some optional updates.
Part 2 will cover adding the optional PinMechSound commands to add SSF, DOF and FLEEP sounds to the entire table.
ALWAYS follow the entire NEW written tutorial for the most up to date and correct information! Only use the video as a visual guide to help you along!
IMPORTANT! Changes for FizX 3.2 that are REQUIRED!
Flippers
- flippers MUST now be named LeftFlipper1, RightFlipper1, LeftFlipper2, RightFlipper2, LeftFlipper3, RightFlipper3, LeftFlipper4, RightFlipper4
- their commands in the table script must be changed to match the new names
- this needs to be done for the main flippers now BEFORE you can start and test a table for the first time (you will get an error if you don't do this)
If you are updating a table that used the AIO Example code, make sure your PinMechSound commands for flippers are ALSO updated to use the new names for LeftFlipper1, RightFlipper1. If you don't do this, you will get table errors!
- slings diverters MUST be named SlingDiverter1, SlingDiverter2, SlingDiverter3, SlingDiverter4, etc
FizX Tweaker Tool
- the FizX Tweaker DMD is no longer required to be added. The table does a check for its existence before enabling its functions (no more errors)
Table Items, Surfaces, Models
- only “rubber” items / models should be set to use Rubber Material type (walls, surfaces, other models must not use rubber material)
- all items that have hit events (switch, trigger, etc) must not have their Material Type set to Plastics. Only Metal, or Wood
- only Targets and Drop Targets (with hit events) can have Material Type set to Plastic in the FP editor, or within the settings of the model itself from FPM-Editor
No mixing of old and new code!
- make sure you use only the code from the new AIO Example table for a new table or when updating a table with older AIO Example code
- you can copy over your Flippers, Rubbers, Drop Target settings in FizX General Settings as long as it was FizX v3.0
- use the new default PHYSICS XML settings, and only change what is different for items suck as kickers, bumper, etc as needed
I'm sure I've missed something... so I'll try to add anything I've missed (when I get some sleep, eventually).
This new AIO Example Table's code and tutorial is made to work for "everyone".
FizX 3.2 has removed the need for any extra work for rubbers and targets while having ALL features of FizX available. The new AIO Example code and tutorial has been made to allow anyone to add only FizX 3.2, without needing to add extra "options" like PinMechsound (for DOF and SSF), Tweaker Tool, or custom rubbers / bands / walls, etc.... but they are still there for anyone who wants to add them later on. That's a win-win for everyone!
It's what everyone has been wanting. So darn it... go get it. No excuses! ![]()
(My Part 2 Video, which is for adding PinMechSound to the same Knight Rider table, will come soon enough... when I get some sleep and can add that to the table and make a new video.)
The new updated table and tutorial can be found here:
https://pinballnirva...y-to-add.21983/
Edited by TerryRed, 21 November 2023 - 03:05 AM.
Posted 22 November 2023 - 10:20 PM
TABLE UPDATE
3.20.08 (Nov 22 - 2023)
- changed GenericPreHitMinBallSpeed = 1 to GenericPreHitMinBallSpeed = 5
This was supposed to be set to 5. This now means all static balls will be ignored, instead of having constant physics updates for balls that aren't moving. More efficient for tables with multiball, or tables with captive balls always on the table that aren't moving often.
Posted 23 November 2023 - 08:49 AM
Posted 02 February 2024 - 02:09 PM
FizX - new updates for v3.3!
AIO Example Table update:
3.30.00 (Feb 2 - 2024)
- FizX code completely updated for FizX 3.30 (now requires BAM 1.5-373 or higher)
- new DEBUG options, to allow you to control what you want to see in DEBUG mode (DOF, SSF Sounds, FP Mech Sounds, Ball Rolling, FizX)
- ramp models updated with two layers to render correctly
- some fixes to prevent excessive triggering in kicker, etc
- added some missing FLEEP sounds (OGG for the table, and WAV in FP_PUP_SSF PuP-Pack)
- PinMechSound code has been updated to now have PUP SSF's Ball Hit sound volume levels match the same control behavior as FP's ball hit sounds (before, they were always at max volume level).
- tutorial updated to reflect changes to the new code and features
- added "SETTINGS THAT CAN BE CHANGED" in table script to make it clear what settings can be changed by table creators / modders / players
=================================================================
AIO Example Table and Tutorial update zip:
https://pinballnirva...y-to-add.21983/
=================================================================
NOTE: you MUST update to the new BAM 1.5-373 to use this new FizX code!
If you have a working install of FP and BAM, then the best way to update (only BAM), is to download the new update zip file, make sure it's not blocked by Windows... and then install ONLY the new BAM.dll file to your BAM and BAM-OpenVR folders.
https://www.ravarcade.pl/download
I will have my "FP and BAM Essentials AIO" updated to the new BAM 1.5-373 soon (I need to update my guides first).
=================================================================
Enjoy the new and much more efficient FizX physics v3.3, and much easier to follow DEBUG options in the AIO Example table!
(All PinEvent tables will be updated for FizX 3.3 soon!)
Edited by TerryRed, 02 February 2024 - 02:09 PM.
Posted 13 March 2026 - 04:02 AM
AIO Example Table update
3.30.05 (Mar 12 - 2026)
The big PUP SSF v2.0 update!
- updated code, PUP SSF, Ball Rolling to support Pinup Player v2.0 features
- Ball Rolling now tracks 10 balls
- PUP SSF v2.0 now has 30 audio channels (10 wood, 10 plastic, 10 wire/metal)
- PUP SSF v2.0 can now change ball rolling sound per ball per material (ramps, wire ramps, etc)
- code uses new SSF PuP-Pack (FP_PUP_X2_SSF) with 30 new ball roll sounds and other updated sounds
- updated all code related to Pinup Player, PUP SSF, PinMechSound, Ball Rolling Sounds
- updated TABLE OPTIONS : added BallRolling_Sound_Mode, FP_MechSounds_Volume, FP_BallRoll_Volume, PUP_SSF_Volume, PUP_BallRoll_Volume
- removed DMDExt option (this caused lots of confusion for people, and 99% of cabinet players run DMDExt separately anyway)
- added optional "BAM LIGHTING and SHADOWS" section (not part of the AIO code)
- updated AIO Example Table Tutorial (new required steps for ball rolling)
=================================================================
The new Pinup Player v2.0 now has a new SSF sound engine!
Pup v2.0 SSF uses bass.dll, and allows for ball rolling tracking and up to 30 sound channels! This means that FP tables updated to support pup SSF v2.0 can now have 10 balls tracked with their own positions and sounds. We can now change each ball's material sounds for when they roll on ramps or different materials (10 wood, 10 plastic, 10 wire/metal)
Pup v2.0 SSF is NOT used with the current FP tables that support PUP SSF. It is currently only used by Popper v2.0 and new FP tables that support pup v2.0 (MOTU CE 1.4 will support this).
Pinup Player v2.0 and the FP_PUP_X2_SSF PuP-Pack (included with this new table update) is now REQUIRED to use the new PUP v2.0 SSF features with the new 3.30.05 AIO Example table update!
You can currently download the latest Pinup Player v2.0 update here:
https://www.nailbust...php?id=beta2026
=================================================================
Will PUP v2.0 affect any of your current table updates using the older AIO Example Table code?
No. All current FP tables updated using the previous 3.30.03 AIO Example Table's code and FP_PUP_SSF pup-pack will still run the same for anyone who is updated to PUP v2.0.
Will I need PUP v2.0 now if I don't use PUP SSF at all?
PUP is still is NOT required for anyone who doesn't want to use PUP SSF features with any table update using the AIO Example Table, same as before.
Will this new table and code update benefit FP Ball Rolling Sounds?
There is no functional benefit for FP Ball Rolling (it's basically the same). However the table's code and Tutorial has been updated to be easier to use and implement with more options in TABLE OPTIONS.
Do I need to update my current tables that had the previous AIO Example Code?
The only major functional benefits are if you want to add additional PUP v2.0 SSF Ball Rolling features to your table (10 balls tracked and changing rolling sounds on ramps).
For new table updates though, I would highly recommend the new 3.30.05 table's code and FP_PUP_X2_SSF pup-pack.
Tutorial is fully updated to 3.30.05
If you are updating any table to use the new 3.30.05 code, you MUST follow the new updated 3.30.05 Tutorial! There are some vital changes (some outlined below).
DO NOT mix old AIO Example code and new 3.30.05 AIO Example code! Only use the all new code in any update!
=================================================================
More details and download are here:
https://pinballnirva...983/post-163613
Edited by TerryRed, 13 March 2026 - 04:03 AM.
Posted 16 March 2026 - 02:22 AM
UPDATE!
3.30.06 (Mar 15 - 2026)
- replaced Sub StopAllBallSounds (if PUPSSF was disabled, it would give an error) with Sub Stop_All_BR_Sounds (this is an optional function, that is not normally used)
- added sub Set_DMD_Color function to make it easier to change the colour of FP DMD (not part of the AIO Code)
- added "BAM SETTINGS - STARTUP" section that delays applying BAM settings on startup to ensure they are applied correctly (not part of the AIO Code)
Stop_All_BR_Sounds will just stop and "clear" the current ball rolling looping sounds (in case a tracked ball is gone, but the looping sound is still stuck on). It won't stop Ball Rolling completely (as any active balls will start playing their rolling sounds again when they are detected as moving)
It's only an "option" to try using if you find you are having this issue. For me with MOTU CE... unlike before when we were tracking only 6 balls, now we can track up to 10 balls, and when things get crazy with 9 ball multiball, rarely I was finding one looping sound may be stuck on (from a ramp, etc), yet there was no ball left for it to be tracked to. Using this command (at the end of that MB mode, etc) in only extreme situations like this was something I came up as a "just in case" option. Normally you shouldn't need to use it.
More details and download are here:
https://pinballnirva...983/post-163643
Edited by TerryRed, 16 March 2026 - 02:23 AM.
Posted 19 March 2026 - 06:57 AM
UPDATE!
3.30.07 (Mar 19 - 2026)
- 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
More details and download are here:
https://pinballnirva...983/post-163695
Edited by TerryRed, 19 March 2026 - 06:58 AM.