a version that we regular users can’t have, right?
Thank you again
You can… the installer is available for download by everyone. you just need to choose between the stable version or the development version. The choice is yours.
Great, from which link or where can I download it?
Hi
or straight here: https://github.com/Externoak/A32NX-installer/releases/latest/download/A32NX_Downloader.zip
If you have the stable version… Delete it first from your community folder, then use the installer to download and install the development version.
1 Like
ohh thanks a lot, I only downloaded the official one. very kind, thanks again
Unfortunately it hasn’t. It just doesn’t always happen. I had it in both my last two flights. This thing is driving me nuts.
Indeed, a320 landing are retarded…
Are you using the fbw dev version? My landings have been, for lack of a better word, buttery smooth since the update. I was having the pitch and roll problem every time before.
If you have your trim set to an axis on your controller make sure that it is neutral before switching of ap. This causes major problems to the pitch.
Btw I do all my landings on manual except in very low visibility conditions.
1 Like
Yes I am on the dev version last updated yesterday, and still have the same issue if I try any aileron input on final. I am flying the entire final descent manually. Thanks for the suggestions though. Not sure if you have tried any wing low crosswind landings, that’s where it always happens.
I don’t even set any of my trim to any controls at all. I let my autopilot manages my trim. And my joystick axis are bound to the primary flight controls only.
I do low and strong crosswind landings all the time. And I haven’t had the wing roll bug for a very long time. At least after I set my deadzone to 10%. I set it this way because it’s almost impossible for me to pull back the sidestick with complete accuracy to the 180 degrees direction. Since moving it slightly to the left/right by one degree would have the aircraft register it as a valid input. It’s basically my arm has a tendency to pull towards my body instead of a straight backwards. So if I’m using a left-handed sidestick, I would roll to the right. If I’m using a right-handed sidestick, I would roll to the left. And since most people are using right handed stick. It’s common for people to roll to the left.
If you’re using analog stick on an Xbox controller, it’s even more prone to this because of the small travel distance in the stick. There’s almost no way everyone can pull back the stick perfectly at 180 degree direction every single time. Same goes for two-handed yoke. How can you be sure that you’re not twitching the yoke by 1 degree each side when you land. That’s why setting a larger deadzone eliminate this issue.
Shoould we have a poll asking how many people experiencing this use vanilla A320, the A320nx stable or A320nx unstable version? I have never has this issue until yesterday. WHat I did yesteday I installed the experimental version of the A320 mod as the stable one is not compatibile with the latest update. All the sudden I had the roll left on flare which never happened to me before.
Still not fixed?? I have this issue and is not just to the left (I think)… I stopped flying on FS and did not renew my game pass yet. I was using just for FS and probably only gonna renew and fly again when they fix this.
2 Likes
No issues with me yesterday.
Doesn’t happen to me anymore. Because of torque, aircraft will tend to easily go to the left. I think the issue was just calibration. I use an x box controller and added less sensitive movement for left and right movements with deadzone s.
Btw you can buy x box thumbstivk extenders to get more movement radius.
I’ve never seen the A320 completely loosing the GS during an ILS approach like in your video.
Do you know why this happened?
I dunno… I assumed it’s the heavy crosswind? I didn’t even realise it until you mentioned it and I rewatched that video. I was too busy being surprised by that one AI traffic pilot who swoops in from below before being told off by ATC to Go around because they need to wait their turn. Hahaha…
I might try the same approach again on clear and calm winds to see if I can still replicate the issue.
Wind shouldn’t cause a GS deviation. The interesting thing is that the A320 never tried to regain the GS.
The funny thing is that the AI traffic was apparently exactly on GS.
That AI event was a nice confirmation why I’ve never enabled ATC and AI traffic!
You do see the GS increase from 96kts to about 102kts around 500ft-400ft descent range, so there was a slight reduction in headwind. As you mentioned though that’s nothing the AP shouldn’t be able to compensate for, I’ll run some tests playing with the winds manually and see if I can repeat this.
Im talking about the glideslope, not ground speed.
I’m aware, the increase in GS combined with the lack of response from the AP is what caused it to overshoot the G/S on the last 400 ft, the question now becomes is this something we can repeat and submit as a bug.
Edit: Need to test a few more configurations, then the unmodded version, but so far this is looking repeatable.
2 Likes