Not 100% ready to call this a bug yet as I'm still very unfamiliar with the plane, having barely had a chance to fly it yet. However, this doesn't feel right to me so wanted to check if others are seeing the same issue or there's anything I need to try before I report it as such.

If I load into the Tristar cold and dark at the gate -- and I've tried this at multiple airports and both with the initial launch version and the current release -- I can't get the engines to start up with a single panel state load.

If I click on the "Ready for Takeoff" panel state, the APU is started followed by engine #2, and then... that's it. The PFB shows "Waiting for engine 1 to stabilize" without ever attempting to start engine #1. I've tried leaving it for a *long* time, and nothing ever happens by itself after that. The engine instruments remain as follows:



If I then return to the PFB and click Ready for Takeoff a *second* time, engine #1 starts up correctly, waits to stabilize and then the text instantly changes to "Waiting for engine 3 to stabilize", again without ever making any attempt to start that engine. Here's how things stabilize:



And finally, if I want all three engines running which I obviously do, I have to load the Ready for Takeoff panel state a third time.

Anyone else seeing this issue with the Ready for Takeoff panel state?

To follow on from the above, I've also tested after completely unplugging all controls except my mouse, keyboard and a single Xbox-compatible controller, with the keyboard/mouse settings being the MSFS 2024 defaults and the controller being used only for general controls but disabled for airplanes and the L-1011 500 specifically. There are no other controllers connected or detected, so the issue definitely isn't somehow caused by my controllers.