I have a folder called "Hack" So the folder structure is like this: [Hack] [SonED2] [Disassembly] [SonED2 Project files]
I ran into an issue quite a while back that concerns the Sonic 3 and Knuckles disassembly where the save format that SonED2 uses for the layout files caused some unwanted problems. See here for more details: http://stealth.hapisan.com/Forum/viewtopic.php?f=2&t=61 I couldn't see much of a way round this myself (being as technically illiterate as I am) but after some discussion with MarkeyJester, I present to you: Sonic 3 and Knuckles: Layout Padder by MarkeyJester To use it, simply drag and drop a layout file from a Sonic 3 and Knuckles disassembly onto the program. This handy program will pad the header of Sonic 3 and Knuckles layout files after they have been saved in SonED2, allowing them to work properly in an assembled rom. Just remember that if you save a layout in SonED2 again, you then have to re-apply the layout padder. Enjoy; and a big thanks to MarkeyJester for this tool.
Hello people. First of all, I'm sorry for bumping this topic up. But, as this topic is pinned, and this topic has been bumped many times before, I guess there are no problems. I'm with a big issue: SonED2 closes inmediately after I try to open the file browser to open a file. I get no error messages, no nothing. I'm getting this problem after I had to format my PC, with Windows 7 (x64) as the OS. Is there any solution for this problem? Thanks.
Thanks Stealth for my problem earlier. I know it was a confusing time on IRC. Also he said that Retro doesn't have the most up to date version of SonEd 2?
Any way to change the collision tile colors for exporting chunks? Its hard to see collision tiles that are black on black backgrounds >__<
That's a great idea for level editors! Consider it stolen! :P BTW I hope MainMemory considers this as well... SonLVL could definitely benefit from this.
You could also simply change the background color (first color of the third palette line). I should probably allow exporting chunks with neither the high or low planes visible for collision purposes though.
I'm having the same issue. Screenshot of crashing. Running Windows 8.1 x64. This is kind of bad, since I need to do something Chaotix-related, and SonED2 is the only tool that can do it.
I seem to recall someone had the same problem once, caused by TortoiseSVN. Do you have any shell extensions installed?
I had this problem in the past, and couldn't find an answer for months until FraGag helped me look into it. It was indeed TortoiseSVN. We solved it by getting rid of C:\Program Files\TortoiseSVN\bin\crshhndl.dll (if you used the default installation path, of course — I renamed the file to crshhndl2 for safekeeping), after which everything worked perfectly.
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.
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.
