Another update. I think the code handler is sort of fucked. I tried about 4 codes with the Mupen integrated version and only saw effect from 1. Feels like it's not writing fast enough, even though it should be. Fixed up a few other things though.
Changes:
-Added an option to the search results to make the memory editor jump to each result clicked.
-Fixed a bug in the memory editor. Goto was getting fucked up when byteswapping was on. I guess it helps to check which column is being edited before swapping bytes.
-Improved the NDS support a bit. It will now attempt to find the RAM portion of No$GBA if the pointer is no good. This is actually a lot quicker than I expected. The downside is it leaves the potential for offset issues between hardware and emulator addresses. Ever try to hack Mario 64 DS with HasteDS? It's 0x4000 off because HasteDS starts at the game's entrypoint in ram, which isn't always 02000000. The Entry Offset box will subtract an offset from the start address if needed. The easiest way to tell if a game is off is look up an address you already know in the memory editor.
RenegadeEx v1.02
http://viper.shadowflareindustries.c...x0r/rex102.rar
Mupen 0.5 (RenegadeEx Edition v1.02)
http://viper.shadowflareindustries.c...en05rex102.rar
It should be noted that Mupen64.exe can be found in the winproject folder.
Reply With Quote