A320 NX doesn't follow the Approach

Discussion Hub Aircraft
1

Hi Guys,

at the Aproach the A320NX dosent folow no more the Route to the runway with loc and APP on and dosent follow also the route from the fmc to the runway unfortunaly. So i must handfly the Approach.

Do you know what that issue is?

regards

Legendsy

2 Likes
2

Feel free to post this in the Third party section.

Bugs & Issues subforum is for bugs with the base sim only.

1 Like
3

As @MortThe2nd correctly said, I have moved this thread to it’s more correct location on the forums.

@anon5812396 It may be useful if you could identify which ‘version’ of the A320NX mod you are using, stable or developer and which ILS/LOC airport you were experiencing this problem with.

4

firstly thanks for moving in the right category. The Approach was via the transition ROMT1H to the ils 24L-X APP at UUEE (MOSKOW-Scheremetjow Airport) the Departure was from ULLI at 14:10 ZULU or 2:10 PM ZULU.

In the Atachment you can find my Settings from the Thrustmaster T16000M Joystick

se new
se new1102×914 139 KB

I have also the Thrustmaster TWCS Throttel with the following settings:

ts new
ts new1116×916 143 KB

5

And what about trying the same approach with the default A320neo, to check whether this is related to the mod?

6

I’ve just tested it with the same Aproach and the standard A320 Neo. And i havent these Problems i had Loc and APP on and i used the same transition. I made a Autland with the standard A320 neo.

7

I talked just for few minutes to a dev or Admin from the A320NX Mod and my issue what i have is a know issue in the Dev Version. So i use now the recommended stable version from a Meber of the A320 NX team.

1 Like
8

I’ve found it’s important to watch the dot after you move the joystick around, then suddenly release it. My Hotas 4 literally vibrated until I manually damped the joystick’s motion. Watch that vibration if you have it, and use that to help you with the size of the dead zone you set. I’ve seen a lot of posts on dead zone and autopilot, and none of it worked for me until I saw that my joystick was “twitching” outside the dead zones I had set!

9

Yeah it’s a known issue in dev and experimental versions. Has been around for a few days now. Hopefully it will get fixed soon- the AP was working spectacularly during the past couple of weeks until this came back:-(

10

I have the same problem since last few days on approach phase with dev. A320NX.

  • The planned route / STARS, CSTR info… not shown on ND screen, have to use the default VRF Map as temporarily to orientate the airports (Washington Dulles, New Orleans and Louisville).
  • No altitudes shown at respected waypoints in MCDU
  • No estimate time at arrival runway and respected waypoints shown on MCDU (UTC 00:00)

Hope the team will fix it soon!

But they also updated the glass panels and looks really cool!