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
It seems like V3.0 added address randomisation causing the pointer offsets to be random on each machine. Code for reading them already works IF the randomisation can be solved. E.g., offsets found are only valid for that session.
Waiting for V3.0 to stabilize then try to find another way to read song id.
The text was updated successfully, but these errors were encountered:
aliencaocao
changed the title
nimpy.AccessViolationDefect: Unexpected error encountered: Read failed [Address: 0x8000000000000070]
V3.0 beta client support
Nov 23, 2023
Currently, the offset for the current time and song array itself can be reliably found, but the song array uses a list of pointer offsets (4-7 of them) and each offset value changes for each session of the client. I haven't found a solution for this part yet.
Last tested on V3.0.6 build 202419
It seems like V3.0 added address randomisation causing the pointer offsets to be random on each machine. Code for reading them already works IF the randomisation can be solved. E.g., offsets found are only valid for that session.
Waiting for V3.0 to stabilize then try to find another way to read song id.
The text was updated successfully, but these errors were encountered: