A32NX altitude and ILS approach broke after MSFS UPDATE

Discussion Hub Aircraft
,
1

Hello Guys:

Since the new MSFS update from yesterday, I am having problems flying the A32NX, when in Autopilot the altitude always stucks at 300 feet below of the assigned, and ILS is terrible when approaching, Autothrottle doesn’t work ok on the approach neither.
Is there a way to fix this? Is anybody experiencing the same thing? I already tried re-installing with no luck.

My approach were all at the ILS R28 on KSFO airport, but the altitude problem is at all times, even in other airports or routes.

1 Like
2

Haven’t checked, but is there already an official update available for the NX?

edit: just checked at github and it says that latest version has been issued 21 days ago.

3

I have seen a post which recommends removing the 320NX folder from your Community folder and then totally reinstalling it from scratch. I did this after yrsterday’s update and not seen the problems you are having. The post also recommended doing the same if you have Navigraph navdata installed. I use the development version of the 320NX so cannot comment on the Released and Experimental versions.

4

What version do you use?

5

I have ILS problems as well at some airports, ILS missaligned at LEMD 32L, GCTS 07.
yesterday after SU IV installed last dev version.
Just now I have installed the last dev for testing:

“built”: “2021-05-26T09:08:11+00:00”,
“ref”: “master”,
“sha”: “a4c7ec6882f1b36cb65435f0c4ceb0e423ed6a09”,
“actor”: “tracernz”,
“event_name”: “manual”

edit:
I don´t use navigraph

6

I use the latest stable release 0.6.1
I removed the entire dir and reinstalled the latest stable again with no luck.
I don’t have navigraph.

The plane worked perfectly until the upgrade..now if I set the altitud to 10000 it stays at 9700 on the autopilot. ILS works really bad, goes up and down all the time while approaching and is impossible to land using ILS.

7

Could you try the dev version? Just for testing…

8

Sure, will try that now to see what happens..

9

I just tested the developer version, not sure what is happening but the plane went crazy and then it crashed right after the takeoff..hahahaha :rofl:
By the way…the new sounds of a32nx seems really awesome…I hope I can fix this soon to start flying like before..

:frowning:

1 Like
10

I’ve flown the dev version after SU4 and have no problems at all with it.

11

flight model set to modern?

1 Like
12

Good point!

13

Hi PZL

Were can I check that config?
May be the update restarted my configs on the plane or on the sim.
I also forgot to say that I use the Microsoft Store version of the game.

14

Options > General > Flight model > Modern

Even if it is set to modern I suggest you switch to Legacy, fly a few seconds and change it back to modern.

It happened to me that the FDM somehow got stuck at Legacy (although I never selected it) and I had to cycle it to get the modern FDM back.

15

Yes, it was on LEGACY…but I never touched that option before.
Let’s see what happens and if this was the cause of everything..

Thanks PZL

2 Likes
16

You are welcome :slight_smile:

Switching to modern will definitely fix it :+1:

17

You actually need “modern” to fly our plane. Me wondering how you flew it before… :face_with_raised_eyebrow:

18

For me the FDM switched to Legacy on its own as well (but still set/confirmed at Modern!) with SU4.

Pretty disturbing discovery IMO and it took quite some to find out what has happened.

19

Yes, that fixed the problem!
Tested the same route, airport and ILS approach and the plane works like before.

Seems that the FS update changed the mode for me without asking.

Thank you so much for the help guys!

Steve.

1 Like
21

We released a new dev version which forces the “modern” flight model, even when “legacy” is set on the MSFS settings. So this shouldn’t happen again. :slightly_smiling_face: