(06-01-2017, 12:25 AM)Gamecubed Wrote: My rom is the one on the world minus thread, and I used the Mico extender on it. (When I just open the vanilla rom the program gives me an error when extending)
What error does SM64 Editor provide when using a vanilla ROM? SM64 Editor will automatically invoke sm64extend if it detects a vanilla ROM, decompressing it in place.
(23-01-2017, 11:33 PM)Platinum Lucario Wrote: Also, I don't think this program has support for little-endian (.n64) or byteswapped (.v64) ROMs either. Some N64 ROMs that are freshly dumped have an appearance of every two bytes been swapped around. As such, even the game code and game title is in this format too. Like for instance, instead of "SUPER MARIO 64", it would say "USEP RAMIR O46" and instead of the game code saying "NSME", it says "N MS E".
sm64extend has support for byte-swapped (.v64) ROMs, but it looks like SM64 Editor is trying to do some detection before passing it along to sm64extend, so that's why it isn't working. You can avoid this limitation by manually running sm64extend on the .v64 ROM and then opening the output of that in SM64 Editor. I didn't have a little-endian (.n64) ROM on hand to test with, so support for that was omitted.
(23-01-2017, 11:33 PM)Platinum Lucario Wrote: Also, it would be nice if there was some feature that would allow you to save the ROM as either byte-swapped format big endian format or little endian format.
Most SM64 hacking tools operate on big-endian (.z64) ROMs. If you want a different format in the end, I recommend using a tool like ucon64
to convert to the desired format.
(23-01-2017, 11:33 PM)Platinum Lucario Wrote: Either way, I'm positive the Nintendo 64's native ROM
encryption processing format is Little Endian.
Actually, the N64's native byte order is big-endian.