-
Notifications
You must be signed in to change notification settings - Fork 11
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
Wrong value at the address #6
Comments
There is nothing wrong with this code. Did you make sure that the value in that process memory was not changed? |
The value (like 5.xxxe-115) PyMemoryEditor given is quite small compare to the value (0.30...) given by Pymem. It's clearly a wrong value. |
Ok, I got it. But, I would like to know if that process is totally under your control and you did make sure that the process is not changing the value during the execution of the PyMemoryEditor method. |
The process is changing the value, but in a small range. The value is one axis of the camera position. I can watch the value using Cheat Engine, so I can comfirm it didn't change that much. |
I have the same issue but with scanning for float values. And I'm sure that many values from the scan don't change the value after scanning for 100%. I'm scanning for 196.1... and all results are like 3.6... Maybe the scan results are wrong because of the wrong float read issue. |
pymem read the right value, while PyMemoryEditor get a wrong value.
Is any thing wrong with this code?
The text was updated successfully, but these errors were encountered: