[Techokami]

Had to uninstall TortoiseSVN and TortoiseGit. This sounds like a bad bug!

[KingofHarts]

I've got a question... Understanding that Stealth answers primarily on his own forum, I think it is one that anyone else can also field. It is regarding Special Stage editing. In particular, the starting position. I'll use Special Stage #1 in this instance. Looking into the binary for Special Stage 1, here are the starting position bytes:

03D0 02E0

Now this comes out to 976,736... which, obviously, IS the starting position in RAM when playing the special stage. Loading in the editor gives me the following starting position:


00F0 0030

This results in 240,48... I imagine the reason for this is so that Sonic's starting position can be placed in the right position in the layout when viewing it in an editor.

1, how exactly does SonEd2 find this position when it is reading the first, real value, from the binary?
2. Just to point out, the bug with saving the position of the Special Stage... it will give some odd value that puts Sonic in some wacked out glitchy area.

The first item is far more important to me so if someone knows this I'd greatly appreciate the info.

[FraGag]

The position displayed by SonED2 (v11.05.19) is (X - $2E0, Y - $2B0).

When it saves, it appears both coordinates are $300 less than what they should be. For example, just saving SS1 without any editing replaces 03D0 02E0 with 00D0 FFE0 ($03D0 - $0300 = $00D0, $02E0 - $0300 = $FFE0).

And the program just crashes when loading a project if the coordinates end up out of the stage.