-
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
Pilot position updates - (num1) and (num2) fields #3
Comments
(num1) = pitch / bank / heading / onground value
Onground aircrafts have usually 0 degree pitch and bank angles, their (num1) value is mostly heading encoded, a small value, very stable until they start taxiing. On the contrary, airborne aircrafts have rarely perfect 0 degree pitch and banking angles, leading to big (num1) values. |
(num2) = difference between Above Ground Level altitude (AGL) and Above Mean Sea Level (AMSL) altitude, as reported by aircraft barometric altimeter Unit is feet, obviously. |
I do thank you and must be grateful for it. This problem has been troublesome for me for totally 5 years. |
Hello, |
Use the bit operate to get the specific bit in the pbh value. That means the pbh value should be discussed at the binary level.
|
What does
(num1)
and(num2)
represent? It's present in both IVAO and VATSIM variants, but isn't present in the original FSD spec.(num1)
is a number of up to 10 digits. It seems to begin with 4.(num2)
is an integer. There seems to be a wide range of values, anywhere between 1 and 3 digits, and can be positive or negative.The text was updated successfully, but these errors were encountered: