Checklist cancelled, Captain

[FS++]

38 minutes ago, V1ROTA7E said:

I'm also trying to create a script for takeoff where I say "set speed, climb thrust." The climb thrust part works, but I can't get the FO to input a pre-desired speed. Ideally, when I say "set speed, climb thrust" the FO would set the speed bug to the "UP" bug, then select climb thrust...but since the latter isn't possible (i don't think) I'd just like them to set 220 knots, then select climb thrust with this command. Unfortunately, when I spell it out in the VoxScript, it doesn't take. See the picture:

In general, you cannot script dialing commands like "set speed two one four" or "vhf one one eighteen seven". Only exception is flaps setting which you can.

A few other speeds can be scripted like "set speed v two"

Since FO is trained for "bug up" command and knows how to compute it. Add these commands to your custom flow

climb thrust

bug up speed

[FS++]

1 hour ago, V1ROTA7E said:

I'm not sure how much work it would be, but I'd love to be able to adjust call-outs.

If I could go digging around and edit these parameters please let me know where to look.

For instance, at our company we have:

At 60 knots the PM says "Thrust set"

Not there

At positive climb indication: Positive Rate

Already implemented

At V2: No call

It's there, and can be made optional

At 10,000: the PM says "10,000" this is for climb and descent

Already implemented

At 18,000 (in the US): PM says "Transition" for climb and descent - would be neat to change it, or preset it for your departure and destination, or just read it from the FMC

Fo always calls "transition altitude" on climb and "transition level on descent"

He knows TL level in US is 180

Outside the US, he can either get the value from Simbrief if using that platform, or by looking up a table of knows transition altitudes, whuich can then be overriden by whatever you type in FMC CDU. The value will be read periodically to ensure it has the latest input. Same applies for Vspeeds.

At 1,000' RA: PF states stable, PM states stable. Although this is a PF to PM challenge, the counter to that response is "Unstable, go around." It'd be neat for the PM to detect a stable approach (flaps set, on speed, descent rate <1000FPM, etc)

With the nagging feature ON, it's not just the rate of descent he looks at. Bank angle, pitch and other parameters).

Since most people don't enable nagging, the check will be made as part of the "call-outs and monitoring"

Going back to the engine start, I've been able to "fake" everything by adding a delay of 60 seconds after the action of putting the starter to ground....however, our FOs say "starter cut-out" just like your hard programed one does.

Try removing "verbose" option for the custom flow that triggers the engine start.

I'd love to keep your automatic start, but make some tweaks to it. For example, Have the ability to say "Start engine number 2" with the response "starting 2 --silence, starter cut out -- normal start." In other words, not reading the engine start parameters out loud.

 

I'm building emergency procedures as well, so for this example, if we have an impending hot start, or a hung start, I can say something like "engine 2 aborted start immediate action items." I'll place the fuel control switch to cutoff, and then the rest of the start sequence calls are cancelled while the FO reads the emergency checklist without overlapping calls from the normal start.

There are two ways you can make him read something.

You added a specific section to checklist to handle that specific emergency. Just add the trigger sentence for that section to the end of the custom flow

The other way, is to write a few "Notify" statements in the flow;

It's possible to pause a flow either by specifying the time in seconds, or until you tell Fo "resume the flow".

This program is awesome, I'd just like to have a bit more control over phraseology and differing conditions, since I'm (and probably others) am using this to train and practice.

Thanks for feedback.

This is what most people don't understand. They think it's similar to others.

Voice control in our world means that. Talk as naturally as possible and make it the closer it can be to "shared cockpit" nirvana. No two MCE users will have the same crew experience. Ask co-pilot what you want, when you want and using the verbiage you want.

It's not a passive scripted adventure where you are expected to sit there like a duck and read tons of instructions in order to workout where you fit in (what to say exactly to the letter and exactly at what time). It's the software that should adapt to your needs.

So yes, we are proud of this. MCE is the only voice based crew simulation nearly fit for recurrent training.

