All In One Example Table - FizX, FLEEP, Ball Rolling, PUP SSF, DOF - Easy to add!

[Saybrook]

yes it's normal if you use less pf friction.

Thank you! I will play around with that setting.

 

[Paolo]

@TerryRed
would you just give me the code of Ball Rolling, and TrackedBalls(xx) to add to my table,please?
obviously if it were possible without inserting pup,ssf and dof.
thanks

 

[Paolo]

@TerryRed , I tell you, that you are more active in fizx.....
I could be wrong, since george and I had covered this topic, so I tried to see if this variable worked "Table_Slope = xx"




I don't know, but it seems to me that the priority always has Fp editor than all the rest, as george and I had noted a long time ago, and discussed in another thread.

 

[JLou5641]

Hi @Paolo , Table slope from script work and override editor setting

 

[Paolo]

Hi @JLou5641 ,ok but....then there is a problem in bam's menu the "Q",because it shows the one set on editor, and not that of the variable in script, if you see the photos.....I have set 9.5 (test) in script, and 8.3 in editor, but the menu shows the one in editor ,last pic.

 

[AnonTet]

Ignore the value in the GUI.

make sure you have only 1 entry for table.slope in the script and for the sake of avoiding even more confusion, (and I think this is a mistake in AIO example table too), remove the slope from XML.

That being said, I have no clue where BAM menu takes its value from but table.slope works and that's where you should concentrate. Actually, if you change slope from 9.5 to 5 you'll notice it. Don't try to read to much into it as you'll only waste your time that is a lot better spent in producing a table :)

 

[TerryRed]

@Paolo

Follow the AIO Example Tutorial in order. Don't skip any part. The important part is to remove any code for older physics and older Ball Rolling code and their timers, etc. Make sure that is done first and confirm the table is completely working before adding the AIO Example code.

You don't need to have PUP or DOF installed to use the AIO Example code. Its designed to make use of DOF and PUP if someone has it installed (and the table has them enabled), but if those are not enabled than the code will ignore them and use normal FP Sounds instead. Just set PUP_SSF_enabled = false and DOF_Enabled = false if you don't want to have your table support those features.

Do not try to take bits and pieces of code from the AIO Example table code, as that is not how it's designed to be used. You will just cause more frustrations for yourself.

Use the recommended settings to start with. Adding PinMechSound commands to the rest of the table isn't "required" to make a table work, but it's highly recommended (you can wait until the end to do that).

