Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dolphin Memory Engine occasionally fails to look for the correct memory addresses #68

Open
Jujstme opened this issue Sep 12, 2023 · 3 comments
Labels

Comments

@Jujstme
Copy link

Jujstme commented Sep 12, 2023

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.

@dreamsyntax
Copy link
Collaborator

May be relevant to #47

@StackOverflow0x
Copy link

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.

@dreamsyntax
Copy link
Collaborator

dreamsyntax commented May 18, 2024

I've never run into this myself, but if I understand Jujustme's proposal it wouldnt be necessary to specify mem sizes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants