- Messages
- 497
- Country
At last something we can BOTH agree on.This system seems horribly messed up and inaccurate.
I really don't understand a separate baro for the AP, let alone the transponder. The transponder typically gets input from either an encoding altimeter (the value provided is the pressure altitude) or from a "static altimeter" that is always at 29.92. There is no need for the transponder to have a baro setting of any type whatsoever. That would not be realistic.
If course it would be "Realistic" - The Transponder has its own Baro, that is ADJUSTABLE, but NOT by the Pilot. It gets calibrated to a fixed 29.92 by the Aircraft mechanic .. but in reality , can DRIFT.
SO, yes, to simulate drift and miscalculation, the SIM's Transponder would have an adjustable Baro, but only adjustable by some sort of "maintenance procedure"
But you are missing the whole point of this thread.
For an AP, that has its own Baro, and the means to adjust that baro, as it is that baro that the AP should use for its Altitude function.
In MSFS, the KAP140AP has Baro is index 2
In MSFS, the KT76c Transponder has Baro index 3
In system,cfg, under {AUTOPILOT}, "altitude Indicator" is set to 2, because it is baro Index 2 that we want the kernel AP Altitude hold code to use.
BUT.. the kernel, after reading "altitude Indicator" = 2, "MUST" be incorrectly adding 1 to that, so it uses Baro 3 = The TRANSPONDER, which is wrong. !!
(the classic, software programming error, do you start counting from zero, or from 1 )
The only reason why it can "Appear" to work correctly, is because, if you are LAZY, and do not manually adjust the Baros as you would in real life, but instead, press B that will set ALL baros, and the AP using the Trasponder baro, now set by the B key, will appear to be working correctly.
This is not Theory, this is not a Guess, it can clearly be shown to be the case, and "IT IS SO WRONG" -- and needs to be fixed.