I say nearly because although the recorded FO voice packs are huge (4600+ recordings per voice and there are 10 of them), once you start creating super complex emergency procedures where Fo reads the real world QRH for you, you'll notice he/she may not have some of the vocabulary. In that case, may want to get a very good Text To Speech font (which will be able to output any statement you add to a flow) and your imagination is the limit.

Obviously, 80% of users don't go that far, therefore the recoded audio largely fits the bill.

 

 

 

 

 

 

[V1ROTA7E]

22 hours ago, FS++ said:

At positive climb indication: Positive Rate

Already implemented

Sorta, he's a bit late with the call, and he doesn't say "Positive Rate"...sometimes he'll say "positive climb" "positive rate of climb" etc.

 

22 hours ago, FS++ said:

At 10,000: the PM says "10,000" this is for climb and descent

Already implemented

Again, kinda...He says "approaching 10,000".

 

22 hours ago, FS++ said:

At 1,000' RA: PF states stable, PM states stable. Although this is a PF to PM challenge, the counter to that response is "Unstable, go around." It'd be neat for the PM to detect a stable approach (flaps set, on speed, descent rate <1000FPM, etc)

With the nagging feature ON, it's not just the rate of descent he looks at. Bank angle, pitch and other parameters).

Since most people don't enable nagging, the check will be made as part of the "call-outs and monitoring"

I tried the nagging feature, but also found it annoying. Not looking for suggestions from the FO or how uncomfortable he is, I just want basic trend call outs (airspeed, altitude, etc) and on approach either a "Stable" or "Unstable, go around" below 1000'.

 

22 hours ago, FS++ said:

Try removing "verbose" option for the custom flow that triggers the engine start.

I'd love to keep your automatic start, but make some tweaks to it. For example, Have the ability to say "Start engine number 2" with the response "starting 2 --silence, starter cut out -- normal start." In other words, not reading the engine start parameters out loud.

I tried that, but he still takes control of the Fuel control lever. I'd like to have control of that, just in case we have a hot/hung/no light off/no oil pressure during start.

 

I'd also like to request the ability to turn of the 500' and 1000' call made by the FO since the plane's GPWS can do it automatically.

 

Lastly, is there an option for the FO to read the items listed on the recall panel? His side's items, i.e. AIR COND, DOORS, etc. When we do a "Recall Review" after an emergency or as part of normal operations, it can prompt an emergency checklist. For instance, if the AIR COND light is illuminated on the recall after it's been pressed or shows up as a master caution, he'll say "Air conditioning" or "Master caution, Air conditioning." I can then look up at the overhead and see what the problem is. Let's say it's an OFF SCHED DESCENT. I can then call for the Off Schedule Descent non normal checklist (which i'll create using the VoxScript), and he'll proceed to read/do the stuff in the book. After completing the checklist, I'll call for a "Recall review" again. If the item has been remedied, and there's no associated light, the recall will be blank, and he can then respond with "No Items." I hope that makes sense.

 

I know this may seem annoying asking for all this stuff, but this is a great tool to train with. One of the biggest challenges when changing aircraft in the real world is learning the specific call-outs and responses. So hearing accurate phraseology is crucial as it can jog your memory if you forgot to do something.

 

Thanks again for everything, and I apologize for being so nit-picky.

[FS++]

2 hours ago, V1ROTA7E said:

Sorta, he's a bit late with the call, and he doesn't say "Positive Rate"...sometimes he'll say "positive climb" "positive rate of climb" etc.

 

Again, kinda...He says "approaching 10,000".

 

I tried the nagging feature, but also found it annoying. Not looking for suggestions from the FO or how uncomfortable he is, I just want basic trend call outs (airspeed, altitude, etc) and on approach either a "Stable" or "Unstable, go around" below 1000'.

 

I tried that, but he still takes control of the Fuel control lever. I'd like to have control of that, just in case we have a hot/hung/no light off/no oil pressure during start.

 

I'd also like to request the ability to turn of the 500' and 1000' call made by the FO since the plane's GPWS can do it automatically.

 

