Engine startup sequence is very slow in MSFS 2024

[callebstrom]

Aircraft Version

Development

Build info

{
    "built": "2024-11-28T01:16:47+00:00",
    "ref": "refs/heads/master",
    "sha": "63c2b9f053448ad0c146fab1ec8c6328a55b1a76",
    "actor": "flogross89",
    "event_name": "manual",
    "pretty_release_name": "master:63c2b9f0",
    "version": "a32nx-v0.13.0-dev.63c2b9f"
}

Describe the bug

Starting engine 2 as per normal procedure (what previously took about 1 minute) now takes closer to 5-10 minutes. N2 creeps up very slowly (about 0.1% per second) and same thing with N1.

Engine 1 starts slightly quicker, but way slower than what I am used to seeing in this mod.

Expected behavior

I expected an engine startup time of around 1 minute per engine.

Steps to reproduce

1. Load into FBW A320neo in MSFS 2024
2. Do normal startup procedure: enable fuel pumps, turn on APU, turn on APU bleed, set IGN START, set ENG1 master to on
3. Observe the very slow n2 and n1 increase

References (optional)

No response

Additional info (optional)

Unclear if something has changed and I am doing something procedurally wrong here or if there is something wrong in the MSFS 2024 integration.

Following the same flow in the inibuilds version of the A320 yields a quicker and successful startup.

This occurs in both stable and dev versions. Also occurs after clearing caches, reinstalling the addon, etc. It also occurs using the Aircraft State "Ready for Taxi" and "Ready for Takeoff".

Worth noting is that I am starting the APU with A32NX_APU_MASTER_SWITCH, A32NX_APU_START and A32NX_APU_BLEED_ON_ON LVAR events (as these are bound to my physical APU switches.

Discord Username (optional)

No response

[heclak]

Tested the engine start in the dev build and engine start does happen in 1 minute. I started the chrono immediately with flipping the Engine Master switch. Engine avail message appeared at 1 minute 5 seconds.

[tracernz]

Note that the A32NX is not yet ready for MSFS2024.

[callebstrom]

@heclak were you using mouse interactions or the events I referenced above to complete the startup sequence? I.e. were you using hardware?

[heclak]

@heclak were you using mouse interactions or the events I referenced above to complete the startup sequence? I.e. were you using hardware?

@callebstrom oh. sorry I missed the part about you using LVARS. There were some changes to the APU and engine start code so your LVARs are probably triggering the pre-patched events. I'm not sure if/when the LVARS will work again due to some 2024 SDK changes. You probably have to use the mouse for now.

[callebstrom]

@heclak that makes perfect sense. I'll keep an eye on this and use a mouse for now. Thanks!

[Saschl]

@heclak that makes perfect sense. I'll keep an eye on this and use a mouse for now. Thanks!

Which tool are you using and are there additional events you use in your flow? We did not change the flow to fix this on our side, but just used another method to trigger events, as the previous one didn't work reliably in MSFS2024

[pefabian]

I have just had the same issue on the Stable build. I have done a normal flight from EHAM to EGMC, did a turnaround (not sure if they are officially supported, I know not on A380) and this happened. I did use a mouse.

Startup was normal until fuel introduction, at which point all of N2, EGT and N1 climbed abnormally slowly. Additionally, after AVAIL message, the engines did not react to throttle position and remained at idle.

After leaving to main menu and trying again, normal startup.

[pefabian]

I had a thought and confirmed this morning.

1. I did an engine start with fuel pumps turned off. Behaviour as described, EGT rising slowly past about 160, N2 slowdown at the same place, N1 barely rising
2. I turned on the fuel pumps, the startup went back to normal immediately, EGT rise and then drop, N1 normal runup, N2 normal runup.

[pefabian]

Also should note this was on 2020 not 2024.