Do you have any add-ons in your Community folder? If yes, please remove and retest before posting.
No addons.
Are you using Developer Mode or made changes in it?
No.
Brief description of the issue:
ALT hold autopilot mode ignores altimeter barometric setting: if I set 4000 ft with altimeter 29.92 the autopilot levels off at 4000 ft, if i set altimeter something different, the autopilot levels slightly higer or lower than 4000 ft, as if the baro was still 29.92. Never noticed such behaviour with different airplanes using g1000, such as c172.
Provide Screenshot(s)/video(s) of the issue encountered:
Not available (I play in VR and I don’t know how to take a screenshot)
Detail steps to reproduce the issue encountered:
Set the altimeter different than 29.92, then set an altitude and reach it by using autopilot vertical speed hold mode; you’ll see the autopilot level off at an altitude slightly different than the one set.
PC specs for those who want to assist (if not entered in your profile)
i76700K, 32GB RAM, RTX 2070, SSD, Oculus Rift S
Did you submit this to Zendesk? If so, what is your ticket #?
Not yet, I need confirmation from the community that this is a bug and not my mistake
Not sure I duplicated your situation exactly, but I went into the Garmin 172, set the baro to 29.92 and let it climb to 3000. No problem. Then changed the baro to 30.00 and the plane slowly corrected back to the original 30.00 I set in. No problem.
Left the baro at 30.00 and set climb to 4000. It started the climb just fine. Then when it hit 4000, I noticed something. The screens inside showed it was at 4000 with the baro showing 30.00, but the external view was showing about 3915 and the baro incorrectly still showing 29.92. It appears the external view doesn’t change the baro reading, and shows the altitude as what it would be if it really were 29.92 rather than the 30.00 that I set inside the plane.
If I changed the baro back to 29.92, the plane move to the correct altitude that it was set to (4000) and it showed correctly both internal/external views.
So it looks like the external view isn’t changing baro reading, and thus incorrectly shows the altitude in that view.
Regards
This seems to be a consistant error: in the BE58 as well the AP uses the altitude as it would be at altimeter setting 2992, and not at the current alitmeter setting.
This is an issue I have since day one in all planes (even the pmdg dc6). It doesn’t matter what your baro setting is, the plane will level of to where the altitude would be if baro was still 29.92.
Example: DC6, baro 29.92, activate altitude hold on 4000ft. Keeps 4000ft. Baro 30.00, activate altitude hold on 4000ft, plane decends to ± 3970ft.
1 Like