Currently, there are 0 users and 0 guests visiting this topic.
Viewing 10 posts - 101 through 110 (of 110 total)
  • Author
    Posts
  • #189635
    htamas
    Participant
    @htamas
    Member

    Hmm… with the high score update, I get this:

    Capture

    It was working fine before the update… what can be the reason for this problem?

    #189637
    JR
    Participant
    @jfr1
    Member

    I had that too and deleted a couple roque centigrade files in my tables folder to get it to run.

    1 user thanked author for this post.
    #189639
    Thalamus
    Moderator
    @thalamus
    ContributorMemberModerator

    Pretty 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.

    1 user thanked author for this post.
    #189654
    bord
    Moderator
    @bord
    MembervipContributorModerator

    Yes, I should have mentioned. Wipe out your high score file and it will work fine.

    1 user thanked author for this post.
    #189656
    Scottacus
    Participant
    @scottacus
    MembervipContributor

    Yes 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 :whistle:

    1 user thanked author for this post.
    #189805
    JR
    Participant
    @jfr1
    Member

    How 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!

    #189861
    htamas
    Participant
    @htamas
    Member

    I 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.

    #189869
    Scottacus
    Participant
    @scottacus
    MembervipContributor

    Yes 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…

    #190742
    konfrad
    Participant
    @konfrad

    Very retro, just like the old pinball machines.
    Very nice table.
    Congratulations

    1 user thanked author for this post.
    #199276
    rothbauerw
    Moderator
    @rothbauerw
    ModeratorContributorMembervip

    Thanks 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.

Viewing 10 posts - 101 through 110 (of 110 total)
  • You must be logged in to reply to this topic.

©2020 VPinBall.com

Log in with your credentials

or    

Forgot your details?

Create Account

The Vpinball app

FREE
VIEW