But then, you’ll be flying on your own…
It’s lonely, but at least I don’t crash
The current workaround is to engage or reengage autopilot when you are roughly on course with the GPS route. Currently if you turn on nav mode and you are not close to the GPS track it will oscillate badly as it tries and fails to follow the track. But if you turn it on while you have flown it to be on track it seems to work just fine and act normal.
Update: my bug report has been logged by the team and is being reported as ‘Solved’.
Assuming we don’t find a full workaround for this, then I’m hoping it’ll be in the next patch.
Edit: I haven’t had a reply from FlyByWire yet.
Still having no issues here after resetting to defaults although I’ve never restarted a flight or used the big tubes. I always go back to main menu and start over from there if something goes wrong in flight.
There’s been some official presence in the original thread in the Bugs forum:
This was a couple of hours before my bug was logged as solved, so I have no idea if they still need information.
Just completed a flight on the A320 with new flybywire update.
AI traffic and ground traffic at 100 and no issues with anything at all.
@FolkishDesert39 Yeah I didn’t have any problems with the new A320 either. I’m guessing something in all the flight models has been changed, they did do a ton of avionics tweaks in the patch.
If we knew what had been changed, we could fix it ourselves.
Turned off live traffic and my sim is smooth as butter now. Also no issues in a/p.
They do. Solved just means that team now know about it.
@CapnAlex78 Ohh ok, thanks.
Disabling live traffic and multiplayer allows me to start from a gate. Yay. So I tried flying somewhere this morning and the sim froze on me. First time that’s happened. 
I believe I’ve found the answer to this problem. Please read:
Do they still use custom liveries if you set it to use the generic AI?
@Neo4316 I have no idea, I don’t have them installed at the moment.
@Neo4316 yes generic AI should still use custom liveries or it does for me anyway.
Thank’s I might do that instead.
So if the issue happen when flying in large group in multiplayer, turning on generic multiplayer aircraft should fix the issue too
I made a flight this morning in the C172 (G1000) with the AI and multiuser traffic disabled. Today the AP worked as I expected it to, including the FLC mode that’s been hounding me. (Yesterday, FLC caused overpitching until stalling.)
Several differences in operation between before and after:
- System has been rebooted.
- Instead of keyboard shortcuts to set FLC mode and speed, I used mouse clicks in the cockpit.
- I waited until airborne to enable FLC mode. Before, I was setting FLC mode and setting the speed to Vx on the ground to get ready for the climb to altitude. This worked for me before the last update but became problematic afterward.
FYI I have a Radeon RX 580 with 4096 MB of memory.
@UnitedSFReader, I was having a similar problem this past weekend with the C172 and G1000… I started a 300NM trip with no problems, but about 2/3 the way through I lost total control of the pitch in the AutoPilot. I could use and maintain headings, but every time I kicked in the AP, the aircraft would pitch up wildly and go into a stall. I ended up flying manually the rest of the trip.
A question though if you noticed at all… while I was having these problems, as I hovered the cursor over either the NoseUp or NoseDn buttons I noticed the values in the popout flags were rapidly changing. I wasn’t actually selecting either button, just hovering over them, and I could see these values changing as though they had been clicked and stuck on or something.
Did you notice that at all?
Thanx in advance,
Jim-Sim