Lastly, is there an option for the FO to read the items listed on the recall panel? His side's items, i.e. AIR COND, DOORS, etc. When we do a "Recall Review" after an emergency or as part of normal operations, it can prompt an emergency checklist. For instance, if the AIR COND light is illuminated on the recall after it's been pressed or shows up as a master caution, he'll say "Air conditioning" or "Master caution, Air conditioning." I can then look up at the overhead and see what the problem is. Let's say it's an OFF SCHED DESCENT. I can then call for the Off Schedule Descent non normal checklist (which i'll create using the VoxScript), and he'll proceed to read/do the stuff in the book. After completing the checklist, I'll call for a "Recall review" again. If the item has been remedied, and there's no associated light, the recall will be blank, and he can then respond with "No Items." I hope that makes sense.

 

I know this may seem annoying asking for all this stuff, but this is a great tool to train with. One of the biggest challenges when changing aircraft in the real world is learning the specific call-outs and responses. So hearing accurate phraseology is crucial as it can jog your memory if you forgot to do something.

 

Thanks again for everything, and I apologize for being so nit-picky.

OK, some changes will be implemented. Will get back to you as soon as possible.

 

[FS++]

On 11/3/2022 at 4:45 PM, V1ROTA7E said:

I tried that, but he still takes control of the Fuel control lever. I'd like to have control of that, just in case we have a hot/hung/no light off/no oil pressure during start.

 

In the end, you won't need a custom flow for this.

You can just use the "start engine two", "start engine one" built-in commands. I forgot to mention there is an option to disable engine start callouts.

That leaves the fuel lever as the only thing to address.

This new patch will provide the answer:

 

http://www.multicrewxp.com/Hotfix-McePmdg737-Edition.zip

Download, unzip and manually replace at least the 2 exe files. Others getiing the patch for the first time, also replace 2 files in \CandC\ folder.

No need for a new option.

FO will first leave it to you to open the fuel lever. If within 40 seconds of the start valve opening you didn't do it, he'll assume the user either expects him to open it or doesn't know how the engine is strated. He'll then open it once.

If you're facing a hotstart and shut the fuel lever, he shouldn't attempt to re-open it.

 

Quote

I'd also like to request the ability to turn of the 500' and 1000' call made by the FO since the plane's GPWS can do it automatically.

Now removed for this specific plane. New "thrust set" callout at 60 knots on takeoff added.

Since "stable" "unstable" recordings aren't there and would involve re-visiting 10 dlls to update them for each voice pack, like (foClive.dll), for now, when below 1000 feet above ground, if Fo isn't happy with any of these parameters, he'll suggest a go-around. Excessive pitch, excessive bank angle, excessive speed for landing., excessive rate of descent.

Lastly, is there an option for the FO to read the items listed on the recall panel? His side's items, i.e. AIR COND, DOORS, etc. When we do a "Recall Review" after an emergency or as part of normal operations, it can prompt an emergency checklist. For instance, if the AIR COND light is illuminated on the recall after it's been pressed or shows up as a master caution, he'll say "Air conditioning" or "Master caution, Air conditioning." I can then look up at the overhead and see what the problem is. Let's say it's an OFF SCHED DESCENT. I can then call for the Off Schedule Descent non normal checklist (which i'll create using the VoxScript), and he'll proceed to read/do the stuff in the book. After completing the checklist, I'll call for a "Recall review" again. If the item has been remedied, and there's no associated light, the recall will be blank, and he can then respond with "No Items." I hope that makes sense.

Yes, he should be able to for most items. He already reports "fuel config" and a few more. Just a matter of ensuring all lights are accounted for. and the ad-hoc audio is run. Next patch

I know this may seem annoying asking for all this stuff, but this is a great tool to train with. One of the biggest challenges when changing aircraft in the real world is learning the specific call-outs and responses. So hearing accurate phraseology is crucial as it can jog your memory if you forgot to do something.

It's OK. We've been fiddling with this for more than a decade and there is always something that needs a second take.

Thanks again for everything, and I apologize for being so nit-picky.

Feedback always welcome. Thank you for taking the time to report these.

.