Title screen error!

Discussion in 'Discussion and Q&A Archive' started by liamsonichacker, Jul 7, 2010.

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

    liamsonichacker Mad Level Skillz ;) Member

    Joined:
    May 29, 2009
    Messages:
    50
    Location:
    Leicester, UK
    Can some body help me please


    I changed the starting pos in ghz1 and this happend:


    [​IMG]


    Please help me, thanks in advance.


    if this helps, here are the choords


    [​IMG]


    :)
     
    Last edited by a moderator: Jul 7, 2010
  2. DanielHall

    DanielHall Well-Known Member Member

    Joined:
    Jan 18, 2010
    Messages:
    860
    Location:
    North Wales
    I've had that error before, but it was through changing the number of something, just change it back and you'll be fine
     
  3. Selbi

    Selbi The Euphonic Mess Member

    Joined:
    Jul 20, 2008
    Messages:
    2,429
    Location:
    Northern Germany
    May I ask for the new location you've set?
     
  4. DanielHall

    DanielHall Well-Known Member Member

    Joined:
    Jan 18, 2010
    Messages:
    860
    Location:
    North Wales
    Who? me?
     
  5. theocas

    theocas #! Member

    Joined:
    Apr 10, 2010
    Messages:
    375
    I also had this issue when a bug in code I wrote set the cammera's x and y location to 0, the title screen scrolled around like crap. I fixed it by just getting rid of the code. As far as I know, doesn't the title screen load it's background data from GHZ1? I guess it also loads the start location and it then does the scrolling.

    No, iamsonichacker should post it.
     
    Last edited by a moderator: Jul 7, 2010
  6. liamsonichacker

    liamsonichacker Mad Level Skillz ;) Member

    Joined:
    May 29, 2009
    Messages:
    50
    Location:
    Leicester, UK
    011302FC


    hope it helps you to help me :)
     
  7. clarisonic1

    clarisonic1 Well-Known Member Member

    Joined:
    Jul 6, 2010
    Messages:
    106
    yay I get a point, because it's because of sonic's starting position in GHZ1. He has to be in the same position as he is in the original sonic 1, which is why I had him on a platform at the beginning of GHZ1 in my hack, because when I had him on the top of the ramp, it had the same error as yours. Change the starting position and you'll be okay.
     
  8. theocas

    theocas #! Member

    Joined:
    Apr 10, 2010
    Messages:
    375
    Maybe you can fix all this by adding a check to the level loading routine and then load the GHZ 1 Start Location from an array in the code instead from the file if it's GHZ1. I don't really know much about fixing this, since I never really had to do much.
     
  9. clarisonic1

    clarisonic1 Well-Known Member Member

    Joined:
    Jul 6, 2010
    Messages:
    106
    I haven't done ANYTHING in ASM yet. I was just told it was the start location, but I figured there'd be another way to fix it, I just didn't know what.
     
  10. Hanoch

    Hanoch Well-Known Member Member

    Joined:
    Aug 3, 2008
    Messages:
    312
    Location:
    Israel
    EduardoKnuckles covered it in his how to enable the 4th act guide.


    Go to Resize_GHZ and add this at the beginning:




    cmpi.b #$4,($FFFFF600).w ; is mode title screen?


    bne.s Resize_GHZ_Continue ; if not, branch


    move.w #$300,($FFFFF726).w ; reset Y boundary


    Resize_GHZ_Continue:



    Problem Solved.
     
    Last edited by a moderator: Jul 8, 2010
  11. liamsonichacker

    liamsonichacker Mad Level Skillz ;) Member

    Joined:
    May 29, 2009
    Messages:
    50
    Location:
    Leicester, UK
    thank you but


    [​IMG]


    now I get that.
     
  12. Selbi

    Selbi The Euphonic Mess Member

    Joined:
    Jul 20, 2008
    Messages:
    2,429
    Location:
    Northern Germany
    Change that line:



    move.b #$300,($FFFFF726).w ; reset Y boundary


    To this:

    Code:
    move.w  #$300,($FFFFF726).w  ; reset Y boundary
    

    Probably a typo by Hanoch, you can't move any value above $FF when it's a byte, and therefore needs to be a word.
     
Thread Status:
Not open for further replies.