Hi guys,

 

I'm running voice control version 1.5 in P3D with the 737NGX, win8 64bit. Everything works fine during the first phase of the flight, pre-flight, start-up, taxi, takeoff, and climb is perfect. However, some time during the cruise phase the copilot usually stops recognising/hearing what I say. There is no green text on the top of the screen, and no command is executed.

 

I can get out of this by toggling fs2crew off and on using the left most of the four main buttons on the fs2crew panel. When toggling off the flight simulator usually hangs between five and 30 seconds before I get a green message saying it has been disabled. Turning it on again works without a hitch and recognition is restored. But not for long. Within a few minutes I am in the same situation again and have to repeat the procedure.

 

I am guessing that the problem might be related to window speech recognition freezing up in some way, but I am not sure, and I have no idea of how to debug it. It might be triggered by the copilot not recognising some command, either because of background noise or that I just give the wrong command at the wrong time. This is not confirmed from my side yet. And, since it works perfectly for the first half, and then freezes frequently the second half, I hardly think this is the problem.

 

Any ideas?

Real name please...

 

PM me with if you don't want it displayed.

No way to edit the post?

 

Frank Olaf Sem-Jacobsen

Hi Frank,

 

That's a weird one I haven't seen before.

 

Happens everytime?

 

I have Win 8 64, too, so that's not the issue.

 

Try this:

 

1. Make a flight in Africa away from all the 3rd party scenery, etc.

 

2. When in Cruise, turn on "Hard Mute".

 

Maybe your mic is really sensitive and it's constantly picking up background noise and you're overloading it? Hard to guess.

Hi, thanks for your suggestions.

 

I did some digging around, and it turned out that window speech recognition was starting with Windows start-up, and I had some problems with my soft muted key when talking to ATC which might have confused it. I fixed these two issues, and the next flight went smoothly. There was not a single hiccup.

 

Full of joy and anticipation I just did another flight, and this time it cut out again right before descent, approximately at the same time it usually does. Again, by turning things on and off I was able to get him back. I also noticed that he appeared to run correctly since I heard some of the background descent announcements from the flight crew.

 

I did not reboot the PC in between the flights, could this be a reason? Since I had done the previous flights a day before window speech recognition would probably already be running, so is this the same problem as booting with it on? I have no idea, I'm just thinking aloud.

Hard to guess.... generally you should not need to reboot your PC between flights.

 

But just ensure "Window Speech Recognition" is check off as per the manual.

 

You do not want it running.

I did exactly that. It is not starting at boot, and it does not seem to be running.

Good.

 

Also, turn down your LOD (Level of Detail) in FSX a bit. Some people have it set way too high.

 

I don't know if that's a factor, but it's worth a shot.

Really? It is at 5.5 already, don't really want to put it lower. My guess is still that WSR fails in some way since fs2crew still works... What is happening with the WSR connection when I turn voice off and on from the fs2crew panel?

What's WSR?

Windows speech recognition

Windows Speech Recognition is separate from FS2Crew.

 

The main reason it needs to be off is because when you speak, it may pick up commands that are intended to control Windows itself, such as "close window", which naturally you don't want to happen.

So where does fs2crew get its speech rec. from? And why would it stop working until I cycle it off and on?

Just another wild guess. What is the purpose of the symbol in the upper left corner of the window that indicate the phase it is currently in? the symbol changes between something like . and = for no apparent reason...

FS2Crew uses Speech Recogntion API from Microsoft.

 

The symbol you're referring to is the "HARD MUTE" symbol (or it may also be the the 'your're in descent mode' indication).

 

Please check the manual for more info.

 

Are you sure you don't have HARD MUTE on?

 

I still can't explain your issue.

 

How far away is your mic from your speakers?