I would like to know if anyone has experienced this before I make a bug report.
On my last several flights after landing, then running APU and shutting down both engines, I had trouble restarting both of them for my next flight.
For example I’d successfully restart the right engine, but the left engine would only partially start up after turning on the fuel values. All fuel pumps are on. I would get it to start by toggling the ignition switch on and off or sometimes toggling the fuel valves for both right and left engines to finally get it to power up the left engine.
It’s a thing in the real world and modelled correctly in the sim. After shutting down, the engines are very hot on the Neo. So to avoid excessive temperatures in parts of the engines, they spin for considerably longer during startup before having fuel injected in order to even out and temperature within. First flight of the day, they are cold and so can be started quicker
Ok well I didn’t noticed any of the temperature readings to be in the red, but I’ll experiment with this later and wait longer for the engine 1 to spool up. I know it was at least 5 mins before I tried to start up again.
I did a few test flights in the new A320 v2 before switching back to other airliners, but don’t recall any engine starting issues of this nature.
As Azlog mentioned, what may be happening is you’re experiencing the bowed rotor motoring process. If the engines are still warm from the last flight, there can be up to 90 seconds of motoring to cool the engine down and ensure the N1 and N2 shafts are straightened out (after shutdown they can bow due to residual temperature and being stationary) before fuel will be introduced. Almost any time the aircraft has already been recently flown, you’ll notice this motoring time. Referring to your prior comment, nothing will be in the red - the temperatures are perfectly normal, but motoring will still be required. This, of course, assumes proper simulation from iniBuilds.
However, this is usually consistent between engines. You mentioned one engine starts fine and the other requires a noticeable delay which makes me wonder if this is something different, or perhaps not-100%-accurate modeling of the bowed rotor motoring process. If both engines have been shut down for the same amount of time, and both engine EGTs are comparable, it’s possible there’s a bug in the simulation of the motoring process.