Hate to be the gadfly, but the Copilot cannot start QW757

[carcoll]

I tried it three times to make sure it wasn't something I did, but no, the FO does not start the engines on QW757.

The FO announces starting engine 2... then nothing...

Its easy to start with CTRL - E of course, but it does appear to be a bug.

[Matthew King]

What do you have in your 757.cfg file? I think there's an option that allows you to control the fuel controllers.

[carcoll]

I will take a look and report back.

Thanks for the responses Matthew.

[carcoll]

OK I added the options line EnableManualEngStart=1

No change.

I watched the Pre Flight Flow and Before Flight Flow and the FO puts on the Pack Buttons which inhibit the engine start.

I manually put the Pack Buttons off selected Copilot Start Engines and the FO was able to start the engines.

I added the options line off of QW757 Available Option doc Packs=1 and then tried but the FO still turns on the Pack Buttons and doesn’t turn the engine on until I manually turn them off.

I then tried the option to Packs=0 and still the FO puts the Pack Buttons on and can’t turn on the engines.

Again, I am a fan of your work and this app just trying to help out.

[Matthew King]

We'll get it worked out! Can you post the entire contents of your 757.cfg here

[carcoll]

Here you go:


Irs=1
YawDampers=1
InhibitCockpitSoundsOnStopSound=1
PlayAnnouncements=1
EADIGndColor=105,59,5
EADISkyColor=25,142,186
EnableManualEngStart=1
Packs=0

[Matthew King]

hmmm...so you don't start from a cold and dark state? I'll make a change this week and get it out on Saturday.

[carcoll]

Thank you Matthew. Keep up the great work!

[Matthew King]

Hey Carcoll! I appreciate you patience, sir. I've updated FSFO to account for you issue. If you're continuing to have issues with the QW757, would you mind opening the user.cfg and look for the following entry:

[MISC]
pauseChklst=500
qwAutoStart=0 //change this entry from 0 to 1 and save the file.