A32nx new issues

Hi All,
All of a sudden it seems the A32NX has regressed back about 6 months. It was rock solid for a long time. I have had 2 flights now where it has just kept climbing stopped following the flight plan, going direct to the runway. A few versions back and after SIM Update 4 this was all in check.

This is the latest version I am using
image

Is it a known thing or is it a bug?

1 Like

In regards to the flight plan stuff, it still uses the default flight plan manager and it’s know that there are issues. It heavily depends on the route etc how good/bad it is.

In regards to aircraft keeping climbing
there are very very few real bugs in the custom autopilot. So with very high probability it’s a bug - a usage bug.

Beside that you provide almost no information what happened. What did your FMA on the top of the PFD show?

MACH ALT NAV - all green.
AP, FD 1+2 , A/THR - white

FMS Flight Plan set from simbreif, as was Weights. SID’s / STARS etc set as best they can be.

However the plane got to FL350 which is correct, 2 mins or so after just tried to climb to FL410 and obviously lost speed till the protections took over.

I use Toliss/Flight Factor etc, I know what I am doing, Nothing else changed on the MCP, Managed speed, Nav, climbed to Crz using Open Climb. It just went crazy
 I cant see why? I left it for a while, I tried resetting the plane, but I could not override anything, it was flying at around 18degrees of pitch on the red bar speed tape
 I could not make manual inputs, as when I did it would nose dive quite deeply, with seemingly no control.

The other flight was all fine, but the Direct to RW issue occurred, it had stopped for ages.

I am not complaining just asking so I dont keep trying and getting the same results. I dont just kick the tires and light fires, I take it seriously so dont want to waste an hour setting things up, planning etc for it all to go wrong anyway.

I am doing the flight again

Its asking to me enter dest data early I think

Maximum operating altitude of the A320neo is 39800 ft so climbing to FL410 is a bit ambitious


I‘ve read that it was usually going on FL350 and then it lost speed when you tried to climb to FL410.

What was going on there? What did you see on the FMA?

Beside that, if you want you can send me the FDR file of that flight, then I can take a look what actually happened. I have created the custom fly-by-wire and custom autopilot. You find the files in the folder described on that page, section „Reporting Issues“:
https://docs.flybywiresim.com/start/autopilot-fbw/

I didn’t try to climb to anything. This started on it’s own? When I finish the current flight I will get those file. This happened with no interaction from me. I wouldn’t take a bus above FL390 unless its a 350/380

Everything was going fine, then it did that. Will the files from the last flight be there? Many thanks

As I said my Flight plan was filed for FL350, why would I try and climb higher? Look at the 2 shots I posted! FL350 on the MCP and in the MCDU. It for whatever reason decided that it wanted to climb to FL410 I had no control over that as explained.

I can see how you would have been quite surprised by the airplane suddenly climbing by itself. How did you know it was climbing to FL410? Or was it just climbing and you inferred it was trying to climb to 410?

The airplane may climb and descent a bit around the selected altitude in order to hold the correct speed within a certain tolerance. But it sounds like this is not your issue.

It is possible that you got hit by a sudden weather shift (i.e., temperature shift) causing the Mach number to increase into the overspeed region and kicking in the airplane’s high speed protection system. There have been numerous issues reported with MSFS and REX weather shifts. This would cause the airplane to pitch up and climb.

Depending on your response to that situation, the autopilot may disconnect, and you may make the situation worse, or correct too much and get into a high aoa/low speed protection situation.

Si I was flying along just fine. Then the power dropped slightly, so no knee jerk reactions, I am at FL350 I have plenty of alt to gain speed. I checked the engines, could see they were now increasing thrust up to about 90% the plane then levelled off at 35,200 ok so usually the AP just brings you back down the excess 200ft
 you are correct wind does this


However there was a sudden drop again, a massive nose high pitch, but a 2500ft climb rate, at this point i tried to intervene:
AP off nose forward, no auto trim now, as soon i removed pressure, nose back up like the elevators were stuck or something. the plane then hit fl410 and kind of just stayed there happily at what I would assume Alpha protection pitched up at about 18+ degrees and just flying along, At that point I could do nothing, I was no longer able to interact with the plane.

I just did the whole flight again and it was fine.

I hope you were able to find the FDR file for that flight and send it to Aguther. It is too difficult from your description to speculate on what may have caused the upset. You say the power dropped and that you needed to gain speed, but then go on to say that the plane leveled off at 35,200 feet. This sounds like the speed was too high, and the airplane climbed slightly to try to offset the speed.

