No engine start.
-
I unfortunately experienced the same issue this morning on the Fokker 70 VH-NUO MSFS 2024. No assigned bindings for fuel cut off. Have done two other flights with the Fokker with no issue.
Engine start up will not accept fuel and the N2 sits at 25%. Resolved the issue by restarting the Sim.
-
Encountering this issue as well. Moreso recently after updating to 1.1 int he Fokker 100
-
I’m experiencing the same issue. Have restarted the sim multiple times.
Even setting the status to ready for take off has no fuel flowing to engine one
-
Same issue, I've tried 3 or 4 times. Haven't been able to fly yet. I haven't tried restarting the sim, I just fly something else.
Try loading the aircraft like normal, cold and dark then selecting restart in the main menu not a permanent solution but perhaps it’ll at least get you
going. -
As well as making sure there aren't any control assignments interfering with the fuel values, can you confirm you've waited the 2 mins required after APU start for bleed pressure to become available? If you continue to have issues please contact support.
-
As well as making sure there aren't any control assignments interfering with the fuel values, can you confirm you've waited the 2 mins required after APU start for bleed pressure to become available? If you continue to have issues please contact support.
@JF-John the 2 min is not in the docs (as far as I can see), but when I had the same issue earlier today there was bleed air coming from the apu
-
Anytime you do a first load of an aircraft, close out back to desktop and restart. This ensures that all the WASM loads properly. Sometimes you don't have to, sometimes you do. Best practice is to close and restart so you don't waste a bunch of time hunting down a problem that really doesn't exist.
-
Just encountered this issue for the first time in the F70. I had positive bleed pressure from the APU. The fuel simply would not get introduced, and N2 remained around 25%
-
It's not something we are currently working on a fix for, as it's not something our development or testing teams are able to replicate. Usually, behaviours such as this that only affect a small number of customers are related to some sort of hardware conflict with control assignments, and/or a software conflict with another mod/product, so it's a matter of figuring out what the common denominator is between all customers that are experiencing the behaviour.
Our best suggestion for being able to properly track this would be for anyone experiencing this behaviour to raise a support ticket for this with Just Flight Support at the following link: https://www.justflight.com/support
Then our support team will be able to keep track of reports and hopefully start to find a trend.
Mark - Just Flight
-
We fully appreciate the frustration, and we certainly don't want customers to have a product they can't or won't use. We strongly recommend contacting Just Flight Support via the link above, who will be best suited to assist further.
There weren't any changes to the engines, throttles, or any other aircraft systems in the v0.1.1 update, so rolling back to the previous version won't likely make any difference to that behaviour. The changelog for v0.1.1 can be found here: https://support.justflight.com/en/support/solutions/articles/17000152601-f70-f100-professional-changelog
Mark - Just Flight
-
I'm afraid to say that I may have an admission and apology to make! I checked my X56 throttle unit and I'd assigned sliders to Mixture and Propeller controls. I've deleted these and the F70/F100s are starting fine! Maybe other pilots with the same problem could have the same solution?
Del -
I'm afraid to say that I may have an admission and apology to make! I checked my X56 throttle unit and I'd assigned sliders to Mixture and Propeller controls. I've deleted these and the F70/F100s are starting fine! Maybe other pilots with the same problem could have the same solution?
DelThanks for reporting back! I'll double check things on my side as well.
