Options command enables menus again

[ShaunX]

I always fly with the ‘Disable Menus’ option in Preferences selected, but have the "Options" command enabled. I then only call "options" if I need to execute mission specific F10 commands via "Take 10" etc.

 

What I've noticed however, is that once I've used the Options command once in a mission, menus then appear to have become enabled again, such that the menu pops up with relevent options during comms with an ATC for example.

 

Am I missing something ?

[MAXsenna]

I always fly with the ‘Disable Menus’ option in Preferences selected, but have the "Options" command enabled. I then only call "options" if I need to execute mission specific F10 commands via "Take 10" etc.
 
What I've noticed however, is that once I've used the Options command once in a mission, menus then appear to have become enabled again, such that the menu pops up with relevent options during comms with an ATC for example.
 
Am I missing something ?

I get this too, it seems things get a little out of sync. Not sure if it is a DCS or VAICOM thing, (or just me).
Was hauling some cargo in the border campaign yesterday, and I think what happened is that I somehow let go of the TX to early, and when I was trying to get the options menu back again, it was alternating between visible and not, even though I could hear the confirmation beeps. I sort of got it back on track by repeatedly "Take 12" commands.
Not sure if this is related or happened because of the "desync", but calling "inbound" to FARP got no respons from it, but as I tried repeatedly they got qued up, and suddenly they all went through and got responses. This I have seen before. The FARP came alive as I came around a hill, so LOS? Even the landing confirmation went through, too late though!

On a side note, recognition is getting better and better. "Otkrytka" gets recognised even if I don't have added it to the dictionary.
So I guess it's true that the more you use MS Speech Recognition, the better it gets.


Sent from my MAR-LX1A using Tapatalk

[ShaunX]

33 minutes ago, MAXsenna said:

I get this too, it seems things get a little out of sync. Not sure if it is a DCS or VAICOM thing, (or just me).
Was hauling some cargo in the border campaign yesterday, and I think what happened is that I somehow let go of the TX to early, and when I was trying to get the options menu back again, it was alternating between visible and not, even though I could hear the confirmation beeps. I sort of got it back on track by repeatedly "Take 12" commands.
Not sure if this is related or happened because of the "desync", but calling "inbound" to FARP got no respons from it, but as I tried repeatedly they got qued up, and suddenly they all went through and got responses. This I have seen before. The FARP came alive as I came around a hill, so LOS? Even the landing confirmation went through, too late though!

On a side note, recognition is getting better and better. "Otkrytka" gets recognised even if I don't have added it to the dictionary.
So I guess it's true that the more you use MS Speech Recognition, the better it gets.


Sent from my MAR-LX1A using Tapatalk
 

 

When I started using Viacom I was using TrackIR, headphones and a decent studio microphone. I spent hours training MS Speech rec to understand me, messed around with settings and mic levels (even tried the "recognise non-native accents" option) but couldn't achieve better than a 50% success rate in Viacom. I still have a Northern English (Geordie) accent (even though I haven't lived there for 30 years!) so I just assumed Microsoft (like much of the US) thinks everyone in England speaks English like the Queen

 

Then I got my Reverb G2, and a new build (so MS Speech untrained) and Viacom immediately started getting everything I say in the headset first time ! Doesn't make any sense but I'm not complaining