Hello,

What a great product fused with another great product. Ever since development was announced, I followed the threads and Store closely. 1st Impressions: Awesome!!! 
But if there is one thing I would complain about, is the Preliminary Cockpit Procedure timing is a bit off. 

To be exact, as soon as the PM turns on the GPU, he conducts the APU fire test and resumes his flows before all systems are booted up. I would hope to see the PM wait until all systems are booted up, until he continues with the APU Fire test and so On. Otherwise he doesn't hear the Aural Indications part of the Procedure.  I don't think anyone would change FSLabs default settings of 40 seconds until the Self Tests are conducted, however usually all systems are booted up about 90 Seconds after AC Power is established, which would be a good time for the PM to then do the APU Fire test and the rest of the Preliminary Flows. 

Otherwise I have nothing. If I do find something, I'll be happy to report.

With Kind Regards,

Ben

Hi Ben,

Glad you like it 🙂

Let me think about this.  I could make it a config option.

When did my TR in the bus, we went fast and exactly by the Airbus manuals.  This version of FS2Crew is a verbatim copy of that the best I could do.

We didn't pause like you're suggesting, and in the era of ultra short turn around times where there are few seconds to spare, pausing may not be done either in actual practice, but it could vary from person to person and depend on how much time you have.

To give you a sense of how time sensitive things were, some instructors told us to set the Takeoff trim prior to the After Start flow just to save a few seconds.

 

 

 

Okay, I just spoke to one of my consultants.

Waiting 60 seconds or so after power established is totally okay.

So I added that to the next version 🙂

 

That's awesome! I'm glad I could help. Well, normally you only do an APU FIre test on the First Flight of the day or on a Crew change, so I would say on the FIrst Flight of the Day or crew change, you would want to do it properly, even if it means waiting a Minute. However, I do understand that every Airline does it differently to either save time or other reasons. In a proper Turnaround State, you wouldn't test it again anyways, which will save the airline some time. Either way, looking forward to future updates. 

Ben. 

1. I just used the latest beta and tested it, however the issue that I hoped to have changed, isn't 100% perfect yet. After the PM said he is conducting the APU fire test, it took another 8-10 seconds before the APU Aural indication was audible (because the Aircraft isn't just yet powered up completely). I know this because as soon as he said this. I held down the test button and counted up. Perhaps add another 10 seconds to the flow before he does the APU fire test, to wich he can immediately continue with his other Preliminary flows. 
I would also recommend this extra 70 seconds delay before testing the APU Fire system should only be implemented when the user has the 'USER STARTS APU (PRE-FLIGHT)' set to YES. 

 

2. When the config option 'SKIP EXTERIOR INSPECTION' is set to YES, then when you start the PF Flows, it should start at 30 Minutes instead of 35. 

With kind regards,

 

Ben

HI Ben,

#1 I can definitely do.

#2 maybe.