Just tested and this doesn’t change anything, the bug still occurs.
Can you provide video examples to see how the bug is not occuring when you land please ?
I never fly with default ATC, and I still get this problem.
I’ve tried this, and it doesn’t make any difference. I think it seem like it makes a difference, because the problem doesn’t occur on every landing, but I’m pretty convinced it’s just coincidence.
This youtube video shows the issue occurring. He clearly didn’t put left aileron.
I did 10 touch-and-go’s today and even though I’m not 100% certain, it seems to occur only when I touch the rudder at 20-30ft. Even the slightest input seems to cause the roll.
1 Like
Hi,
I’m just wondering if this is normal or not, but before touchdown with the A320neo (787-10 same issue), the joystick at the last ‘50’ callout is getting really sensitive which makes is hard to gently pull back the stick to make a smooth landing, which causes you to bounce over the runway like a balloon.
Is this normal? Is this a bug?
1 Like
People told me this could be something like driving a car: once driving your car with 100mph, the steering is less sensitive as driving a car with 10mps. Never had this issue with X-Plane or FSX this much tbh.
There is already a big thread on this.
1 Like
This is about the flare to left issue (got this too, not that much), my issue is mainly about the pitch.
If you read down that thread, it is talking about general stibility (pitch and roll) immediately prior to landing. It is the combination of 5 related threads about over sensitivity, e.g.
https://forums.flightsimulator.com/t/a320-banking-left-and-difficult-to-flare-at-landing/302268/10
https://forums.flightsimulator.com/t/a320-banks-left-right-when-50ft-above-the-runway/285754/43
https://forums.flightsimulator.com/t/a320-bank-left-and-right-while-landing/302685
https://forums.flightsimulator.com/t/a320-roll-on-landing-issue/292893
etc
2 Likes
I’ve heard that when a plane slows down, movement will be less as there is less air moving around the control surfaces. At least for normal aircraft, not fighter jets who turn better when they go slower, i can fly almost at stall speeds in DCS and turn on a dime.
As for banking, I’ve had it bank to the left and right, i think it is related to the wind direction and speed. Almost had a wingtip strike today in the A320 because of 25 kts crosswind over Sweden. Did 2 go arounds but eventually decided to go to another airport - no banking there.
I’ve been talking about this for quite a while. its a problem with the state logic on FBW aircraft. Open up a project in the DEV mode, goto aircraft editor then debug aircraft AP.
you will see that when you get below 100ft or 50ft that the system switches from roll and pitch FBW mode to direct joystick mode. However, it doesn’t even go fully into direct joystick mode, you are fighting the FBW system.
When you are taking off you will see that while on the ground you are in direct Joystick Mode 1:1. Once you leave the ground and some level above that it switches to FBW mode.
I don’t care what knobs you turn in the config files this is the problem.
i’ve been testing AP PID controls for 2 weeks and their is definitely functional issues with all FBW aircraft. I cant suggest that all aircraft exhibit these problems as i only attempt to fly the A320.
Test it for yourself.
2 Likes
In hind sight i see this: you approach 50ft, all roll control authority is basically lost as it switches modes. Im guessing that we are fighting the Integral part of the roll control PID. The reason why i say this is if you are monitoring the AP in Dev mode, Turn off the autopilot and all the values hold. They are never zero’d out.
For the folks who have never seen this, at the last 100 feet put in a bit of roll and as you approach 50 feet, try to straighten it out. You won’t be able to for some period of time. That’s why i think its the Integral Portion of the FBW.
You will command full ailerons to level it out and it will just sit there doing almost nothing for a time period.
Several weeks into the AP tuning and it is showing there are definite issues.
Im not gonna pee into Asobo’s cornflakes as they have a great sim here, There is just issues that cant be tuned out.
5 Likes
I just verified. The Roll Problem doesn’t exist if ELAC1 is turned off. It is a FBW problem.
It also is really hard to fly with that off as it is waaaaaay sensitive in pitch
‘Always has been’
yep. just a verification
So just to understand that better, if you turn off ELAC1, you are expanding the behaviour of the final 50ft to the entire flight regardless of altitude?
If the mods could merge these bugs (and the votes) that would be higher priority than many others. I am still astonished people care about the Any key that much, while there are issues like this.
1 Like
When i turn off ELAC1, it reverts to direct joystick mode, with very sensitive pitch responce. No output from the Pitch controllers. You also loose auto trim.
1 Like
as i had mentioned ive been working on tuning for several weeks. I have 25 deg roll working, fairly good vertical altitude level changes attempting to maintain speed. Definite Heading, ILS loops tuned fairly good. The vertical portion of the FBW has some real issues. Tuning the level change stuff was a gain here then suffer there problem. The state logic as well as how all those PID’s work together has issues.
For a level change you shouldn’t have to suffer endless tweaking for it to function properly. You should only have to tune each of those PID’s for proper response to minimize control errors.
I think it would be easier to write a FBW than try to explain the issues.
Im a controls engineer by trade. Id love to talk with these guys. There are allot of fundamental problems just with FBW.
I’ve spent more time trying to make the A320 fly better than i have actually done flights. Seems like FSX all over again.
FlyByWire has this issue on their list since 18 days.
Must be an issue in the vanilla game…
Hope it will be fixed in the new FS2020 update 
1 Like
I think he was actually talking about the fly-by-wire system of the FS2020 A320.