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

Hex editor improperly displays the values of addresses when a cheat size smaller than the data size is applied to one of the addresses #1026

NarryG opened this issue Oct 18, 2017 · 1 comment


None yet
3 participants
Copy link

commented Oct 18, 2017

If you apply a cheat that's smaller than the displayed data size of the memory domain, the hex editor will mis-report the values in memory.


If you swap to 1-byte mode, you'll see the actual values.



This comment has been minimized.

Copy link

commented Oct 19, 2017

This one is trickier to solve then the other one.

For reference, the problem lies in GenerateMemoryViewString, line 512 of HexEditor.cs

The code pulls in the displayed number of bytes even if a cheat only effects one byte. I'm not sure when I'll sort this out but that's the place to start if anyone is interested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.