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

Started by Snoopy, June 07, 2010, 01:31:42 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Quote from: snoopy on June 23, 2010, 04:22:46 AM
http://www.mediafire.com/?yjynfy0qxiy

Silver hexed to have a TransN of 1.  sorry it's just the .MDL0 file, my brawlbox is having problems saving things.  all you have to do is insert this model into the one you already have of Silver on Olimar, and it should work.  i can't test it, but if it doesn't work, tell me and i can try something else.
the shoe now disappears and some parts of the model also disappear in different animations ._.  Its even more glitchier then before ._____.
Quote from: Miacis on December 10, 2013, 04:48:45 PM
Never underestimate the power of the ass.


alright, i thought something like that might happen, give me a bit to mess around with it some more, i think i know why it didn't work.


How exactly do you find the bones in the Hex Editor?
I tried to find it by searching for it but nothing shows up.

NecroMaster, Pokemon Trainer has 47 bones.  is he not in the list?  i may need to change that.

Hax, the way you find the bone is like this:  first, in brawlbox, go to the bone you want to edit.  second, where it says MDL0 offset, that's where the bone is located in the MDL0 file, but brawlbox displays it as a decimal number, so you will have to convert it to hex.  third, once the number is converted, open the .MDL0 in the hex editor, and go to that offset, and there's the bone.  if you need a clarification (i can't explain things overly well) i can post pictures to help you.

and Pokechao, i haven't been able to get it to work, it just keeps glitching brawlbox or freezing the game.  sorry.

Oh, ok, thanks ;D
Also, do the huge hitboxes have anything to do with this?

uhh, i'm still not exactly sure about the weirdness of the hitboxes.  what i've noticed is sometimes when new animations are made that it fixes most of them, but i haven't been able to pinpoint this one yet.  my theory is that some bones just don't know what to do when a new model is placed over them, and that new animations and PSA should get rid of the problem, but that's only my theory. 

Ok, about the hexing, do you just change the bone index by just replacing the numbers?
Mine ends with 04, so can i just change it to 06?

Quote from: Hax on July 02, 2010, 01:30:51 PM
Ok, about the hexing, do you just change the bone index by just replacing the numbers?
Mine ends with 04, so can i just change it to 06?
Yes

I still have a problem, here, i have the model before the edits.
The Hex number of the offset is c18.

The 04 is the BoneIndex, so i did this.

But it still shows up as 4 in the boneindex, anything i did wrong?

^This happened to me before. Hexing the index never changed it.

Quote from: dingoberriz on July 02, 2010, 02:39:50 PM
^This happened to me before. Hexing the index never changed it.
Is there a different way to change it?

Hey, I hexed the bone index of the TransN to 2 on my model, and I put it on the SD card, and it still has the run glitch. Hexing it did nothing!!!!! Please help me.