#Super mario 64 ds rom hsckd how to

Repointed stuff might well be tricky if the build tools are designed to handle certain locations, certain sizes and such like or have other assumptions. Assets might be replaced in place, or someone might have repointed it to somewhere else in the ROM (expanded in size perhaps as well). *the N64 also saw a fairly popular use of texture replacement hacks that operate at emulator/shader level, both as 'HD' textures and more conventional hacks (translation can be done as it is still a picture on the screen).įor more traditional hacks that aim to work on hardware then in general you will have assets and code to consider.

#Super mario 64 ds rom hsckd how to

This opens some doors and closes others, as well as makes remaking certain things a lot easier (what might take a master assembly hacker some considerable time a 'I know how to press compile and took a high school class' types might well do over a weekend or even by dead reckoning in minutes. You could port things from the N64 to the DS version and run that on the 3ds, that would however involve running the DS version which some might object to and it is not a trivial task either compared to maybe porting a hack between regions on the N64.Īlso now we have seen ports thanks to the decompilation (and possibly leaked beta from the gigaleak but I think they avoided that for 3ds stuff I saw). That said N64 emulation on the 3ds is not so hot so probably not an issue. As many N64 hacks, even those that stuck to hardware*, might have exceeded what the original emulator (or alternatives) were tasked with doing then that might make basic emulation troubled. The Wii quite notably saw a limited emulator compared to what the max the N64 could handle.

Such things get tricky depending upon what is done. I did cover this in a bit more depth on a Wii thread the other month