No engine start.
-
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.
-
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 -
-
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
