And that's another thing.when creating the memory card exploit, he was able to see his stack traces when a failure occurred and I don't think this is possible with Dolphin.
#Memory card for dolphin emulator download mod#
Oh, and Magus, if you haven't already seen, you NEED to check out wParam's SSBM Notes about his crazy mod and how he created the memory card exploit. So maybe I'M just the dummy.Īlso, this guy apparently does USB hacking with Dios Mios. And I know they are being read because I change them and things move in-game.īut I'm also not a computer science guy, so I don't know the technicalities behind the limitations of breakpoints, etc. I've also experienced memory read breakpoints not working for certain things, generally, in higher memory. And then following a gazillion branch links inbetween which just gets to be incredibly tedious. With Dolphin, the only way I know of ever being able to find this out is to find a function that the start of is executed and that the end of is not, due to the game crashing before it gets back. Turns out, trying to play the stage produces an assert for no background music and the game would then then branch to an infinite loop. I know that USB Gecko is better with this because I was reading wParam's Crazy Mod notes where he was figuring out why the "Dummy" stage (Stage ID: 0x0000) would crash the game. I just get a message saying the Dolphin has crashed and then the program closes completely. The biggest problem I experience with Dolphin is that if the game crashes, it has no way of telling me what line of code failed. I've never used a USB Gecko, but I really want to try one. Did you add the "/d" to the filepath to make it the Debug version? Click to expand.I do not believe you need visual studio to run that version of Dolphin.
0 kommentar(er)
