exactly, but I was hoping the solution could be simpler
Yes, I also noticed that, if we start the flight all lit up at the end of the runway … the AP is functioning normally
I have the same. A320 turn left on AP. Earlier was almost good
For me it doesn’t matter the flight level, second the USB is plugged back in its a race to the ground at a left bank.
The devs dropped the ball hard on this as it was working just fine in alpha and day one up until the Japan update.
1 Like
If you can disable the FLT/CTL switches on the default 320. Try switching them off ( white ) before engaging autopilot or even before take off.
If it behaves properly. Try using selected heading to make turns and see if using those FLT/CTL switches does anything different.
I use the modded version and had a problem with the FD being stuck way off target, and infinitely banking left with AP on.
I’ve tried two flights now with all the FLT/CTL switches turned off and it behaves normally.
Specifically, SEC3 seems to create oscillations during turns and with SEC3 off i’m not having issues.
Try this and see if it makes a difference with your own vanilla or modded aircraft.
1 Like
So I’ve heard about this as a solution, but I’ve always started my flights cold and dark at the gate. It feels much more realistic to me and I feel like by starting at the runway, I lose out on the pushback and taxi to the runway phase of flight. They really need to straighten this out soon. This is the first major bug I’ve experienced with the A320.
2 Likes
The same thing happens to me, this game does not improve, it gets worse with each update. These folks instead of stabilizing and making the game playable, they put out ridiculous scenario updates as if that’s what we simmers demand. We ask that an airplane be flyable in IFR, which at present, when you are going to start a flight, you don’t know how it will end and if you will.
To the aforementioned problem, I think that starting the flight at the head of the runway does not manifest the problem, likewise when the failure manifests not even the manual Heading works, which is laughable at the point where we are launching this ■■■■, bad called product.
That if I would like the Messrs. Of Asobo, the programmers to inform where they studied their professional careers, more than anything to prevent my children from going to those Universities.
13 Likes
So was this with the mod A320 or default? Like I keep saying, I don’t use any mods except for a livery pack for the default A320. But I’ll try if it’s for the default A320.
1 Like
I just flew the A320 and programed it and had zero issues. Flew from Queens NZQN to Christchurch NZCH and even used RNAV to get me to 100ft and clicked off and landed fine. This is a non modded a320 using the in game flight planner and setting up my FMS for CLB/CRZ/DES.
2 Likes
If you can unplug your peripherals and the autopilot starts working, then the issue has to be in the control setup, or the controller itself. I had this same issue earlier, and I deleted my keybinds and reassigned my controls. It was annoying, but it fixed my left death bank issue that everyone is describing.
Its been confirmed elsewhere on the forum that this update messed with the controls, so give it a shot and see. I’ve had 3 cold and dark started flights today and all worked perfectly. I hope it helps…
1 Like
The solution is also just not feasible for those of us who like flying on VATSIM or IVAO, as those networks basically require you to start cold and dark. The A320 used to be the only plane viable for on-network IFR flights, as it would work at least somewhat reliably. (What a shame, the B787-10 is such a beautiful plane)
Now, its basically impossible to fly on network IFR with airliners in this simulator.
I really really hope they fix this very very soon (not next month with the next update), but im not sure hoping is wise seen as their track record so far is abysmal.
9 Likes
Agree… I have to stop flying on VATSIM due to this update with unreliable A320.
2 Likes
So wait, if this worked for you, what do I need to do again? I use my pc keyboard, a wireless mouse, and my Logitech joystick if that helps.
i’ve had no issue with the default actually.
Seriously, even after yesterday’s update?
Yes. On my first flight after the update running a dev build of the 320x i had the “stuck in a bank, not following NAV or HDG” bug.
I tried more flights with it later playing around with the FLT/CTL switches and the aircraft behaved about normal. SEC3 seemed to cause oscillation in corners.
Then i tried the default a320, no mods. It worked fine. It was slow to turn but it seemed to behave normally.
I tried the latest dev build of the 320x, no other mods. And it got stuck in a bank and did not follow NAV or HDG both with FLT/CTL switches on or off regardless.
I then re-tried the slightly older dev build and had no bug, SEC3 still causing oscillations.
So i have honestly no idea, the first flight post update seemed to have been a fluke of some sort. It was in KLAX and the behaviour of the aircraft was similar to the latest build. And FLT/CTL switches don’t seem to have an impact on the late dev build when it bugs out. So it must be something else entirely. I have not tried other planes besides the 208 ( with Garmin mods ) in the Discovery tour that worked just fine.
I deleted all my keybindings, including axis bindings, to my joystick and throttle. Then I reassigned all of my bindings and primary flight controls. That corrected the issue of the A320 following the flight plan so I hope it works for you as well! I think the update duplicated one of my primary flight control surfaces.
If you have some slight roll oscillations in cruise I suggest tuning down the autopilot PID. Someone had a fix here on the forums which also worked for me.
Ok so I’m having the same issue but it does a continuous bank to the RIGHT. I just started my first flight on VATSIM after updating and had to cancel my IFR after takeoff. How embarrassing.
3 Likes
I’m currently trying this method. Starting cold and dark at the gate, but I just deleted and re-assigned my key bindings on my joystick. I’ll let you know if I have any luck.