You might have wondered about the reason why they originally made the graphics for Sonic's running legs separated from his body. Well, it looks like he was supposed to have different running animations when he's running much faster than normal (just like happens with Tails), and these animations show the same graphics only differently mapped. The lost animations just move Sonic's body away from his legs, making Sonic look like he's indeed trying to run faster. Just replace "FF3C3D3E3FF" in the Sonic 2 prototype ROM with "FF40414243FF" (animation 2) or "FF44454647FF" (animation 3) to see them in action.
Wow, and anyone would have thought the beta was sucked dry! Nice one IceKnight! What offset would I go to to enter that?
0x10D00 Or just search for the values ICEknight gave; it's the only instance of that particular string in the entire ROM. =P
Sort of like how he runs in Sonic CD. When he reaches a specific point in speed his sprite changes. Nice find, ICEknight
Wow! That's awesome! I think everyone thought the ROM was squeezed totally dry! Kudos on a new discovery!
Cool. A new find. Congratulations! However you didn't say who found this.... If it comes from a trusty source I believe this is true. Else it can be a hack or a hoax
Lost, Iceknight explains how to make this happen in the Sonic 2 b ROM. So obviously it's not a hack, or a hoax.
Heh, well the offset was found, but when I did a search for FF3C3D3E3FFFFFFFFFFFFFFFFFFF HexWorkshop turned up nothing. *Sigh* I guess its because I'm not a real big user of Hex editing software so I don't fully understand how to use it <_<
First you have to search in the BIN, not the SMD :P And second, you are 80% in risk at spelling the hex numbers wrong when searching, so try again and again.
When I tryed that, it said invalid format or some shit. I had to type it in myself. I'm using XVI32 and it doesn't like strings like that, it likes spaces, but it wants to put it's own spaces in, but not when you paste something. It's bitchy.
I used XVI32, too. Yes, it's bitchy, and when searching the .bin file, it couldn't find the specified string. <shrugs> I gave up. But yeah, Lost is right in saying this could simply be someone's hack. Any proof that this was in there to begin with?
Apparently, ICEknight found it while documenting the animations format for the Sonic games. I Copy-pasted his post from SCARZ, to save him the trouble: So, while the animation frames themselves are real, there seems to be no existing animation that actually uses them; hence why it is nessecary to replace an existing animation's frame list to view them ingame. In essence, it is a short hack that merely enables people to easily view the lost animation frames found in the ROM in a situation that they most likely would have been used in. As well as clearing up, finally, why the sprite was designed to have the legs as a seperate sprite.
I found it myself. :P Just make a savestate with Sonic waiting in his very first animation frame and change that animation to: Code (Text): 000102030405060708090A0B0C0D0E0F 101112131415161718191A1B1C1D1E1F 202122232425262728292A2B2C2D2E2F 303132333435363738393A3B3C3D3E3F 404142434445464748494A4B4C4D4E4F 505152535455565758595A5B5C5D5E5F 606162636465666768696A6B6C6D6E6F 707172737475767778797A7B7C7D7E7F 808182838485868788898A8B8C8D8E8F 909192939495969798999A9B9C9D9E9F A0A1A2A3A4A5A6FF You'll see all the animation frames, Sonic 3 Debug style. On second thought, I think it looks more like Sonic actually had three different running animations depending on his speed, with 4 frames each rather than just having a second one with 8 frames (even though it looks kinda cool). About the frame lists, I've noticed there's a leftover from a previous Sonic 2 build in the Floating animation (which is always 0E): Code (Text): 079496FF They forgot to change the frame numbers for the newest graphics set at that time. Not that they were actually going to be used anyway... EDIT: Of course it's a hack since I'm telling you to modify the ROM...