don't click here

Secondary Collision Data

Discussion in 'Engineering & Reverse Engineering' started by Rika Chou, Jun 3, 2004.

Thread Status:
Not open for further replies.
  1. Jun 3, 2004 #1
    Rika Chou

    Rika Chou

    Tech Member
    5,276
    169
    43
    Is there a way to add secondary collision data to a level that only contains primary collision data? MTZ for example?
     
  2. Jun 4, 2004 #2
    LOst

    LOst

    Tech Member
    4,891
    8
    18
    Talk to Ultima. I believe he programmed it to work on every level that you like to have secondary collision data
     
  3. Jun 4, 2004 #3
    Rika Chou

    Rika Chou

    Tech Member
    5,276
    169
    43
    No, Ultima prgrammed it so every level can have it's own collision index. I need to have collision for the lower plain.
     
  4. Jun 4, 2004 #4
    Hivebrain

    Hivebrain

    Administrator
    3,049
    163
    43
    53.4N, 1.5W
    Github
    You just need to change a pointer.
     
  5. Jun 4, 2004 #5
    Sonic Hachelle-Bee

    Sonic Hachelle-Bee

    Taking a Sand Shower Tech Member
    812
    203
    43
    Lyon, France
    Sonic 2 Long Version
    I think you know this offset index at $49E8.
    There is already 2 adresses for each level (8 bytes), one for primary collision data, and the second for the secondary collision data.
    You may have to change a pointer in this index and add your data at the adress this pointer refers to. I think that's easy as that. :lol:

    EDIT: A little mistake. At $49E8, that's only the primary collision data pointers.
    Secondary collision data pointers come after at $4A2C.
    EHZ primary: 00 04 4E 50
    ...
    SCZ primary: 00 04 58 C0
    EHZ secondary: 00 04 4F 40
    ...
     
  6. Jun 5, 2004 #6
    Rika Chou

    Rika Chou

    Tech Member
    5,276
    169
    43
    Thanks, that helps a lot.
     
Thread Status:
Not open for further replies.