No engine start.
-
Thanks for reporting back! I'll double check things on my side as well.
@JGreen5278 Hope it works!
-
Had this problem happening again today, now on 0.1.1.
No controls set to prop/mixture/fuel etc -
What I do now is start at a runway with engines on, and then taxi back. the engines seem to start up normal after this. It could just be a MSFS2024 issue, as it still has many. I just wish I could have this great jet in X-plane 12. Would make my life easier.
-
2020 versions here. Everything was working perfectly until V1.2a and now cannot start engines at all. No fuel bindings or anything remotely similar. Following same checklists as before. Engines die almost immediately if I start flight on runway. Set to TO fails also. Now I just have an expensive unflyable Fokker 100 model. Restarted and restarted and restarted then uninstalled and reinstalled no change, no engines start at all. Opened support ticket…not feeling optimistic. Usually just comes back “we cannot replicate….” Or blame user for other add ons, which I have nothing new just a couple F100 liveries since before while the F100 was working and flying great with those liveries. Still I deleted those and no start. The one and ONLY thing that has actually changed was the update to V1.2a
-
There were no intentional changes to the engine logic or any control assignments in v1.2a, as it was only a very small update to cover a handful of items noticed post the larger v1.2 update: https://support.justflight.com/en/support/solutions/articles/17000152601-f70-f100-professional-changelog
From my experience, engine start issues that only affect some users are almost always related to a control assignment/hardware conflict.
The easiest way to test that is to temporarily unplug your flight sim hardware from your PC (joysticks, throttle quadrants, etc.) and then try to start the engines using the same method as previously. If the engines start with no hardware plugged in, then that suggests a control assignment conflict, and I recommend checking that FUEL VALVE, STARTER, MIXTURE or PROPELLER assignments are not unknowingly assigned to your hardware.
If that doesn't resolve the issues, then it could be something else, such as another mod/product causing a conflict. In any case, Just Flight Support will be best positioned to offer further assistance.
Mark - Just Flight
-
STATE SAVE Was the source of my problem.
I fixed my start failure issues by loading a flight and going into the Fokker100 settings in the EFB and disabling “State Saving”. Then restarted the same flight and my engines started again. I believe the issue is more related to the State Save functionality than anything else. Especially if the last flight with State Save enabled resulted in a crash, pulling engine fire levers, or engine flame out before being unable to start engines as per normal.
Didn’t need to remove my mixture settings from my Flight Yoke System, just need to be sure the mixture lever is always on full rich as with any add on. This was my solution, there could be others as well. Good luck all. -
I'm afraid to say I've had this problem for the first time today as well. Engine 2 starting fine, but engine 1 wouldn't start.
I've done around 15 succesful flights before, always with a cold and dark starting state and never had this issue. This was the first time I had enabled state saving after the previous flight. So I would consider state saving as a possible source for the issue.
After I ended and restarted the flight (state saving still enabled) the engine fired normally. So that makes any controller or key assignment issue much less likely in my opinion.
For reference, this was on 2024
