Engine cannot start

[PikaFr]

Aircraft Version

Stable

Build info

{
    "built": "2024-11-09T16:32:29+00:00",
    "ref": "refs/tags/v0.12.3",
    "sha": "7c0bb7fee6051b07edd3435d923b7acf1cec2945",
    "actor": "FoxtrotSierra6829",
    "event_name": "manual",
    "pretty_release_name": "stable/v0.12.3",
    "version": "a32nx-v0.12.3-rel.7c0bb7f"
}

Describe the bug

I cannot lunch my engines, when the APU is ON, the ENG1 start bouton automaticly goes ON and i cannot turn it OFF, both of the ENGINES don't want to start. I have FAULT on both engine in the top panel

The same actions on the original A320Neo from Microsoft work to start the plane

I am in MFS24

Expected behavior

I jsut can't lunch ENG1/2

Steps to reproduce

I have followed the Officials Checklists and I have followed some tutorials on Youtube
The Start bouton ENG1 turn ON when the APU is Available

References (optional)

No response

Additional info (optional)

No response

Discord Username (optional)

pika_fr

[G-DRAW]

I see the problem with your configuration of certain switches.

First of all you've got ENG 2 MAN Start selected ON, (the blue ON light at the bottom right corner of the overhead panel).
Secondly you are trying to start Engine 1 automatically.

So what is happenning here is the APU is struggling to supply compressed air to both engines at the same time. You can only start 1 engine at a time on the A320 family's.

So it appears that you've tried to do a manual start on Engine 2 and at the same time do normal automatic Engine start on Engine 1.

On the bottom right corner of the overhead panel, set ENG 2 MAN Start push button OFF, and you should be good to go from there.

[PikaFr]

I had indeed tried to force the start of the engines, so I followed your instructions but the problem does not seem to be resolved, after a long wait N1 finally reaches 20% (but the engines do not seem operational according to the MFS HUD) but starts to drop then turn off, still 0 PSI on ECAM ENG

Enregistrement.2024-12-17.191923.mp4

[tracernz]

The stable version does not have any MSFS2024 compatibility patches, and even the dev (master) version is not fully compatible yet.

[ShallonTZ]

I am having this same issue in MSFS 2024.

As soon as the APU starts (AVAIL shows on start button) then the engine 1 master switch (E1MS) automatically turns to on. If you try and turn the E1MS off again it turns to the off position and then 1 second later turns itself back to the on position.

I have tried shutting the APU down again after this behaviour and once the APU is off you can switch the E1MS to the off position and it stays there, as is the expected behaviour. If you then start the APU again exactly the same unexpected behaviour starts as soon as APU is available.

[dkkavanagh17]

Same issue as well for me. I'm running MSFS 2024, latest patch, with the stable version of the A32NX from the Fly By Wire installer.

I've uninstalled all A32NX liveries from the community folder in case they were the cause of the issue. I've uninstalled and reinstalled the stable version of A32NX.

I've reproduced this issue at EKCH, EDDB, YSSY, so I'm fairly confident it is not region-specific.

Just as @ShallonTZ described, If the APU is AVAIL (as shown on the ECAM), then the Engine 1 Master Switch turns to ON. It appears that it actually is on because Engine 1 begins to slowly spool up (as shown on the ECAM). If the switch is turned to OFF, it returns to ON about a second later. This lasts as long as the APU is AVAIL, after which the behaviour ends. This behaviour does not appear to affect the Engine 2 Master Switch.

This happens both from a cold and dark gate start, and a runway start.

If it occurs during a cold and dark gate start then starting the engines in a realistic manner is (as far as I know) impossible. Engine 1 can never be started after Engine 2, and Engine 1 will take around 3 minutes to reach slightly around ~50 N2, at which point it will suddenly drop down again.

The same behaviour can be replicated from a runway start, if the Engine 1 Master Switch is turned off it will return to on.

I would be greatly appreciative if anyone could find a solution to this, because as it stands the A32NX is not realistically flyable in the current version of MSFS 2024, which is a shame because it is one of my favourite aircraft in MSFS.

[tshomas]

"I would be greatly appreciative if anyone could find a solution to this, because as it stands the A32NX is not realistically flyable in the current version of MSFS 2024, which is a shame because it is one of my favourite aircraft in MSFS."

The aircraft isn't compatible with MSFS2024 and the team haven't said it is ready yet, which is why you're experiencing this bug. This is one of many bugs which is preventing us from saying it's ready, so yes, the plane is not flyable in MSFS2024 yet.

[dkkavanagh17]

Ah, well thanks very much. It works very well otherwise though. Is there a way for someone to add the "MSFS2024" tag to this issue?

[tracernz]

You may like to try the dev version rather than stable. You should have a lot more success in MSFS2024, but perhaps still some smaller bugs.

[FinnakaLite]

Having similar issues in MSFS 2020, #9691

[dkkavanagh17]

You may like to try the dev version rather than stable. You should have a lot more success in MSFS2024, but perhaps still some smaller bugs.

I probably should've mentioned that I switched to the dev version after reading a similiar issue, and it works fine.

[tracernz]

Going to close this as it seems it is fixed already in master (dev version).