You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The way Dolphin Memory Engine looks for the memory address of the emulated game in Dolphin is, at least for gamecube games, essentially by checking if a certain memory page is flagged as MEM_MAPPED and has a fixed size of 0x2000000.
This, however, occasionally results in the program finding a wrong memory region if any other memory page has the same features and has been allocated at a lower address.
This issue is easily solvable by checking for the gamecube magic number (0xC2339F3D) at offset 0x1C in the emulated memory.
The text was updated successfully, but these errors were encountered:
I think in a similar issue, I was having trouble hooking the latest version of Dolphin Memory Engine with the latest version of Dolphin (5.0-21543). It would just say no emulation was running but the actual problem was I had a different memory override setting set which didn't match the memory engine's memory region. The error message could be a bit more helpful as that would explain why it couldn't hook to the running emulator.
The way Dolphin Memory Engine looks for the memory address of the emulated game in Dolphin is, at least for gamecube games, essentially by checking if a certain memory page is flagged as MEM_MAPPED and has a fixed size of 0x2000000.
This, however, occasionally results in the program finding a wrong memory region if any other memory page has the same features and has been allocated at a lower address.
This issue is easily solvable by checking for the gamecube magic number (0xC2339F3D) at offset 0x1C in the emulated memory.
The text was updated successfully, but these errors were encountered: