#54 Timer in "Super Mario Land" cycles between 400 and 500

v1.5.x
closed-fixed
General (30)
5
2010-01-10
2010-01-01
Anonymous
No

In "Super Mario Land" the time limit indicator does not count down. It goes like: 417, 420, 437, 450, 479, 412, 420, 433, 450, 479, 417, ...
This also means that at the end of level 1-1 you get stuck at the point when bonus points are added for the remaining seconds.

Discussion

  • Jörg Jahnke

    Jörg Jahnke - 2010-01-02
    • assigned_to: nobody --> joergjahnke
    • status: open --> pending
     
  • Jörg Jahnke

    Jörg Jahnke - 2010-01-02

    Can you give me a bit more details? Where is this time limit indicator, and is there something special I have to do to see it? Perhaps a screenshot would be helpful.

     
  • Nobody/Anonymous

    Sorry for being wage. I'll go into more detail. When playing Super Mario Land 1 you see the word TIME on the top right of the screen. Below you see a number which starts at 400 and counts down by one every second. When it reaches 0 Mario dies. At the end of each stage you earn points for the remaining seconds. In JSwingBoy the first value displayed is 400 (correct). But it does not count down. Instead it jumps up through some numbers. Before the numbers get bigger than 500 it starts between 410 and 420 again. The order of number looks similar to this: ..., 417, 420, 437, 450, 479, 412, 420, 433, 450, 479, 417, ... To replicate just start Super Mario Land in JSwingBoy and watch the number in the top right corner.

     
  • Nobody/Anonymous

    • status: pending --> open
     
  • Jörg Jahnke

    Jörg Jahnke - 2010-01-02

    Thanks, I'll have a look.

     
  • Jörg Jahnke

    Jörg Jahnke - 2010-01-02
    • status: open --> open-accepted
     
  • DerKoun

    DerKoun - 2010-01-03

    (got myself an account) I noticed one more thing: the music is playing way too fast. Not sure if this is related to this issue. Also I sometimes get "index out of bounds" exceptions when starting the game.

     
  • Jörg Jahnke

    Jörg Jahnke - 2010-01-10

    Just a short update: The problem seems to be tougher to solve than I thought. I did some debugging and until now I could not nail down the problem. So it might take a bit longer...

     
  • Jörg Jahnke

    Jörg Jahnke - 2010-01-10
    • status: open-accepted --> closed-fixed
     
  • Jörg Jahnke

    Jörg Jahnke - 2010-01-10

    In the end I stumbled over the wrong implementation of the CPU's "DAA" instruction, which also caused the problem, so that the fix was easier than I thought. I am going to create a new release within the next few days.

    fixed in HG rev. 416

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks