MZ2 Crash

Discussion in 'Discussion and Q&A Archive' started by ProjectFM, Oct 20, 2014.

Thread Status:
Not open for further replies.
  1. ProjectFM

    ProjectFM Optimistic and self-dependent Member

    Joined:
    Oct 4, 2014
    Messages:
    912
    Location:
    Orono, Maine
    In my hack I've changed the layout and included more lava waves (stopping points not added) and whenever I get to a certain x- coordinate near the beginning of the level it crashes. I think it may have something to do with the original lava wave stopping point but even after removing the stopping code it still crashes at the same point. Can somebody help me? Thanks in advanced.

    Note: I am using the Hivebrain 2005 disassembly.
     
    Last edited by a moderator: Oct 20, 2014
  2. Irixion

    Irixion Well-Known Member Member

    Joined:
    Aug 11, 2007
    Messages:
    670
    Location:
    Ontario, Canada
    Okay really, I have no clue what you even did. But in any case, it's probably a mucked up object that you've placed down. Delete the object file for the level and have SonED2 to recreate it, or replace the original MZ object file and start editing it from there.
     
  3. ProjectFM

    ProjectFM Optimistic and self-dependent Member

    Joined:
    Oct 4, 2014
    Messages:
    912
    Location:
    Orono, Maine
    Thanks! I couldn't find any object that seemed messed up in SonED2 but I deleted the objects around the crash area and now it works fine. I don't know why I didn't think of doing it before.
     
  4. Irixion

    Irixion Well-Known Member Member

    Joined:
    Aug 11, 2007
    Messages:
    670
    Location:
    Ontario, Canada
    Considering how many error handlers Sonic 1 has, I'm surprised it doesn't have an error handler for a wrong object subtype. In any case, make a lot of backups of your work so you don't have to start over should anything else like this happen.
     
  5. redhotsonic

    redhotsonic Also known as RHS Member

    Joined:
    Aug 10, 2007
    Messages:
    2,969
    Location:
    England
    It's probably an Object wrong subtype. Making an object from say (for example) 4D 00 08 to 4D 01 08, can make the whole game crash (depending on the object). Similar to what Irixion has already said. That's all it probably was.
     
Thread Status:
Not open for further replies.