August 21, 20205 yr Not sure if this is how it supposed to work, a bug or Pilot error . I have set the required altitude, taken off and have armed Nav on the AP but not engaged AP. I trim to the vy speed and manually fly to intercept the GPS. Whilst still climbing I engage AP to capture Nav mode but all hell breaks loose and the aircraft nosedives, trimming all the way down. On the flip side if I don’t engage AP until I reach altitude then everything is OK. it may be that’s it’s all or nothing on the AP front but that’s not what I’m used to. Could someone enlighten me? FYI this is in Cessna 172 but it’s the same across the board.
August 21, 20205 yr Commercial Member I would recommend always engaging the AP first, then NAV mode. That works for me and is standard practice I was taught. Since that's the way I've always done it I haven't noticed the behavior you describe, which sounds like a bug. Charles "Dutch" Owen - Developer at Military Visualizations - currently working on the C310R and SR-71A project for MSFS.
August 21, 20205 yr we've discussed this, your're AP is conflicting with other settings in devices. Ryzen 5 5600X - Noctua U12A, 32Gb Vengence, Sapphire Pulse 5700xt, WD Black SN750 NVMe SSD
August 22, 20205 yr I am having a problem with the NAV key command. When ever I press it am getting LVL instead of GPS.
Archived
This topic is now archived and is closed to further replies.