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
Possible cheat code pointer issue (reported by email) #10557
Comments
That example cheat is copying 0 from address 0 with offset 0 to offset 0, aka doing nothing, made a better "test cheat" for some of those pointer types that are more popular in #10072 (comment) which can be used in any game, then looking at 08801040 in disassembly to see if results match the expected ones. Also I made sure they work before merging that pr and there were no further changes, so unsurprisingly they still work and produce expected results. So this could simply be about someone thinking cheat code doesn't work based on some existing cheat made for PSP, while in reality pointer could be stored at different location or offsets could differ aka memory allocation issue. But that's just my interpretation, I have no practical use for pointer code types as it's easier for me to just inject a script into the game and let it do all the work, which leaves my cheats safer and not affected by memory allocation issues. |
In theory it's a bug if we're not accurate on memory allocation. I think it will be hard to get some timing right, though... The biggest things I know of are Psmf/Mp3/etc. (see #9601) and I think sceIo*Async calls (which allocate a thread stack I think.) I don't know what else makes it off... -[Unknown] |
Issue |
This will now be tracked in #11167 closing. |
@LunaMoo you might have some idea?
Got this message:
Does this make sense?
The text was updated successfully, but these errors were encountered: