January 6, 201610 yr WHY?!? Pressing NAV should only ARM it and engage the FD bars. Sigh. Am I incorrect in my logic here? | My Liveries | FAA ZMP | PPL ASEL | | Windows 11 | MSI Z690 Tomahawk | 12700K 4.7GHz | MSI RTX 4080 | 64GB 6000 MHz DDR5 | 500GB Samsung 860 Evo SSD | 2x 2TB Samsung 970 Evo M.2 | EVGA 850W Gold | Corsair 5000X | HP G2 (VR) / LG 27" 1440p |
January 7, 201610 yr please delete my post. Francisco Blas Windows 11 Pro | X-Plane 12 | ASUS Hero Z790 | Intel i9-13900K | G.SKILL 64GB DDR5 | ASUS STRIX 4090 | WD 4TB SN850X NVMe | ASUS Ryujin II AIO 360mm | Corsair AX1600i | Lian Li 011D EVO | DELL Alienware 38 G-SYNC
January 7, 201610 yr Yep, it's pretty annoying. Every recent Carenado release has that issue. It's an easy XML hack to fix it.
January 7, 201610 yr I discovered this as well. Really hoping a service pack comes soon and/or Bert does his magic with it.
January 7, 201610 yr Bert just got his copy, and NAV correctly arms VOR1 in FD mode on mine.. Is this only in FMS mode that you see this? Edit: Yes in FMS mode, the NAV button turns on the autopilot.. doubt that is correct.. Bert
January 11, 201610 yr Yes in FMS mode, the NAV button turns on the autopilot.. doubt that is correct.. Hi Bert, I had the same problem in the Hawker and sent them an email...Seems they didn't correct anything. Sorry to hear that. Regards, Perry
Create an account or sign in to comment