[ChEeZeBaLL]

I found a bug at the end of Act 2 of Labyrinth Zone zone that I haven't seen documented anywhere. I've seen other people report the point bonuses that are placed too far before the sign post area, but if you enter the place that has the misplaced point bonuses and then go backwards, the screen will lock at that point and you will be unable to proceed to the right in order to cross the sign post (the screen locks in the correct area, but the signpost object disappears). The only thing you can do is wait for the time to run out.

An even more interesting find is that if you have over 50 rings, the big bonus ring will appear in the area you're stuck in. If you jump into it, Sonic will disappear but you will still be stuck on the level screen. If you wait for the time to run out, you will hear Sonic's dying sound and the time will stop at 9:59, but you'll be stuck on the level forever. The only thing you can do is reset or turn off the game.

Here's a video I made of the bug:

This post has been edited by ChEeZeBaLL: 09 April 2012 - 05:06 PM

[SpeedStarTMQ]

Interesting. I've never heard of this before, so thank you for documenting it.

Any tech members who can explain this?

This post has been edited by SpeedStarTMQ: 09 April 2012 - 07:38 AM

[jasonchrist]

I love Sonic 1!

[redhotsonic]

My only guess is that when you get close, the signpost loads, but when you go backwards, because of "markobjgone", the signpost gets deleted (like any other object), except when you go back to it, the signpost fails to reload itself. That may explain why the big ring is there (2nd time 'cause of your ring count) and the points objects you jump at is there, but no signpost.


Does this happen to any other level in Sonic 1? Or just LZ2?

[muteKi]

redhotsonic, on 09 April 2012 - 10:25 AM, said:

My only guess is that when you get close, the signpost loads, but when you go backwards, because of "markobjgone", the signpost gets deleted (like any other object), except when you go back to it, the signpost fails to reload itself. That may explain why the big ring is there (2nd time 'cause of your ring count) and the points objects you jump at is there, but no signpost.


Does this happen to any other level in Sonic 1? Or just LZ2?

Only on this act, I think -- I'm pretty sure the screen lock is much closer to the goal on all the other levels.

[X-Crim]

LOL I never see nothing as this xD

[ChEeZeBaLL]

redhotsonic, on 09 April 2012 - 10:25 AM, said:

My only guess is that when you get close, the signpost loads, but when you go backwards, because of "markobjgone", the signpost gets deleted (like any other object), except when you go back to it, the signpost fails to reload itself. That may explain why the big ring is there (2nd time 'cause of your ring count) and the points objects you jump at is there, but no signpost.


Does this happen to any other level in Sonic 1? Or just LZ2?

The erroneous screen lock is actually much further to the left than where the signpost is. Now that I'm thinking about it, the fact that there are misplaced point bonuses before the signpost means that there is probably an extra big ring object placed before the signpost as well. The big ring sprites only appear when you have over 50 rings and the tiles for it are loaded only when you get near the signpost screen lock area.

Basically, it's like the designers originally planned for the level to end in this area to the left, but then later decided to make it so you have to run a bit further to the right to finish the level, but they forgot to delete all the leftover stuff to the left, like the point bonuses, the big ring, and whatever defines the screen lock area.

^incorrect

This post has been edited by ChEeZeBaLL: 09 April 2012 - 04:34 PM

[MainMemory]

ChEeZeBaLL, on 09 April 2012 - 04:20 PM, said:

The erroneous screen lock is actually much further to the left than where the signpost is. Now that I'm thinking about it, the fact that there are misplaced point bonuses before the signpost means that there is probably an extra big ring object placed before the signpost as well. The big ring sprites only appear when you have over 50 rings and the tiles for it are loaded only when you get near the signpost screen lock area.

There's only one Big Ring, next to the signpost.

[ChEeZeBaLL]

MainMemory, on 09 April 2012 - 04:30 PM, said:

There's only one Big Ring, next to the signpost.

hmmm, nevermind then. I guess the signpost just isn't loading. redhotsonic's hypothesis is probably correct.

This post has been edited by ChEeZeBaLL: 09 April 2012 - 04:38 PM

[redhotsonic]

MainMemory, on 09 April 2012 - 04:30 PM, said:

There's only one Big Ring, next to the signpost.

Therefor, I am guessing I am right. You got close to the signpost so it loaded, ran away so it deleted itself, and then it never loads back up again. Whereas the big ring "probably" loads, then gets deleted when you run away, but does have the ability to reload.

You said it only happens to this level/act because the screen lock happens a lot earlier. This explains why in all other levels, because the screen lock happens a lot later, when you try to run away and you meet the screen lock, the distance to the signpost isn't far enough, so it doesn't delete itself. And the signpost won't load in the first place until the screen lock comes into play.

Anyone correct me if I am wrong.



EDIT:


I will say though, those first three points objects do seem quite far away from the signpost. But then again, the object's art doesn't load 'til the screen lock comes in. Maybe that's why it locks itself early?

This post has been edited by redhotsonic: 09 April 2012 - 04:39 PM

[Knucklez]

Well it could possibly occur in other levels besides LZ2.

If you really wanna confirm that, you could always test it out.

I mean it's not like anyone would normally pass the point of screen-lock, stop before the signpost area, run backwards, then forward for the signpost to disappear.. on purpose. So you could try and figure out if this is a recurring bug.

[muteKi]

redhotsonic, on 09 April 2012 - 04:38 PM, said:

MainMemory, on 09 April 2012 - 04:30 PM, said:

There's only one Big Ring, next to the signpost.

Therefor, I am guessing I am right. You got close to the signpost so it loaded, ran away so it deleted itself, and then it never loads back up again. Whereas the big ring "probably" loads, then gets deleted when you run away, but does have the ability to reload.

You said it only happens to this level/act because the screen lock happens a lot earlier. This explains why in all other levels, because the screen lock happens a lot later, when you try to run away and you meet the screen lock, the distance to the signpost isn't far enough, so it doesn't delete itself. And the signpost won't load in the first place until the screen lock comes into play.

Anyone correct me if I am wrong.



EDIT:
[image here snipped out for space]
I will say though, those first three points objects do seem quite far away from the signpost. But then again, the object's art doesn't load 'til the screen lock comes in. Maybe that's why it locks itself early?

Yeah, as you suggest, I recall those first 3 points not actually having their art cues properly loaded at the point where you can first encounter them. It seems like they did expect the level to end a lot earlier than they did. I'm not sure why this is inconsistent for this level -- I could hazard a guess they might have done this to try to prevent the end-of-act crouching glitch, but clearly that didn't make a difference in that regard.

[XCubed]

Nice find! I'm disappointed that the point bonuses have been re-purposed as airtime trick points. Sonic 2 had a complete absence, but Sonic S3&K added the clever "we're dropping the signpost from the SKY bitches!!!" along with bonus points and monitors full of fun. Whatever happened to the little things like that?

[Irixion]

The screen locks too far away, other levels have a smaller screen lock. Simple fix really :v

[SonicGenesis89]

I found this bug hilarious for some reason. Especially when you hear him die after going in the ring and nothing happens lol. It's sorta surprising that not to many people recall experiencing this glitch since it looks pretty easy to have occur.