January 30, 201511 yr Hello all I just reinstalled fs2crew on my new pc, and now after take off, instead of just giving me the "cmd a" prompt after takeoff (400ft), it gives. L nav, vnav.. But then it actually deactivates it, because I armed it at the gate already. I'm not sure what I do different. Any tips/ trouble shooter? Vkr Victor roos Victor Roos
January 30, 201511 yr Author I have been looking at the noap.but, having it engaged on the ground, wouldn't change it would it? .. Victor Roos
January 31, 201511 yr Commercial Member LNAV and VNAV should not disengage at 400 feet if you pre-armed them. The 400 feet LNAV / VNAV calls are FMA calls by the FO only. Something else is happening. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
January 31, 201511 yr Author Hm. But, if they show up on the second screen, that aren't calls right?. That actually are commands for the fo? Because then, he deactivates the l&vnav Victor Roos
February 27, 201511 yr Hm. But, if they show up on the second screen, that aren't calls right?. That actually are commands for the fo? Because then, he deactivates the l&vnav I have the same here. Also wondering why. Greetings, Klaus Schmitzer Klaus Schmitzer i7-14700KF 5.6GHz Water Cooled /// ZOTAC RTX 4070 TI Super 16GB /// 32GB RAM DDR5 /// Win11 /// SSDs only DCS - XP12 - MSFS2020
February 28, 201511 yr Commercial Member Make sure you're not skipping the ruwnway entry procedure and takeoff flows. Arm LNAV/VNAV prior to running these flows. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
Create an account or sign in to comment