team

 

i have an annoying little problem ... as it is my preferred phrasing to say "speed / heading / track <***>" on my ngx.

 

all works fine except when i say "speed 2 1 0" for example, the copilot intereprets "speed to 1 0".

 

saying for example "speed 1 9 0" or track "2 1 0" is no problem.

 

there seems no command phrasing "speed to" which might be the clash ... as listed in the various command files.

 

saying "2 1 0 speed" is okay, but any phrase with "2" after "speed" is a problem - eg "airspeed 2 1 0".

 

so, any help on this would be welocome.

Hi there...

 

Yes i agree it is a bit annoying, but unfortunately that's how it is in the real world as well... I got taught to make a pause after "speed to" so my "audience" would know when the command finished and when the actual value starts.

 

I had not thought about changing the phrase to "210 speed" on MCE, great idea!! Love how we are not restricted to repeating the same commands like parrots and we can have a few options.

thanks will

 

i had tried pausing but with inconsistent success.

 

i remain a tad flustered but won't surrender yet... given i prefer to say all in the same sequence & to say the control first is for me an intuitive / logical / non confusing thing to do.

 

the curious thing is that during mce's wizard, there is a check phrase "set speed two four zero" which i pass !!

Have you tried 'set speed 2 ten'

 

Also I found if you turn the speech speed' up a little that helps. It's on the general tab, I think. That helped a lot for me, especially if you speak slightly faster than normal!

alpha117

 

thanks & will try your suggestions ... i had tried "speed 2 ten" to no avail !!

My way of dealing with this was saying speed to tooooo (long two) toooooo zero. It is not perfect, but works usually.

thanks bart ... will try.

 

i am finding eg "210 speed" always works, much to my frustration !!

 

i am hoping that mce's trainer may over time help with my preferences.

 

i am still curious why for example "heading 2.." is not a problem but "speed 2.." is.

 

maybe a comment from FS++ would enlighten.

thanks bart ... will try.

 

i am finding eg "210 speed" always works, much to my frustration !!

 

i am hoping that mce's trainer may over time help with my preferences.

 

i am still curious why for example "heading 2.." is not a problem but "speed 2.." is.

 

maybe a comment from FS++ would enlighten.

 

Agree this is annoying.

 

What happened is that last year we added, "set to" as another variation mainly to accommodate some fs2crew users who were used to saying it that way.

 

Because we have to support both "set speed to 240" and "set speed 240", and since the spoken "to" can be seen as "2" it leads to misunderstandings.

 

I think we will remove the "set to" variation in next build.

 

Users who absolutely want that variation will have to obtain a replacement grammar file, which will allow "set to". But they'll have to say it that way for every request.

 

There is no problem with “heading 240” because the grammar doesn’t allow “set heading to 240”, only “set heading 240”. Same for altitude.

 

Just a reminder, taken from the documentation, all these variations are available. That was before we added the "set to" which with hindsight wasn't a good idea.

 

 

· <THE_SPEED> on the speed

· <THE_SPEED> on the speed bug

· <THE_SPEED> on the airspeed

· <THE_SPEED> on the airspeed bug

· <THE_SPEED> speed

· <THE_SPEED> on the speed

· <THE_SPEED> speed bug

· <THE_SPEED> on the speed bug

· <THE_SPEED> airspeed

· <THE_SPEED> on the airspeed

· <THE_SPEED> airspeed bug

· <THE_SPEED> on the airspeed bug

· Set <THE_SPEED> speed

· Set <THE_SPEED> on the speed

· Set <THE_SPEED> speed bug

· Set <THE_SPEED> on the speed bug

· Set <THE_SPEED> airspeed

· Set <THE_SPEED> on the airspeed

· Set <THE_SPEED> airspeed bug

· Set <THE_SPEED> on the airspeed bug

· Select <THE_SPEED> speed

· Select <THE_SPEED> on the speed

· Select <THE_SPEED> speed bug

· Select <THE_SPEED> on the speed bug

· Select <THE_SPEED> airspeed

· Select <THE_SPEED> on the airspeed

· Select <THE_SPEED> airspeed bug

· Select <THE_SPEED> on the airspeed bug

· Adjust <THE_SPEED> speed

· Adjust <THE_SPEED> on the speed

· Adjust <THE_SPEED> speed bug

· Adjust <THE_SPEED> on the speed bug

· Adjust <THE_SPEED> airspeed

· Adjust <THE_SPEED> on the airspeed

· Adjust <THE_SPEED> airspeed bug

· Adjust <THE_SPEED> on the airspeed bug

· Airspeed <THE_SPEED>

· Airspeed bug <THE_SPEED>

· Airspeed bug set <THE_SPEED>

· Airspeed set <THE_SPEED>

· Speed <THE_SPEED>

· Speed bug <THE_SPEED>

· Make the Speed <THE_SPEED>

· Make the Speed bug <THE_SPEED>

· Speed bug set <THE_SPEED>

· Speed set <THE_SPEED>

· Set Airspeed <THE_SPEED>

· Set Airspeed bug <THE_SPEED>

· Set Speed <THE_SPEED>

· Set Speed bug <THE_SPEED>

· Select Airspeed <THE_SPEED>

· Select Airspeed bug <THE_SPEED>

· Select Speed <THE_SPEED>

· Select Speed bug <THE_SPEED>

· Adjust Airspeed <THE_SPEED>

· Adjust Airspeed bug <THE_SPEED>

· Adjust Speed <THE_SPEED>

· Adjust Speed bug <THE_SPEED>

· Adjust the Airspeed <THE_SPEED>

· Adjust the Airspeed bug <THE_SPEED>

· Adjust the Speed <THE_SPEED>

· Adjust the Speed bug <THE_SPEED>

· Make the Airspeed <THE_SPEED>

· Make the Airspeed bug <THE_SPEED>

· Make the Speed <THE_SPEED>

· Make the Speed bug <THE_SPEED>

 

Because changing grammar files doesn’t involve compiling exe or dll files, anyone who sees this as an issue can request the relevant grammar file as of today.

 

Just mention your preference.. I mean whether you’re always using the “set speed to 240” form or the “set speed 240” without the “to" in the middle.

 

Cheers.

gerald

 

such good news & service heartens my blurry soul this early sunday morning.

 

i certainly put my hand up for a "without to" file ....will you add it to the forum ??

 

as an interesting aside, i did find the "issue" occurs less / almost gone when i disabled "show commands in FS".

 

again thanks

Hi John

 

The files will not be added to the forum, due to the fact that these files keep changing as more and more voice commands (or variations) are added.

 

Just drop the FS++ team an e-mail and they will send you the file that you want

 

 

Clive

a note to thank FS++ for the revised files - for "without to" - which work a treat.