I’ve read about 17 fps rule, that it can create problems with autopilot (which is especially bad, considering how widely spread memory leak issue is). But recently, I’ve downloaded A320 FBW, stable 27+ fps(don’t want to play in FSX 2003 graphics, but at least with FPS), which is enough for stable work. And everything works fine, except for LNAV. For the test I’ve started from the runway(because cold startup is too complex for my ape brain, at least for now), turned on AP, and height and VNAV work fine, but not LNAV. Maybe I’m doing something wrong? And there is a bit more comolex to turn on AP(like on TBM, where you have to connect it on plane’s controller)? Or is it some plane’s problem, or wrong version? My version was stable release
For everything to work correctly, you have to program the MCDU fully - with all infos it needs. Did you do that?
I thought that it will be programmed automatically, if starting up from runway(it was like this in more earlier versions). Now it changed, I guess?
As I’ve said, I’m not talking about cold startup. In “runway” start up systems are already started on it’s own, and earlier, LNAV worked. If it was from the very beginning not working, as on 787XH - that would’ve been one thing. But earlier it worked fine. That’s the main reason why I’ve started this topic.
Did you put a full flight plan before you start your flight? And are you on Managed NAV mode?
I think saying LNAV doesn’t work is a bit ambigous. You might need to explain with a bit more detail of what actually happened. If writing them is a bit too difficult, a short video recording of the issues can go a long way for the rest of us to be able to see and analyse what the actual issue is.