The new Ball Rolling is part of the AIO Example code. If you follow the tutorial from start to finish (and there are no problems... then the ball rolling should automatically work for most FP tables.

Table Slope is set in the FizX General Settings now. I'd recommend starting between 5.5 to 6.0. This will override the table editor and the XML code, no matter what the BAM menu tells you. Don't try to think like the older ways of doing things, as that will confuse you (it took me a long while to get used to how FizX works).

 

[Paolo]

Thanks for the tips Guys......however I managed to add Ball Rolling.

@TerryRed
The fact is not to take a piece here and there, as a builder I have my vision, and I would like a "FizX" that suits me, in the simplest possible way..... and allow me to also say, shorter as a code to insert.
Now if I ask for a "FizX" according to my way of making tables and vision,I'm sure not allowed or granted to me, I build tables I don't make "mods" no offense to anyone.
An type FizX-Lite.....it had been proposed by me at that time, then I took a step back, and on the other hand I was no longer active in FP,but don't talk about FizX-Lite for now.

I understand your vision very well, you have integrated everything in this FizX 3.0, for every user who downloads the table and plays with it, but let me tell you, there are not only more or less beginner users, there are also builders who perhaps have the their ideas and vision, that's what I meant with my three questions in the other thread.

 

[AnonTet]

Let me be blunt on this because you're also very strict with your tables:
- You either use FizX or you don't. If you don't, you can't tag a table with FizX.
- FizX-Lite is dead. There will be no FizX that suit you or anyone else in particular, no matter how experienced, vision, religion, political view or whatever notion can be imagined. There are however, many options to make FizX behave the way you want to a certain degree because FP physics engine has limitations at its core. Use those options.


TLDR for FizX specific stuff:

' *********************************************************************************************************** '
' * FizX code is for personal use only. * '
' * Permission is given to use on any table and can be distributed with them if author is credited. * '
' * It cannot be sold alone or as a bundle with any software. If you paid for this you are being scammed. * '
' * No modification of this code is permitted without written consent from the author (@JLou5641). * '
' *********************************************************************************************************** '

 

[TerryRed]

The AIO Example table's code is mostly FizX 3.0 (with includes automatic dynamic ball hit sounds) and Ball Rolling. The extra code for PUP and DOF support is "very" small compared to the physics code. So you are adding very little extra code for those.

If you are hoping to get FizX 3.0 code and functions to be as small as the old DF1 flippers... it won't happen. Again, you are making more work for yourself if you try removing anything.

It's VERY easy to add FizX 3.0 to another table by just following the AIO Example tutorial (it can be done quickly once you know how). If however your intent is to not use the AIO Example table's code and FizX v3.0 in it's entirety (following the tutorial) as it's intended, then I won't be able to help you, as that is not what this topic was meant for.

 

[Paolo]

The extra code for PUP and DOF support is "very" small compared to the physics code. So you are adding very little extra code for those.

Yes I understand, but since I don't use it, and I can't use it(PUP and DOF), so I don't need to insert it, this would be having less codes to insert.

If you are hoping to get FizX 3.0 code to be as small as the old DF1 flippers... it won't happen.

I never hoped or thought about it!!

If however your intent is to not use the AIO Example table's code in it's entirety (following the tutorial) as it's intended, then I won't be able to help you, as that is not what this topic was meant for.

My intent is to see how my table works with FizX, obviously without adding any code that I don't think is necessary for the purposes of my table itself.......if you want to help me more than thank you I can't tell you, and you would make an author happy about to retire and hang Fp on the nail of the wall.
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Probably someone misunderstood when I say a FizX suitable for me, I meant without some codes that I consider unnecessary for the purposes of my table.
don't need to be so hard...... I don't understand this sentence "you're also very strict with your tables"like all the rest of the comment, superfluous words for me in this context, and without knowing what I'm really asking.
FizX-Lite is dead.......it's not my problem, and I think it's a penalty.

 

[TerryRed]

Yes I understand, but since I don't use it, and I can't use it(PUP and DOF), so I don't need to insert it, this would be having less codes to insert.

The PUP / SSF / DOF functions are part of the commands and control code that this table is using for FizX, Ball Rolling, and the automatic ball hit sounds (and PinMechSound commands). It's kind of the whole point of the creation of this example table, as it complements JLou's intention for FizX v3.0 to begin with (and it's what he wanted) :)

I do understand not wanting extra stuff you don't use, but this is an integral part of FizX 3.0 itself. You aren't benefitting yourself by trying to remove it. You are just creating more work for yourself, and possible complications, and I can't (won't) help / support anything customized that doesn't use the original code as it was intended. I've done my part and have shown how it works and how to use it. I put in the extra work to allow anyone to disable the features they don't want to use (or support).

 

[Paolo]

and I can't (won't) help / support anything customized that doesn't use the original code as it was intended.

ok, you made yourself very clear!!

 

[Paolo]

a question if I may ... because in Sub CreateNewBall() there are three lines of code equal?
in my opinion it also needs to be said if some kind of code should be inserted in the original code of Fp



like that

 

[JLou5641]

don't worry about that.. It's already in my "to do list" for update .
Next update will be script optimization... All PFTrajectoryCorrection will not necessary anymore in all place on script.

 

[TerryRed]

a question if I may ... because in Sub CreateNewBall() there are three lines of code equal?
in my opinion it also needs to be said if some kind of code should be inserted in the original code of Fp

