|
|
Post by rlbomber on Sept 28, 2017 7:11:22 GMT -5
I would like to know how to keep the engines from shutting down when passengers are boarding? I'm using FSCaptain version 1.7.4 with Wilco/Feelthere Evelution 737. Trying to do a little research, it was stated that by turning off the "disable engine shutdown" in the config file found in the FSCapatain\config. But, this did nothing, the jet engines still shut down.
I'm trying to keep the engines from shutting down due to the complexity of having to start them again.
Is there something I'm missing?
Richard |
|
|
|
Post by Travis on Sept 28, 2017 19:14:49 GMT -5
Hello Richard, I've tested the option DISABLESHUTDOWN=1 just now, and that allows me to board PAX and go OUT with my CRJ's engines running. (My flight crew did a fingers and toes count, and everyone made it aboard in fine fettle!  ) To know what's happening with your aircraft, I'd humbly ask for you to either email us (or attach to a new forum post) an FCDU log of a flight where you've experienced this. If your DISABLESHUTDOWN option value is 0, then we will not board PAX until you shut down your engines. We put a message to that effect on the FCDU. That's all we do. Our default behavior tries to mimic real world operations. I don't know of an airline that will board passengers on a turbojet with the aircraft's engines running. That's why we offer the 'global' option to DISABLESHUTDOWN.
From your post, I could assume that your engines are shutting down instead of us telling you to shut down your engines. If I am mistaken in my assumption, please excuse the rest of this post....  We do not shut down engines at boarding or at going out, so perhaps something else is doing that? The only other thing I can guess at is that when it's time to start boarding passengers, we open the PAX and Cargo doors for an aircraft, and that something else is shutting down your engines when they see the doors open. You could test that in your aircraft (which we do not have) without running FSCaptain to see if your aircraft (or another add-on) is stopping your engines. Best regards, |
|
|
|
Post by rlbomber on Sept 28, 2017 20:52:29 GMT -5
Thanks for the response. I can confirm that as soon as I click on normal load, the engines shut down. It actually happens with the stardard CRJ700 as well. Hmmmmmm, now I have to see what is causing this. I will test this without running FSCaptain. I will post a log as well and hopefully that will help find my issue.
|
|
|
|
Post by rlbomber on Sept 29, 2017 6:38:51 GMT -5
Travis, It seems that it only happens when running FSCaptain. I load up the FSX, then the flight plan and as soon as I log in to FSCaptain and hit proceed, the engines shut down. This happens in all the various aircraft and I do not have any other programs running in the background such as REX weather. Please see the latest flight log below. I ended the flight as soon as the engines shut down. It does seem that FSCaptain is causing this but if you state it doesn't then I will need to research some more. FSCaptain log.txt (10.56 KB) |
|
|
|
Post by Travis on Sept 29, 2017 12:29:03 GMT -5
Well if it's happening with more than one aircraft then it's not "something that the third-party aircraft is doing."
The log you posted doesn't include flight data - the FSCaptain log mostly shows your initial options and interface data with the sim.
Please post your FCDU log (you can upload it as an attachment as it can be quite long) because I'm wondering if your aircraft are having their fuel levels set to zero - just for a moment - as we initialize the aircraft's state.
Regards,
|
|
|
|
Post by rlbomber on Sept 29, 2017 13:07:57 GMT -5
Travis, that would actually make sense! What's strange is that I reinstalled FSX last week and just finalized everything. I downloaded the latest build of FSCaptain and after it was installed, I copied the FSCaptain directory from the old drive to this new one. I've attached a the FCDU of a completed flight.
FCDU_20170926_183545.log (237.57 KB)
|
|
|
|
Post by rlbomber on Sept 30, 2017 6:55:04 GMT -5
Travis, that's exactly what's happening. As soon as I hit proceed, the fuel level goes to 0 lbs and then the motors shut down. Then it loads the proper amount of fuel that was designated. So, how do I keep that from happening?
|
|
|
|
Post by rlbomber on Sept 30, 2017 8:50:50 GMT -5
Travis, I finally figured it out. Under the Profile.cfg I turned off the autofuel and now the engines don't shut down.
|
|
|
|
Post by Travis on Sept 30, 2017 22:52:02 GMT -5
You could instead check the Suppress Auto Fuel Load for a particular aircraft.
Or you could wait 40 hours for the upcoming 1.8.0 Beta 2 (which I am terming a "suggested upgrade") that shouldn't zero out fuel before setting it to "minimums".
Best,
|
|
|
|
Post by rlbomber on Oct 1, 2017 9:57:38 GMT -5
I can wait an additional 40 hours. Thanks.
|
|
|
|
Post by rlbomber on Oct 6, 2017 16:16:40 GMT -5
So, I downloaded and installed the 1.8.0 Beta 2 fired it up and guess what happened? The fuel went to 0 and the engines shut down! Travis, I thought you stated that this was going to be fixed in this update, what happened?
|
|
|
|
Post by Travis on Oct 7, 2017 13:39:58 GMT -5
I can only imagine one way it's still failing for you. Please email/post your FCDU and FSCaptain logs for this!
Regards,
|
|
|
|
Post by rlbomber on Oct 8, 2017 12:58:14 GMT -5
|
|
|
|
Post by rlbomber on Oct 10, 2017 5:47:56 GMT -5
Travis, anything on this yet?
|
|
|
|
Post by Travis on Oct 10, 2017 11:26:10 GMT -5
Your logs didn't show any loading activity at all.
And I sent an email about 11 hours ago....
Regards,
|
|
)