If you don't have problem with score too high (overflow error in script) and table works fine with results limited to 9 digits (exactly 2 147 483 647 max), when don't do anything.

With new BAM version (v1.4-183) max score may be: 922 337 203 685 477, but you will need to change few things in script. Sometimes it will be easy, sometimes not.

How to enable support for 15 digit score.
Support for big score is not enabled by default. To enable it you need to add one line in script:

Please note comment char (apostrophe) at line begin. This line will not be executed, but it is enought to let BAM know, that we want to enable support for big scores.

How it works and what are limitations.
Here is list of nvRAM registers with support for biger than 32 bit numbers:
nvScore1, ... , nvScore4, nvScore(i),
nvHighScore1, ... , nvHighScore4, nvHighScore(i),
nvSpecialScore1, ... , nvSpecialScore4, nvSpecialScore(i),
nvSpecialHighScore.
All that registers are now CURRENCY type.
See: https://msdn.microsoft.com/en-us/vba/la ... -data-type

So, max value is 922 337 203 685 477.

Because this data type need more "bits" to store vaule than normal 32-bit integer, when BAM will use nvS14, nvS15, nvS16 to store only few vaules between FP table reload/restart.
Stored are: nvHighScore(i), where i = <1, ..., 10> and nvSpecialScore1.
(Why nvSpecialScore1? because "Bride of Pinbot" use it).
All other values are stored as maximum int (2 147 483 647) between FP table restart.

Please remember. Do not use nvS14, nvS15, nvS16 if you want to use big score numbers.

.... and that is only beginning. Some scripts need special modification to work correctly.
Here is list of error/problems and solutions.

1. Overflow error with modulo operator.
In script you can find line like this:
LastDigit = nvScore(i) mod 10
Problem is in modulo division in vbscipt. It converts first arg (nvScore(i)) to 32-bit integer and if you have bigger value store in it you will get overflow error.
See: https://www.promotic.eu/en/pmdoc/Script ... at/Mod.htm

Solution:
We need to use own "smarter" modulo function (add it to script):

... and replace line from example above to:
LastDigit = Modulo(nvScore(i),10)

2. Overflow error with integer division operator.
In script you can find line like this:
thousands = nvScore(i) \ 1000
Problem is in integer division operator (\). It converts first arg (nvScore(i)) to 32-bit integer and if you have bigger value store in it you will get overflow error.
See: https://www.promotic.eu/en/pmdoc/Script ... vision.htm

