Noobs guide to model swapping and glitch fixing :Update 7-28: Re-write for BB.67

[hughie]

Did you add bones to it with the bone adder?

.......
I am a retard.

[NecroMasterX]

I still don't see how it affects it.

Edit:
I changed it on the model with no added bones and it worked:

[Snoopy]

well, it's something with the bone adder program. once you use it on a model, anything you try to change hex wise won't work.  you need to make the hex changes before adding bones.

[NecroMasterX]

Hey, I change the transN and added bones, and my model swap was very glitchy ingame.

[♤♡◇♧]

Hey, I change the transN and added bones, and my model swap was very glitchy ingame.

Did you change the TransN bone before or after adding bones?
After the issue is obvious.
Before however then, could be a problem with the bone itself (how it is connected to the model).

[Snoopy]

i haven't had much sucess at moving the TransN as well.  i think it may require more editing than just the index, but i'm still not entirely sure what.

[Velen]

This forum needs a Polygon Swapping tutorial so badly.

Nice tutorial though.

[JDub]

Ok, I found the MDL0Offset and converted it to hex. But whenever I search for it, it can't find it. What am I doing wrong?

[Snoopy]

the MDL0 offset isn't part of the hex code, the offsets are shown on the side.

[JDub]

the MDL0 offset isn't part of the hex code, the offsets are shown on the side.

*facepalm* How did I miss that?

Edit: Ok it makes a random jump in between the offsets.

[Snoopy]

that's fine, it took me a little bit to realize that at first as well.  and what do you mean by random jumps in the offsets? 

[JDub]

For instance I'm trying to find AF8 but when I look for it, it goes from AF0 to B09.

[Snoopy]

the side offset numbers take you close to where you need to go, but for your example, you would go to AF0 and then go over 8 bytes, and there's AF8.  if the hex editor displayed the bytes exactly, then there would only be one byte per row.  the offset numbers on the side are the byte numbers for the first byte of the row, but then you just need to count into the row to get to where you need, if it's not the first on the row.

[JDub]

Mkay, the model swap is completely invisible. For reference it was invisible before the offsets were changed.

[Snoopy]

so which model are you trying to place over who?  and you can send me the file and i'll fix it, if you want.  i'm assuming you're trying to hex the BodyM bone to be different so the model will show up without the need of having a smash ball.  the easiest way to get rid of it is to hex the BodyM index to be the same as the TransN, simply because the TransN is always shown.  like i said, i can either fix it up for you, or i can post a picture to help explain it better, i'm usually not overly good at explaining things.