View attachment 38677

like that
View attachment 38678

I think JLou may have added that into the table from before on older FizX versions (it doesn't hurt if it was in there), but its not needed.

You don't add PFTrajectoryCorrection to the table script at all for FizX v3.0 (that was only for older FizX). I haven't added it on any of the 12 tables I've updated with FizX v3.0. It's why I never mention needing to do it on the updated Tutorial for FizX v3.0.

If there is a need to add extra lines of code for FizX or anything else to the rest of the table (like for slingshots, Flipper Nudge), I mention that in the Tutorial, and I note it in the script. (needed for FizX)

 

[pinhead1]

ALL in One Example table Tutorial​

Add FizX, FLEEP, PUP SSF, DOF to any Future Pinball table! Easy!​

What was once a daunting task, has now been made easy! Add the latest FizX physics, FLEEP sounds, Ball Rolling sounds, PUP SSF and DOF to any Future Pinball table quickly and easily using this new All In One Example table and Tutorial!



View attachment 37532


FizX Physics System for Future Pinball - new updates for v3.0

• new! Flipper Nudging! (when a ball rolls on a flipper, rapidly tap the opposite flipper to nudge ball back down the flipper)
• independent settings for each flipper
• new coil system based on the new custom BAM FSRC
• new EOS system which keeps flipper momentum on the first stroke. Huge improvement on backhand shots and post passes!
• new bouncing setting which is easier to understand and set
• new Flipper Omega and Mass System
• new ball vs ball physics setting. Ball hitting other ball has more bounce
• new PHYSICS XML settings
• new Ball Spinning Momemtum absorption and bounce deflect on hit for Flipper and Rubber
• Tap pass and Tap shots are much easier
• table slope and other new settings are now defined in FizX General Settings

To put it simply... all the quirks from FizX v2.0 have been fixed. Flippers have full power now when they should. Post passing, and backhands are easy and correct now.

Flipper Nudging is a real thing now, as long as the ball isn't rolling too fast on the flipper (the nudge strength can be adjusted in FizX settings).


This video below will briefly go through the new FizX 3.0 settings and changes, the new AIO Example table and Tutorial, and it will showcase FizX 3.0 in action with amazing new table updates I have coming out!

---

Please note, that the AIO Example table with FizX v3.0 is not the same as FizX Lite. Their code is not compatible or interchangeable!

---

DESCRIPTION of TERMS and FEATURES


FizX

- this is a new physics system for FP (created by JLou)
- it has adapted techniques, similar to nFozzy physics on VPX, to be used on FP to drastically improve FP's physics and flippers
- it uses BAM features, new code, new models (for rubbers, bumpers, slings, ball, etc) to make this happen
- automatically outputs FLEEP sounds of most ball hit events based on the material / speed, etc
- any FP table can be updated to use FizX physics (some old tables may need additional table changes to properly modernize them)

FizX Tweaker Tool

- a tool using a DMD to display FizX settings (while playing) so they can be adjusted in real-time to see their effect
- any changes made using this tool will still need to be manually set in the FizX settings in the table script

FLEEP Sound

- a very high-quality set of mechanical sounds recorded by FLEEP
- each type of sound uses multiple recordings that vary slightly to create a much more dynamic / natural experience
- it's ideal to also try to control the output / volume of these sounds based on ball speed / collision material

DOF (Direct Output Framework)

- an app used to control feedback (solenoids, shaker, chimes, etc) and lighting on real cabinets
- this can be used with apps like VP and FP to have real feedback and lighting activated by table events
- this tutorial adds direct DOF support! (DOFLinx is not used, and must not be running!)

PUP (Pinup Player)

- an app used to playback video, audio, text on separate displays / windows
- this can be used with apps like VP and FP to control modern score / video displays or playback audio / music / SSF
- PUP SSF uses pinup player to playback mechanical sounds and ball rolling sounds based on their position in the game
- PUP DMD is the combined output of text / videos / images on a display (can be similar to a modern pin's LCD display)
- PuP-Pack is a folder that contains the collection of video / audio / fonts / config files used by Pinup Player for a specific table

SSF (surround sound feedback)

- a method of playing mechanical-based sounds within in 3D / surround space based on the position of the item on the playfield
- this can be used in any speaker configuration (stereo, 5.1, 7.1)
- when used in a cabinet with multiple exciters / shakers, it can make it sound like you have a real pinball game inside your cabinet

FP Sounds / FP Mechanical Sounds

- the sounds played by FP (using playsound) for mechanical / hits events for things like flipper, slings, bumper, ball hits, etc
- these can only output in mono or stereo, and do not support positional output

PinMechSound

- a command (and code) created by TerryRed that will control the output of FP Sounds, PUP SSF, and DOF automatically
- only FP Sounds or PUP SSF are output at one time
- if PUP SSF is disabled (or not installed), then FP Sounds are used
- DOF (if installed and enabled) will always be outputted

---

########## ALL in ONE Example Table Tutorial ##########​

What will this add to a Future Pinball table?

- FizX v3.0 physics system
- FLEEP mechanical sounds
- dynamic ball hit sounds (based on speed and materials that are hit)
- ball rolling sounds
- surround sound feedback (PUP SSF)
- DOF (cabinet feedback)
- PUP (for "simple" PuP-Packs)

This will result in a FP table supporting the above features automatically, even if you don't use all the features yourself.

Simply follow this tutorial (in order) to get the essentials installed. You can make changes as needed for your table and preferences.

You can get the essential FizX items / physics, fleep sounds, ball rolling and dynamic ball hit sounds working very quickly using this tutorial and example table!

I can add the essential files and code to a table in under 5 mins and it just works!

The extra steps for adding FizX rubbers (required), linking PinMechSound commands (recommended) doesn't take long once you know how to add it to the table's specific items and events.

---

Table version: 3.00.27 (June 14 - 2023)

FizX: v3.00


CHANGELOG

3.00.27 (June 14 - 2023)

- updated table for all new FizX v3.0 code and features
- added flipper nudge commands for each Flipper's .SolenoidOn command
- updated FizX Tweaker Tool for new FizX settings
- updated FizX Tweaker Tool to remove all "Save to fpRAM" and "Load from fpRAM" options
- added triggers to ramps and code examples to change ball rolling sounds when on ramps
- the tutorial is now in a PDF and docx file!

---

What is REQUIRED?

- the All in One Example table zip file's content
- BAM 1.5-363 or higher

ravarcade.pl - Download

Better Arcade Mode for Future Pinball Cabinet

www.ravarcade.pl

A "normal" Future Pinball table is needed!

- we need a future pinball table with nothing specialized added to it (this will conflict with the new features!)
- remove any previous physics related code or timers. Remove any PHYSICS XML code (the green text code)
- if any special / custom flipper models are used (Zed physics), replace them with normal flipper models!
- remove any code / timers / commands used for any previous ball rolling sounds (smoke)
- if a table was updated for DOFLinx, remove all DOFLinx related code (we are now using direct DOF support)
- confirm your table is working COMPLETELY after removing all the above!
- DO NOT go farther with this tutorial until this is completed!



DOF and Pinup Player (PuP) are NOT required to be installed for the table to work!

• PUP SSF and DOF are "extra" features that will be used if they are installed (and enabled). If they are not installed (or they are disabled), then the table will use FP sounds for everything automatically

PUP SSF and the FP_PUP_SSF pup-pack

• if the player has PUP installed, but does not have the FP_PUP_SSF pup-pack installed (included with this tutorial), then if PUP_SSF_Enabled = true, the player will have no mechanical / ball rolling sounds, as PUP won't be able to load any sounds from the FP_PUP_SSF PuP-Pack
• I recommend you include the FP_PUP_SSF pup-pack folder with your tables that use this AIO Example code. Make mention in your download post about copying FP_PUP_SSF to the PUPVideos folder for anyone who has PUP installed
• if you do not want to include the FP_PUP_SSF pup-pack with your table, or don't want to support PUP features on your table... then be sure you have PUP_SSF_Enabled = false set in your table script

---

What this Tutorial will NOT do:

- add the same features as PinEvent tables. No PUP DMD! No PUP Stream!
- it won't create a "PinEvent" table (PinEvent = TerryRed releases)
- it won't go into great detail about all of FizX's settings, and physics, and fine tuning, etc
- it won't tell you how to remove older physics or other ball rolling sound methods
- the new Ball Rolling code won't automatically change the ball rolling sounds when rolling on plastic ramps, or wire ramps. You will need to do this yourself. Only PUP SSF will play more than one ball rolling sound at a time.
- it won't tell you how to update every FP table for issues not covered in this Tutorial. Some older tables need to be updated / modernized to properly use FizX physics (some tables use multiple playfield surfaces, and workarounds for old FP physics that can have a negative effect, and will need to be removed, as an example)

This tutorial is more about getting everything easily installed and running on another table. There will be other posts (made by others) that will go more in-depth about FizX settings and physics. I will provide links to them on this page as they are created.

---

Download the AIO Example Table and Tutorial zip file:

• the latest AIO Example table's zip file is attached to the bottom of this post
• open the Tutorial file (pdf, or docx) and follow the instructions in order!

IMPORTANT: Do not add new changes to the main code that the Example Tables uses! Use it as it was intended following the written tutorial! This table and its code may not always have the latest WIP / beta code for FizX, etc. Trying to mix in different bits of code or updating a table in a different way may result in the All In One Example table's code not working correctly for your table! Just follow the tutorial (in order), and it should work fine for you.


For more details about FizX settings, JLou will have more information here:

Help - BAM - FizX - FizX 3.0: How to tune physics in FizX profile

Coming soon....

pinballnirvana.com

If all went well, you should have a FP table that:

- plays MUCH better and more realistically with FizX physics
- complete dynamic ball hits sounds for the entire table based on all materials being hit
- ball rolling sounds that automatically work
- full SSF for everything on the entire table (if using PUP SSF)
- FP Sounds for all mechanical events (flippers, slings, bumpers, etc)
- DOF feedback for solenoid based events


Enjoy a new world of better physics, sound and feedback in FP!


Thanks to:

- JLou for his amazing work and dedication to FizX physics on FP
- AnonTet for his support towards FizX
- ravarcade for more excellent updates to BAM that made this all possible
- smoke (used small bits of your ball rolling code for the new unified ball rolling code)
- Nailbuster for DOF and PUP support
- all others who have shown support with their time and testing and feedback

---

Video Example:

This video below is a non-stop, start to finish example of me showing 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.

The video is broken into chapters! So you can go at your own pace, and easily pick up where you left off.

Adding the new code and essentials items is quick and easy to do to get a table up and running... its the table specific additions that take the most time afterward. I probably spend more time explaining things and showing how they work before and after than I do actually updating the table. :)


Note: this video was created using an old version of the AIO Example table and an old version of FizX. The process for using the AIO Example table code is still mostly the same, but there are some differences. With the current AIO Example table and FizX code:

• you now MUST set the table slope in in FizX General Settings (this overrides the slope settings in the table editor!)
• you do not need to set the flipper swing angle in FizX settings
• you need to add extra commands for flipper nudge
• FizX Flipper settings and General settings have changed
• FizX Tweaker Tool no longer has "Save to fpRAM" or "Load from fpRAM" options

ALWAYS follow the "written" tutorial for the most up to date and correct information! Only use the video as a visual guide to help you along!


I will update the All In One Example Table and the Tutorial as needed in the future when significant changes / features come along.

TerryRed

---

How to update a table (with older AIO and FizX code already added) to use the new AIO Example Table code and FizX v3.0:

• if you have tables you've already updated, never fear. You can update your table with little hassle
• it is VERY important that you do this correctly as there are many changes in FizX v3.0 that are not compatible with older versions
• its easy to do and FizX v3.0's changes are game changing compared to older versions

Goto this post and follow the steps in order:

All In One Example Table - FizX, FLEEP, Ball Rolling, PUP SSF, DOF - Easy to add!

Looking at it again.... it's correct. :) Sub OnPreHitFlipperSettings(FlipperExt) if BallSpeed_Volume_enabled = true then If FlipperExt.hit = True and FlipperExt.BallVSpeed > 100 then PinMechSound ("mech_Flipper_Rubber_" &Int(Rnd*7)+1), "ball", (( xBAM.Ball.HitSpeed / 1000 ) *...

pinballnirvana.com

i have not finished my new install.
i still have some work to do including the install of FP and get a new card.
isn't this already included in the new FP installer or do i need to add it?

Add FizX, FLEEP, PUP SSF, DOF to any Future Pinball table! Easy!​

 

[TerryRed]

i have not finished my new install.
i still have some work to do including the install of FP and get a new card.
isn't this already included in the new FP installer or do i need to add it?

Add FizX, FLEEP, PUP SSF, DOF to any Future Pinball table! Easy!​

This is not an update to FP itself. It's an example table and tutorial that shows how to update a FP table to support FizX physics / Fleep Sounds / PUP SSF / DOF.

These features need to be manually added to each table (if you want a table to use them). It's not something that can automatically work for every table.

This table and tutorial is not something you need if you just want to use FP.

 

[AnonTet]

Probably someone

Someone? Isn't it obvious? This is funny

misunderstood when I say a FizX suitable for me, I meant without some codes that I consider unnecessary for the purposes of my table.

Well I've seen you do it multiple times starting on lady diamond. I didn't misunderstood anything. And you just said code unnecessary for my purposes.

don't need to be so hard...... I don't understand this sentence "you're also very strict with your tables"like all the rest of the comment,

Who's the one who made a fuss when someone used his table to demo in VPE? I would have been honored if a table of mine was featured in something.
Where can your tables be downloaded from?
Who decided to keep the tables to himself. I (not someone) said before it's a shame and though I understand it's really selfish and hypocritical after decades of public availability... Not that they can be found if wanted though.

superfluous words for me in this context, and without knowing what I'm really asking.

Another humorous content to me. Because it is funny how people tend to forget history. Hopefully now you understand the context: what goes around...

FizX-Lite is dead.......it's not my problem, and I think it's a penalty.

It seems to be because it is what you're trying to achieve: a working version that suits your needs... And as usual, your overcomplicating things which was mentioned a few times now.

 

[TerryRed]

I just want to point this out to everyone...

This topic is about the All in One Example table, it's "complete" code and FizX v3.0, and it's tutorial. NOTHING ELSE.

That means it's intended for discussion and support of only the following:

- FizX v3.0 (no other variations)
- DOF
- SSF
- PUP
- Fleep sounds
- Ball Rolling Sounds

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

PUP and DOF (optional)

To clarify, again, you do NOT require PUP, or DOF installed to use this code, to test a table using this code, or to play any table using this code. If you don't want to use these features, or don't want to test these features, or don't want to support these features on your tables using FizX v3.0... then just disable these features by setting the following in the table script:

DOF_enabled = false
PUP_SSF_enabled = false

Nothing else is required.

If you are not going to take the extra steps to add in PinMechSound commands to your entire table, then both of these features MUST be disabled! This will ensure all sounds from FizX are also only played using FP playsound commands and sounds.



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

PinMechSound commands (optional, but recommended)

- this part of the tutorial is NOT a requirement, but highly recommended, so that all SSF and DOF features will work for everyone
- if you don't want to worry about supporting these features, or find it intimidating, then simply don't add PinMechSound commands
- if you are not going to take the extra steps to add PinMechSound commands, then you MUST make sure that both DOF and PUP are disabled, as noted above
- if you are not going to use PinMechSound commands, then you can remove that section of commands if you wish, but DO NOT remove the PinMechSound Sub and code!



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

Drop Target walls (optional, but recommended)

- depending on the table and layout, adding in FizX drop target walls (and commands) can be a benefit, but its not a requirement
- this can be a bit tricky to properly add, depending on the complexity of the table
- if you are not sure about how to do this, you can skip this part and come back to it later on (I don't do it on all table updates)

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

Bumpers (optional, but recommended)

- many older FP tables used different methods to improve bumpers (em kickers, drop target skirts, etc)
- with FizX, its best to remove these items and their commands, and replace them with the newer FizX models and their settings
- this will ensure they will work correctly

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

Ball Rolling Sounds (optional, but recommended)

- this can be disabled if you don't want to use it, or you want to use another ball rolling sound method
- nothing else is required




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

What is REQUIRED

All other parts of the All in One Example table's code and the tutorial's methods are REQUIRED for FizX v3.0!

- removing all aspects of older physics methods, and ball rolling sounds, etc and confirming the table works 100% FIRST
- textures, models and sounds
- slingshot diverters
- FizX rubber posts (diverter models) and rubber band walls (named correctly and added to FizX General Settings in the script)
- timer for Ball Rolling sounds (if using this feature, but should be added just in case)
- FizX Hud DMD for Tweaker Tool (not required for FizX to run, but you'll get errors if its not added. You need to edit the code if you don't add it)
- adjustments in the editor (flipper names and settings)
- new commands in code for slingshots, flipper nudge, etc
- changes in the script if needed for flipper names being changed, etc
- adjustments for the PHYSICS XML code section, only if required (only make changes to the noted items)
- adjustments to table items (kickers, etc) only as required, and possibly to match changes to the PHYSICS XML code
- adjustments to FizX settings in the table script as needed or desired (FizX v3.0 default settings are good for most tables to start with)
- anything else I missed

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


The ALL in ONE Example table and FizX v3.0

- this table was JLOU's creation as was FizX v3.0
- he asked me to help him implement support for FizX / DOF / PUP / SSF / Fleep / Ball Rolling into one code standard for FP (that no one had done before). This is what JLou wanted for FizX!
- he also asked me to help create the tutorial, as English is not his native language
- many aspects of the table's mechanical sounds / code are now tied directly to FizX. They are not optional.
- the extra features of PUP / DOF / Ball Rolling Sounds can be disabled. No one has to use them!
- I put in a lot of work to ensure no one was forced to use any extra options they didn't want to. Nothing else is required by you guys!
- no one should expect JLou or myself to undo all the work we have done just because you want something different. Take it or leave it.


This example table and the tutorial was what JLou had wanted for a long time. It is a "complete" game changer for FP. This is a VERY good thing. This is what is REQUIRED to make better and complete physics improvements happen on FP. That is what FizX was all about from the beginning! Not just a quick copy and paste of a small bit of code to improve only the flippers.

If people can take days / weeks / months to create / update / mod a table.... if they want it to play better, the least they can do is take the very SMALL amount of time it takes to properly and completely update a table for FizX. This is also what is required for VPX tables to be updated for better nFozzy physics as well.

It's not "hard" to add once you learn how to do it, as has been shown by @HZR or @Gamer7 ! These guys are completely new to FP table modding. If they can do it, there is no reason why anyone else can't if they take the time to learn how.

If someone doesn't want to take the extra steps and time to do the "minimum" that is required for ALL of FizX v3.0 (not just better flippers)... then you want something else as that is not FizX.

That's ok if you don't want to do that and want to do your own thing for your own projects. However, if you are going to upload and share those creations publicly, don't call what you added to the table FizX, because that is no longer accurate, and is a misrepresentation of JLou's hard work... and what others have come to expect from a table labelled as having FizX physics.


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


How long to add just FizX v3.0?

It does not... I repeat... does not take multiple hours just to add FizX v3.0 physics, (if that is all you want to add) using the AIO Example table and tutorial.

Don't let the example video throw you off, as it is an unedited video (with me "explaining" everything), that goes beyond what you need for FizX 3.0, as I'm also adding in PinMechSound commands and more on a table I've never looked at before.

I can have a table completely updated for "all" of FizX v3.0 physics (code, dmd, sounds, models, textures, rubbers and slings) within 30 mins. This is assuming there are no table conflicts that need to be resolved, or additional table adjustments / tuning.


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


So I'll say again....

This topic is about the All in One Example table, it's "complete" code and FizX v3.0, and it's tutorial. NOTHING ELSE.

If you want to discuss anything else... take it elsewhere.

If anymore drama continues.... I'll ask the moderators to lock this topic, and everyone can follow the tutorial and fend for themselves. I'm tired of seeing my tutorials and uploads get spammed with this stuff.

 

[bcarter1234]

I hope this is sufficiently on topic. If not, let me know and I'll post a separate thread. I'm nearly finished updating a Future Pinball version of a woodrail table to FizX 3.0, I just need to go through the SSF setup steps. It is currently playing very well.

I used only the PDF and it was manageable even though I have no modding experience. I suspect the video would have made it easier but I figured I could go back and watch it if I got into trouble. That said, I apologize if my question below is answered in the video.

As my first effort it took a few hours a lot of which was going back and forth trying to make sure I was doing the right thing. Having done one I think an hour or a little more would be close for the next one. This table has 36 RubberPosts and 22 RubberBands. Positioning them took a big chunk of the time.

The biggest issue I had came from an error related to "InlaneTrigger" being an "undefined variable" in the Mechanical Sounds and Feedback section. I'm going from memory so that may not be the actual error wording.

I fiddled around for quite a while before settling on taking a section of a line of code from the flippers to replace "InlaneTrigger" with LeftFlipper and RightFlipper respectively. No more error message and it sounds good on the desktop.

What should I have done?

I have optional solenoids on the cabinet flippers but leave them switched off most of the time. I find the SSF flipper feedback to be subtle but effective. On this particular table the placement of the solenoids would be just about perfect for the slingshots anyway.

Thanks for any guidance.

 

[TerryRed]

The biggest issue I had came from an error related to "InlaneTrigger" being an "undefined variable" in the Mechanical Sounds and Feedback section. I'm going from memory so that may not be the actual error wording.

The error means you are trying to reference an item on the table that doesn't exist... at least not by that name.

With PinMechSound, you need to change the "fp_item" part of the command to an item on the table that has the following in the Future Pinball Editor:

- name
- x position
- y position

If it doesn't have ALL of those, then when the PinMechSound command is given, FP has no idea where the item is located, or can't find an item with that name.

You need to change those PinMechSound commands to match what your specific table is using, as not all tables use the same names for similar items.

Change the InlaneTrigger to an item on the table that is closest to that position.

 

[bcarter1234]

TerryRed,

Let me know is this is a good solution. In the script section below I replaced the "LeftInLaneTrigger" with "SlingDiverter2" and "RightInLaneTrigger" with "SlingDiverter3". It seems to be working fine.



Previously I misunderstood thinking LeftInLaneTrigger defined a sound file, not a location.

 

[Popotte]

You can add an invisible object in the middle of the slingshot (bulb or whatever you want) and assign it in the PinMecSound sub.

 

[bcarter1234]

While I'm asking...

I replaced the bumpers and skirts as prescribed in the PDF. They work great. How do I get visible red bumper skirts? It appears I'm only seeing the bumper body.