- This topic has 109 replies, 25 voices, and was last updated 3 years, 5 months ago by studlygoorite.
-
AuthorPosts
-
July 2, 2020 at 11:23 pm #189635
Hmm… with the high score update, I get this:
It was working fine before the update… what can be the reason for this problem?
You need to login in order to like this post: click here
July 3, 2020 at 12:28 am #189637I had that too and deleted a couple roque centigrade files in my tables folder to get it to run.
You need to login in order to like this post: click here
1 user thanked author for this post.
July 3, 2020 at 1:18 am #189639Pretty sure that JR is right. Delete old highscores. I had the “same kind of error”, some weeks back, using Loserman’ Jackpot – not cleaning it out after testing the kees version a long time ago.
You need to login in order to like this post: click here
1 user thanked author for this post.
July 3, 2020 at 6:39 am #189654Yes, I should have mentioned. Wipe out your high score file and it will work fine.
You need to login in order to like this post: click here
1 user thanked author for this post.
July 3, 2020 at 7:10 am #189656Yes that should fix it. In any table that uses a text file to save game settings like high scores, number of balls, free or coin the script looks for specific values in specific spots in the text file. If the script sees something unexpected in one of those spots it will throw out an error.
Sometimes when a table exits incorrectly a character like an @ will get written into the text file. In this case the script is looking for a cdbl (type of number) so the script will error. Another cause is if the table author has changed what the script saves (like getting rid of a variable for ball shadows) and the new script tries to read an “older version” that contains the data in a different format or order, an error will occur.
Don’t ask how I know all of this
You need to login in order to like this post: click here
1 user thanked author for this post.
July 4, 2020 at 12:01 am #189805How do you know all this?
This is interesting. I’ve had random EM tables throwing script errors at me and figured it was just my set-up and would usually delete the nvram but they don’t always have them. I think I have a few em’s buried and forgotten because I couldn’t bring them back to life. Care to share any more thoughts on how to prevent scripts from misbehaving? I’ve had to re-set Scuba 100 times!
You need to login in order to like this post: click here
July 4, 2020 at 11:31 am #189861I had that too and deleted a couple roque centigrade files in my tables folder to get it to run.
Thanks. It was actually not in the Tables but the Visual Pinball/User folder where I had to delete the high score files to get it running.
You need to login in order to like this post: click here
July 4, 2020 at 1:02 pm #189869Yes the files are in the Visual Pinball/Users folder which sis what that folder is intended for.
@JR I know these things because I’ve caused them and had to fix them…
You need to login in order to like this post: click here
July 10, 2020 at 3:44 pm #190742Very retro, just like the old pinball machines.
Very nice table.
CongratulationsYou need to login in order to like this post: click here
1 user thanked author for this post.
September 3, 2020 at 9:29 am #199276Thanks for the update bord. Gave it a spin last night.
Anyone else notice the special light coming on when it shouldn’t?
Current Project: Perpetual updates of VPX physics.
You need to login in order to like this post: click here
November 6, 2020 at 9:39 am #208821Very nice table, looks and plays great, thanks for sharing.
You need to login in order to like this post: click here
-
AuthorPosts
Forums are currently locked.