First, a huge thank you to everyone involved in the creation of Dolphin. Your hard work has made a lot of people very happy. Thank you!
Now, on topic: I would love to know if there's any way (either within Dolphin itself, or using an external program) to view the main memory of the emulated console. I've used Cheat Engine to do this with other emulators (PCSX2, Project64, et al.), in which the emulated console's main memory is stored as a single contiguous block at a static location within the emulator's memory. All I had to do was figure out the offset between the two and subtract it out.
Dolphin, however, seems to store the console's memory differently. I've tried using Cheat Engine with Dolphin to search for simple variables in several GameCube games (Paper Mario: TTYD, Tales of Symphonia, Super Smash Bros Melee), and every time, I end up with 0 remaining Addresses after just a few searches. The only thing I can figure is that Dolphin doesn't store the console's memory in a static location like the other emulators I've used, but rather, constantly moves it around to different locations.
I have used Dolphin's built-in Cheat Search function to track down some simple variables. It's a great addition and very useful, but it doesn't replace the ability to actually view memory. Viewing memory around a located variable can make the process of identifying other related variables much easier and faster compared to setting up a reductive search for each one.
Further, directly viewing memory is really the only reasonable way to find variables that aren't represented numerically in-game, such as the identifying values associated with Items and Equipment. Since you won't know what those values are beforehand, it's extremely difficult to find them through reductive searches. It's much easier and much faster to find them by locating a related numerical variable, then viewing memory around it and watching for what changes when you change Equipment.
Anyway, any insight on how Dolphin stores the console's memory and whether and how I might view it would be greatly appreciated! BTW, I'm using Dolphin r7501, 64-bit, for Windows.
Also, while we're near the subject, does anyone happen to know of a good disassembler program for GameCube (I'm thinking along the lines of ps2dis for PS2), or even just what assembly language GameCube uses?
Thanks in advance for any help!
Now, on topic: I would love to know if there's any way (either within Dolphin itself, or using an external program) to view the main memory of the emulated console. I've used Cheat Engine to do this with other emulators (PCSX2, Project64, et al.), in which the emulated console's main memory is stored as a single contiguous block at a static location within the emulator's memory. All I had to do was figure out the offset between the two and subtract it out.
Dolphin, however, seems to store the console's memory differently. I've tried using Cheat Engine with Dolphin to search for simple variables in several GameCube games (Paper Mario: TTYD, Tales of Symphonia, Super Smash Bros Melee), and every time, I end up with 0 remaining Addresses after just a few searches. The only thing I can figure is that Dolphin doesn't store the console's memory in a static location like the other emulators I've used, but rather, constantly moves it around to different locations.
I have used Dolphin's built-in Cheat Search function to track down some simple variables. It's a great addition and very useful, but it doesn't replace the ability to actually view memory. Viewing memory around a located variable can make the process of identifying other related variables much easier and faster compared to setting up a reductive search for each one.
Further, directly viewing memory is really the only reasonable way to find variables that aren't represented numerically in-game, such as the identifying values associated with Items and Equipment. Since you won't know what those values are beforehand, it's extremely difficult to find them through reductive searches. It's much easier and much faster to find them by locating a related numerical variable, then viewing memory around it and watching for what changes when you change Equipment.
Anyway, any insight on how Dolphin stores the console's memory and whether and how I might view it would be greatly appreciated! BTW, I'm using Dolphin r7501, 64-bit, for Windows.
Also, while we're near the subject, does anyone happen to know of a good disassembler program for GameCube (I'm thinking along the lines of ps2dis for PS2), or even just what assembly language GameCube uses?
Thanks in advance for any help!