Solution:
Replace division with something like this:
thousands = Fix(CDbl(( nvScore(i) / 1000))

3. Overflow error when you assign score to hud display / gas discharge segment displays / DMD displays.
In script lines like this:
SigDisp1.SetValue(nvScore1)
SigDisp1.Value = nvScore1
Source of problem is in function SetValue or type of Value variable for that objects.
In both case it is limited to 32-bit integer.

Solution:
If object (like gas discharge segment display) can display text, when .... display text. Like this:
SigDisp1.Text = nvScore1

If object can't display text, when use Modulo function (defined above).
SigDisp1.Value = Modulo(nvScore1, 1000000000)
In this example you will get last 9 digist of result diplayed.
If you need more digits (all 15?) when you will need 2 SigDisp and code like this:
SigDisp1Low.Value = Modulo( nvScore1, 1000000000)
SigDisp1Hi.Value = Fix(CDbl(( nvScore1 / 1000000000))

_________________
http://www.ravarcade.pl
Better Arcade Mode
current BAM version: v1.4-249, released: Feb 5, 2019

Absolutely brilliant work again Rav!!

Guys,

This is a great enhancement for FP. At least some of you have experienced problems with high scores causing an error. It's pretty disappointing when are playing your best game ever and then have it produce an error. The limit occurs when the score reaches about 2 billion. Rav's enhancement increases it to 922 trillion! Although 2 billion points may seem like a lot, it doesn't take all that long on quite a few solid state tables where you can be awarded several million points at one time.

Don't let Rav's requirements for making changes scare you off. I am a novice at scripting but I can fix many tables because no changes are required other than adding Rav's FixScore code. This is a list of tables I have tested and verified that the only change you need to make is adding this code below the line near the top of the script below the line that says that says "Option Explicit". You should be aware that the display may not be able to show the full score because there is not enough space for all the digits, but the fix will still work and it will add the full score to the high score list even if the in-game display doesn't show all of it.



There is an easy line of code you can add to test it. Just add the following line of code below the line that says "Sub FuturePinball_KeyPressed(ByVal KeyCode)". This script works on most tables although there are a very few exceptions (like "Bride of Pinbot"). After you add it, you just type the letter V to add 900 trillion points to the score. In fact, you can test tables not on the list this way and see what happens or you can do searches for the script that Rav talks about in the previous posting. If you want to do searches, look for "SetValue" and "AddValue" as it relates to the score (it may be also used for credits or other functions which are OK). Search for " mod " and back slash (\). Note that that a forward slash (/) is OK.



This is the list of tables that I have found so far that do not require any change to the script other than adding Rav's fix score code. I listed the specific version that I tested although the script is usually so similar between different versions that the code will probably work on all versions of the table. Three of the tables have ways of limiting high scores that I explain how to fix:

24 CE (Original Playfield) 1.01 x64 Zed Physics 1.0
AC DC 1.21 Zed Physics 1.11
Addams Family ULTIMATE 1.10
Aliens Legacy ULTIMATE 1.12
Apollo 13 1.0a
Astrohits, Tribute to the 80's RC2
* Attack From Mars ULTIMATE 1.02
Avatar ULTIMATE 1.01
Back to the Future (DE) ULTIMATE 1.04
Battle of Britain 1.0
Big Bang Bar 2015 2.0 HQ
Big Guns ULTIMATE 1.01 Physics 2.6
Blue Vs Pink v 1.0
Classic Panic 1.0
Dead Hunters ULTRA 1.01
Elvis 1.1 Night Zed Physics 1.0
Genie 1.0 Night Mod
Iron Man ULTIMATE 1.06
Junkyard Cats 1.0 Zed Physics 1.1
Knight Rider 2.0 Zed Physics 1.0
Lord of the Rings ULTIMATE 1.06
Masters of the Universe MASTERED Edition
Medieval Madness ULTIMATE 1.02
Pirates Of The Caribbean 1.0 Zed Physics 1.0
Robocop ULTIMATE 1.05
Scared Stiff 1.1a Normal Ledwiz HD Zed Physics 1.0
Shadow, The 1.0 Zed Physics 1.1
Spider-Man ULTRA 1.09 Physics 2.5
Three Angels ULTIMATE 1.02 Physics 2.6
TutenKham, Tribute to the 80's 1.0
** Twister 1.0
*** World Cup Soccer 1.31

* Attack From Mars has a line of code that divides the score by 100 to prevent the high score overflow. You will want to change this as I describe below because you won't need it anymore.

Change this line of code:

to this:


** Twister has a line of code that divides the score by 10 to prevent the high score overflow.

Change this line of code:

to this:



*** World Cup Soccer has some script that limits all scores to 1,499,999,990 points in order to prevent high score overflow. You won't need this anymore so you should find the following script and delete it or add an apostrophe to the beginning of each of the three lines.



As part of the testing phase, Rav sent me some tables that he fixed. I have posted the script of them so you can see how to change the ones that need changing a little better.

George

This is the first of the examples of Rav's fixes to some of the tables he sent me. This first one is an example of "1. Overflow error with modulo operator." You can search the script for "High Score Fix" and you will see the changes that were made.

Bride of Pinbot ULTIMATE 1.02

Add this section of script below the constants:



Replace this section of script:

The script below is taken from "Bubble Bobble 1.0". It is an example of "3. Overflow error when you assign score to hud display / gas discharge segment displays / DMD displays" in Rav's first posting. It is not too difficult to fix.

When you find script like this:
Player1seg.AddValue(points)

it needs to be changed like this:
Player1seg.Text = nvScore(CurrentPlayer)

Likewise script like this:
DispSegPlayer1.SetValue(nvScore1)

needs to be changed like this:
DispSegPlayer1.Text = nvScore1

Galaxia 1.0 has 2 problems. It has examples of "1. Overflow error with modulo operator." and "3. Overflow error when you assign score to hud display / gas discharge segment displays / DMD displays". Rav also found a few errors in the script that I have included his fix.

Example of "3. Overflow error when you assign score to hud display / gas discharge segment displays / DMD displays"


Example of "3. Overflow error when you assign score to hud display / gas discharge segment displays / DMD displays"


Example of "1. Overflow error with modulo operator."


Continuation of example of "1. Overflow error with modulo operator."


Example of "3. Overflow error when you assign score to hud display / gas discharge segment displays / DMD displays"

George , so you and Rav don't blow a gasket, I wouldn't worry about all the tables?
No one has complained so it is likely no one had reached the crash point....in most tables anyways?

The Walking Dead (S3) 1.2 has examples of all 3 problems.

Example of "3. Overflow error when you assign score to hud display / gas discharge segment displays / DMD displays"


Example of "3. Overflow error when you assign score to hud display / gas discharge segment displays / DMD displays"


Example of "1. Overflow error with modulo operator."


Continuation of example of "1. Overflow error with modulo operator."


Example of "3. Overflow error when you assign score to hud display / gas discharge segment displays / DMD displays"


Example of "2. Overflow error with integer division operator."


George

I tested all the tables I discussed here to 900 trillion points. Of course, I used the cheat code. I didn't have any problems.

But then Rav has a point. Why change something that is not needed? The old EM tables would probably never need this change. But if you are creating a new solid state table, why not write the script to allow it to achieve 900 trillion points?

I am not sure all the tables I tested really need the change. Personally, I will definitely fix "Attack From Mars" and "World Cup Soccer" for my own use because I don't like the way the script changes the score. But then, I would definitely not tackle "The Walking Dead" (see the above posting) if there was not a real need for the change.

To my thinking, what is the harm if there is no change needed to fix the table other than adding the fix score code? If there are problems, we can fix them as they occur.

I suppose Rav may have a different opinion.

George

In my tweaking adventures, I believe
Slam, Francisco, Rom, Glxb,Polygame,Wild, Franzleo all use standard scoring routines (occasionally will use nvscore/10) so I think the simple xBAM.FixScore will suffice for most people


And I agree EM reel tables are designed for low scores, so they are not even a concern here (so that includes many Popotte tables)