I'm hoping that we will get these very helpful and informative 'titbits' from the FS++ team on a fairly regular basis. When they arrive I will post them here.

 

So here's the first titbit direct from the FS++ Team......thanks Guys

 

 

To get the best out of the virtual co-pilot:

 

 

Do not hesitate to bombard your co-pilot with requests.

 

He will let you know when you're asking too much.

 

For instance when there are 2 requests to dial 2 different things, he will proceed with the first one, queue the second one in his head (which will be executed when he's done with the first). He won't take a third request for dialling as this isn't humanely possible. He can still reply to you or execute the odd command all while performing a time consuming task like a scripted flow.

 

In general for all tasks involving dialling...

 

You can ask FO to modify or cancel on the fly

 

Example:

 

You say "set heading two fifty"

FO starts dialling

You realise you meant 350

Just say "correction 350"

FO knows what item you're referring to (heading, speed, altitude, DH, VHF, NAV, ADF etc...).

Correcting on the fly is valid as long as the FO is still dialling. When he's done you'll need a new voice command

 

Equally, you can cancel on the fly. Say

 

"cancel this"

"cancel that"

"ignore this"

"ignore that"

"stop this"

"stop that"

"what are you doing"

...

... many other variations

 

FO will then reset heading, altitude, speed or whatever to original value.

 

All critical actions have safeguards against spurious commands.

 

FO won't just jump on the IRS switches in the middle of the Atlantic just because the microphone picked-up "IRS off"

 

There will always be request for confirmation before proceeding with such drastic actions.

 

Regarding script flows.

 

You can either have the FO comment on everything he does with the option "Verbose" (in Voxscript) ticked, or do all the actions silently with option un-ticked.

 

Script flows that involve drastic actions like engine shutdown are better secured with a mandatory request for confirmation.

 

With all the measures above in place, you should relax in the knowledge that the occasional mis-recognition won't lead to mayhem.

 

FS++ Team

Here's the next useful titbit of information direct from the FS++ team...thanks Guys.

 

This is especially for Dan :Nerd: who asked the question in the forum earlier

 

Here is a complete list of possible voice commands just for the engine generators

 

First the simple ones, and just for GEN 1

 

"connect generator engine one"

 

"switch on generator engine one"

 

"turn on generator engine one"

 

"switch on generator engine one"

 

"Activate generator engine one"

 

"generator engine number one connect"

 

"generator engine number one switch on"

 

"generator engine number one turn on"

 

"generator engine number one set to on"

 

 

"generator engine number one Activate"

 

"generator engine number one on"

 

"generator engine one connect"

 

"generator engine one switch on"

 

"generator engine one turn on"

 

"generator engine one set to on"

 

 

"generator engine one Activate"

 

"generator engine one on"

 

"Set generator switch engine number one on"

"Select generator switch engine number one on"

"Switch generator engine number one on"

 

"Set generator switch engine one on"

"Select generator switch engine one on"

"Switch generator engine one on"

 

"generator switch engine number one turn on"

 

 

"generator switch engine number one turn on"

"generator switch engine number one on"

 

"engine number one generator switch turn on"

 

"engine number one generator switch on"

 

"engine number one generator select on"

 

"engine number one generator activate"

 

"engine one generator switch turn on"

 

"engine one generator switch on"

 

"engine one generator select on"

 

"engine one generator activate"

 

... I could go on and on with at least another 60 variations. You can also add "please" at the end of each sentence.

 

 

We don't expect our users to memorise these (that would be scary).

 

We rather do our best to identify all possible variations (as per real world crew operation) to enable the user to speak naturally. What we expect from users is familiarity with aircraft systems.

 

It takes many years to get these grammars right. Bear in mind that the commands above are just for one item. And to allow thousands of commands to live in harmony (to make them different enough for the speech engine to make successful recognitions, all while sticking to real world operation) is a challenge on its own.

 

 

 

The FS++ team

Just noticed I got a mention :-) Useful info :Peace:

Another useful piece of information:

 

The mce.ini inside MCE installation folder should never be edited. It serves as backup in case the one in |AppData\Roaming\ folder gets messed up. When you select "Restore factory settings", the ini in installation folder will overwrite the other one with the default settings, which work for the majority of users.(FS++ Team)

Having problems with running over the MCE mechanic when using GSX/AES

 

Then here is an answer that will help with the hospital bills!

 

Look for the [MECHANIC] section in mce.ini, and option PushWithGSXandAES. If missing, you can add them.

 

set things as follows

 

[MECHANIC]

PushWithGSXandAES=1

 

When ready for pushback, ask mechanic "ground are you ready for pushback?", he will then hand you over to GSX mechanic and will say goodbye immediately.

Can someone tell me how we are supposed to download new versions of the software now that they have changed the website?

1 hour ago, Grand_Pubah said:

Can someone tell me how we are supposed to download new versions of the software now that they have changed the website?

As indicated on webpage, request Demo by sending mail to [email protected] and specify the simulator used.

If you happen to be a registered user, you'll be given a permanent link

 

 

I dont know if this is the right place to ask this.

I downloaded the latest patch, but I use MSFS and cant figure where to place the contents of the scripts folder.

Thanks.

You copy the scripts to their respective folders.

The actual scripts you are using are stored under

 

My Documents\Multi Crew Experience\Myvoicescripts\Copilot\Aircraft\Aerosoft CRJ\ folder for the CRJ

and

 

My Documents\Multi Crew Experience\Myvoicescripts\Copilot\Aircraft\Asobo_A320_NEO\ folder for the ASOBO and FlyByWire mod

 

Once you put the dat file in, in most recent MCE versions, when you click <Command> button, you'll see a list box showing many of the available commands for the relevant plane, so you can easily make custom scripts, without looking up the potential commands in documentation.

Gerald R

The FS++ team

36 minutes ago, Burge said:

You copy the scripts to their respective folders.

 

 

The actual scripts you are using are stored under

 

 

 

My Documents\Multi Crew Experience\Myvoicescripts\Copilot\Aircraft\Aerosoft CRJ\ folder for the CRJ

 

 

and

 

 

 

My Documents\Multi Crew Experience\Myvoicescripts\Copilot\Aircraft\Asobo_A320_NEO\ folder for the ASOBO and FlyByWire mod

 

 

 

Once you put the dat file in, in most recent MCE versions, when you click <Command> button, you'll see a list box showing many of the available commands for the relevant plane, so you can easily make custom scripts, without looking up the potential commands in documentation.

 

 

Gerald R

 

The FS++ team

 

Thanks for that, I didn't realize I had MCE files under 'My Documents'.

I managed to install and all seems well.

 

Robin.

How do we know when to update mce

1 hour ago, Burge said:

How do we know when to update mce

Version is displayed on website: