Hi, I just started using Dolphin primarily for its debugging purposes, but I am finding it is quite difficult to find relevant memory locations in games. The debug mode has breakpoints but as far as I can tell these are only for instructions, not memory. Am I missing something or is there no way to find important memory addresses without stepping through the ASM? If not, then I would suggest adding this as a feature as it is pretty invaluable.
Similarly, to help facilitate finding important memory locations, a comparitive memory search feature would also be very useful. For example, I know a variable changes every frame, but I don't know its value. By doing a "not equal" search of the memory every frame for a few frames I could quickly find this variable. Other emulators with debugging have this, and it makes it much easier to find memory addresses for known variables.
Sorry that this post became more of a feature request, I'm mostly just asking if there is a better way to find the address of a variable with known behaviour (such as changing every frame) without having to step through the ASM. I tried to do it, but it just took way too long to advance even a single frame.
Similarly, to help facilitate finding important memory locations, a comparitive memory search feature would also be very useful. For example, I know a variable changes every frame, but I don't know its value. By doing a "not equal" search of the memory every frame for a few frames I could quickly find this variable. Other emulators with debugging have this, and it makes it much easier to find memory addresses for known variables.
Sorry that this post became more of a feature request, I'm mostly just asking if there is a better way to find the address of a variable with known behaviour (such as changing every frame) without having to step through the ASM. I tried to do it, but it just took way too long to advance even a single frame.