Then you say there was a sudden drop again. I’m assuming you are referring to N1, rather than speed or altitude. The reduction in N1, followed by a pitch up sounds like the high speed protection kicking in after an overspeed situation. I still think this is consistent with a temperature anomaly introduced by live weather system bugs. But without the FDR, that is simply speculation.

FYI, the airplane will continue to try to correct the overspeed situation by a pitch-up command until that situation is rectified. It doesn’t matter whether the autopilot is on or off. In fact, it will disconnect the autopilot at MMO + 0.04 (or VMO +15).

Glad you were able to re-do the flight with no problem.

1 Like

Q: How do we report bugs?

A: You can report bugs to us via the #support channel in the Discord server. Addtionally, you can start/create a GitHub issue (please make sure your issue doesn’t already exist).

https://github.com/flybywiresim/a32nx/issues?q=is%3Aopen+is%3Aissue

1 Like

Just one minor note. In case of AP engaged, the overspeed protection (HSP) engages a bit differently than in manual flight:

The lovely thing about forums is they’re a place to discuss things.

Just to be clear to all
 I did not change speed, change ALT nothing, Everything was fine. The MCP the MCDU was all ok. I changed nothing, I have seen the weather in MSFS push the plane up and down in a few instances +/- 1000’s of feet, this can happen in real life if you hit bad turbulence or a Clear Air Burst.

This behaviour I saw was all un-commanded. I dont get why ppl assume when ppl have issues its always their fault. I repeated the flight again and it was fine.

No Disrespect but I use Toliss and Flight factor add-ons which are way more complex “AT THE MOMENT” and dont have all the issues the base sim in MSFS has" AT THE MOMENT" so I know how an A319-A321 Neo/CEO/PW-JM/IAE etc should work as best as a non ATP Pilot could or should.

The plane behaved perfectly untill this point, at which point I HAD NO CONTROL over it. it was stuck in its perpetual high AOA and I guess at low speed protection
 That’s it, no interaction from me.

The reason why I am asking is because:

  1. The mod has been amazing up till now, never had an issues beyond the usual sim related issues.
  2. Over the last 3 flights the plane has been behaving as if it was like 6 months ago, I am not complaining, I am not moaning I am just asking because well
I dont know.

Yeah, please also understand that it’s hard to help you as long as I don’t get more information. Now you give me the info it was in high AoA protection


Over time there have been systems added like high AoA and they are of course depending on what the sim is doing. So it’s also not under our control alone. Maybe you got icing? Who knows
it’s just guesses up to now.

I invite you to send me the FDR files as a link via private message from those flights and I can take a look into around 400 parameters of that flight like environment conditions but also which mode the AP was and what the plane was doing then. Those files contain no personal information at all, only flight data from the sim. The tool to convert it is also in the A32NX repo (src/fdr2csv).

If you don’t want this please make a video or at least screenshots the next time it happens, this helps a lot understanding what is happening.

Where can I find these files and I will send them to you. I am not complaining by the way. It is my intention that as soon as I can use your custom LNAV I think I will be saying good bye to Xplane. Airbus is my favourite plane, I have nothing but love and respect for you guys and your amazing addon.

I really want this plane to succeed that’s all, as I am sure you guys do as you all put your hearts and souls into it.

Read carefully, please.

Rules for 3rd Party Addon Category
2 Do not post bug reports here. Contact the addon authors to report bugs (see table below)

[READ FIRST] Rules for 3rd Party Addon Category - Third Party Addon Discussion - Microsoft Flight
Simulator Forums

What, the original post or your latest information?

Anyway, great thread, really interested on how this progresses!

See here:
Autopilot / Fly-By-Wire - FlyByWire Simulations Guides

If you need a file transfer, i.e. you can something like this:
SwissTransfer.com - Send large files securely and free of charge

Just give you an idea how this will look like (from a different flight):





I have sent you the files. Many thanks.

1 Like

Hi,

I have observed bizarre behavior of throttle in most recent build (5f697b1). Despite of not changing anything in my throttle sensitivities and calibrations, idle setting enables the reverses.

Smallest increase of throttle results in reaching the 60% of power.

Furthermore I am unable to select the “Speed” & “Climb” modes.
Has anyone observed such issues as well? I am not sure if that is a bug or something on my side.

1 Like

Check your throttle calibration in the EFB again. Maybe it changed somehow.