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
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.
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.
The text was updated successfully, but these errors were encountered: