Correctly indentify some fields in CPlane#287
Open
gaussandhisgun wants to merge 1 commit intoDK22Pac:masterfrom
Open
Correctly indentify some fields in CPlane#287gaussandhisgun wants to merge 1 commit intoDK22Pac:masterfrom
gaussandhisgun wants to merge 1 commit intoDK22Pac:masterfrom
Conversation
Field mappings were obtained with experiments. Turns out these four fields are all floats that represent the plane's control values.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
So I was doing some shenanigans with planes, wanting to send a convincing pad state in SA:MP based on the plane status when its driven by in-game AI, and I noticed the relevant values are mapped as integers, and the CPlane class in general lacks descriptions for most of its fields. Hope this helps someone in future :D