FBW A320NX engine not starting correctly (please help)

Greetings,

I recently downloaded the newest FBW A320NX (stable version) and I am having an issue. I was curious if anyone here that is using it may have some advice.

In a nut shell, when I power up the engines you can hear them turn on but only spoil up to %1 when normally/on the old A320 Asobo version it spoiled up to 20% at idle.

If I increase throttle it’ll show the throttle is increasing but engines don’t spoil up or increase and the engine percentage doesn’t move either.

But.

If I do the old fashion “CTRL-E” hot key to start the aircraft everything starts up and the engines idle 20% and when I increase throttle it increases and plane moves as normal.

So it’s not a plane bug or controller bug because when I do the “CTRL-E” key to start everything it works fine.

This is sequence of overhead panel buttons I press to start (alaways worked in the past)

Battery 1 and 2
External power
All the pumps
ApU master
APU start.

Then when I’m ready I turn on APU bleed

Turn the “MODE NORM” switch to IGN/START.

Then power up eng 2
Then engine 1.

(*not including seatbelt/exit/ect switches)

Am I missing a step?

I tried watching videos but can’t catch anything anyone is doing that I’m not.

When I turn APU Bleed on and start it so I need to turn APU master off? Or. APU bleed off after the engine switches are on?

I’d appreciate any advice with this- yes I can just use the hot key to start it but I enjoy the simulation of using the switches and buttons

Thanks

I guess the only thing I can think of do you have enough fuel?

And what’s your outside temperature. The engines won’t start if it’s below -40° C

1 Like

…and as always (only for diagnosing, please report the issue if it is caused by a third-party mod!):

  • Run the mod without any custom livery (remove them from your community folder)
  • Run the A32NX without any other mod (remove them from your community folder)
  • Check, if your flightmodel setting is in “modern” (MSFS settings)
1 Like

I will check. It’s just strange if that was the case then why it would start just fine when using CTRL+E key.

This is one Klugy deal … It works then for months it does not. No clue what causes - been round and round with this. There are PROFILES on the FLy Pad that should start for you - but thats not the best way. It works about 50% of the time unfortunately. IF you watch the process on the fly pad you can try to emulate manually - I cant make it work. I did notice the profile “locked Cockpit Door” and also did the “Cockpit Recorder” test. Wheeee.
If it were specific to certain Community folder programs you would think there would be a list by now… right ? there isnt. Everyone just keeps saying delete your community folder (doesnt help).

Having same issues more than a year, ocassionally it starts but next time no ! Since when does CTRL E work ? I would b ethrilled if I can get aircraft started on RAMP to taxi for takeoff. Cannot do even using the CHECK LIST - automatic option ?

I’m not sure if using the checklist to fire up the A32NX is enough. It is a complex airplane. Try using our documentation.
https://docs.flybywiresim.com/pilots-corner/a32nx/a32nx-beginner-guide/overview/
(and turn off all assistant settings [MSFS] before)

Interestingly I cant get any A320 started so far… NEO or NEO V2. weird !
It does work once in a while ? then next flight no, reboot, no.
I have watched numerable You Tube videos, and even tried the AUTO CHECK LIST provided at the top of the screen in MSFS, and Neo V2 has Fly Pad option to “Ready to takeoff” still nutin ? so strange.

It does appear that N1 & N2 are movig up very slowly ! but never to the point where I can fly or feel any real activity in my seat vibration or sound .

Have you got it figured out yet?

I am also having the same problems! I have been starting the A32nx just fine up until recently. Unless the process changed, which I doubt it did. Whenever I turn on the engines, N2 climbs very slowly and when it reaches 60% it shuts off?

Even the automatic startup from the flypad doesn’t solve it. I tried uninstalling and reinstalling the mod but still no luck.

To clarify things: are you on 2020 or 2024?
(pls always mention that)

Microsoft Flight Sim 2020. I have never had these issues before, I also have the A380 installed and that one starts up just fine. The default A320 also starts fine, as well as the inibuilds A320 V2. It’s only the FBW that’s not starting and I do not know why.

Forgot to mention that I am using the A32NX v0.12.3 stable.

Could you uninstall the stable version (within our installer) and try the developer version?

Also: is your multiplayer turned on when that happens?

Ive given up and gone to the FENIX, but i just got a APU error on fenix for the first time in a dozen starts. I have a feeling that with the A320nx it has something to do with button assignments or hardware that is attached. I think I am going to disconnect several devices and re attach to see. This has been more than a year I have been trying to get passed this.
Can you tell me if yu have many of the buttons involved in start up assigned to devices ? or you are using your mouse in the cockpit ? Ive tried each version multiple times, rebooted, stood on my head, have both feet flat on the foor.

Can you tell me if you have many or any buttons assigned for the startup process ? I have assigned many of them to button box, and Honeycomb Alpha and Bravo.

Yup, I just did that and still no luck. Here is a video I took to better explain the issue. This thing wouldn’t let me paste a link properly for some reason:

www[.]youtube[.]com/watch?v=tSuQuxdItRo

No sir, I am simply using an xbox controller and my mouse like I always have, nothing has changed! It’s just an issue with either A32NX or FS2020 itself. I tried everything myself and still no luck unfortunately :frowning:

Thanks for the video

  1. Is your multiplayer on? (turn it off if so)
  2. Would you please move everything out of the community folder, including all liveries (so A32nx only with its default livery)
  3. Nothing else running in the background (FSUIPC, GSX, etc.)
  4. Would you pls switch the MSFS settings > accessibility > cockpit interaction system to ‘legacy’
  5. Also check if MSFS settings > flight model > is set to ‘modern’.
  6. Check if all MSFS assistance settings are off (also fuel is NOT set to infinity)
  7. Then restart the sim and try again

YESSSSSS IT WORKS!!!

Removing everything out of the community folder worked! Now I have to put things back one by one to figure out which livery/mod is causing the issue! Thanks so much for your help!!!

1 Like