A320 rocks back and forth on autopilot after latest update

Eric,

Today's flight also problem with reaching FL390, with a tailwind. No doubt there's still a bug with this plane regarding that. I can get it to FL350 while maintaining managed speed, and sometimes a bit higher, but until they get this bug fixed it's best to keep the cruise altitude set in the low FL300's. As I mentioned earlier in this thread, the manual setting of the ILS freq is required and also the setting of the takeoff speeds and flap settings. Once the flap setting is entered, you can just click on each of the takeoff speed bug settings in PERF of the MCDU. The first click will bring up the speed and the second click to that will confirm and lock it in. Then your speed settings will show on the readout during takeoff. At least this is with the addon mod from Flybywire.

John

Thats the exact same problem I had. I couldn't get the aircraft higher than FL350 or 360. Any higher and it would nosedive. I actually still haven't flown another flight because it was so frustrating after the last update. I needed a break from fighting with the sim.

I also use selected altitude rather than managed altitude, as managed alt had been buggy. On approach I've been manually setting Approach phase in Perf of MCDU. This drops managed speed so that I can start extending flaps for landing. Sometimes it doesn't happen automatically, so it's good to have that done in advance of picking up the glideslope and localizer. I also turn on the ILS information display (LS button next to FD) so that I can see the localizer information to ensure that I have the freq set right prior to the LOC needle coming live. Turning off auto pilot a bit earlier today seemed to allow a smoother landing for me without a penalty of passenger screaming due to g-force from my Econ settings on SPAACARS. Of course this is all with the Flybywire addon enhancements to the default A320N.