-
Notifications
You must be signed in to change notification settings - Fork 4
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
[BUG][TM2020] VehicleState::GetVis
can return the wrong CSceneVehicleVis
#13
Comments
after investigating a bit, |
Looks like Tested with the 2023-12-20 update. Do you want i open a pull request for 2 characters? 😅 |
Thanks! I'm taking a look now. |
Is this just going to be a recurring thing, where the offset changes every now and again? I can tell you that we had this exact issue with I haven't played in a while, so never noticed anything breaking, but I'm assuming the magic number just changed again and broke things. Maybe nadeo undid their change there and so we are back to the old offset? I have no idea. Either way, if there are issues with the vehicle state, at least we know where to look. |
Perhaps. It could also be that it's a buffer of vehicle ID's, as there are more than 1 in that range already, and we have to read the "first" in the buffer. At negative 0x20 for example there is often just 0. |
In TM2020, if you open the Debug Window in the "Player States", you will see that players can have the same
VehicleState
values.Note that the
VehicleState::GetAllVis
function works well (as you can see in the "All state" tab)The text was updated successfully, but these errors were encountered: