Hi I realize the potential of voice commander for the 767, but I'm just not actualizing it.Install went smooth. I have the 1.2 version. Installed the SAPI engine. I did the mike callibration- it's ok.Panel config lines are as the manual shows. Loaded fs9, placed 767 in Denver,ticked off all the options required by manual. Imported the panel state.FS2Crew main panel appears ok, have VOICE and DSP ticked.Configuration panel pops up ok. I program the fmc to the point of COMPLETE.Now the snags appear.Examples:1. In the old button version, fs2crew would start by clicking on the clock. Now it's done from the config panel. The manual says the pre-flight events is optional. However, the only I way I figured how to get fs2crew running is by pressing the RUNPF button, and then pressing the FF buttn to start the clock. If I don't want preflight events, how do I start the clock to run? It seems to stand still.2. I have tried using both mike/speakers and headset options. But my voice is recognized with a delay. Sometimes my voice will be recognized after a minute or more, sometimes not at all. This disrupts the natural flow of things until things come to a halt. BTW all the fuel slps, weight disribution etc,come in on time. My room is quiet so it's not environmental problems.3. Briefing for the departure. In the old version there was a window which showed the stages of briefing. Now what am I supposed to say. I can't find any script to read from.That's as far as I got. I know I'll get through eventually. I just need to know why these snags are happening.Eytan OrnsteinMS Windows XP Home SP3Intel Core 2 CPU 4400 at 2.0 GHZ2GB RAM DDR3GeForce 9800 GT"Twin Monitors- Samsung 19" Syncmaster 931BF and Mag21"Thrustmaster T flight HOTAS XFS2004.

Hi I realize the potential of voice commander for the 767, but I'm just not actualizing it.Install went smooth. I have the 1.2 version. Installed the SAPI engine. I did the mike callibration- it's ok.Panel config lines are as the manual shows. Loaded fs9, placed 767 in Denver,ticked off all the options required by manual. Imported the panel state.FS2Crew main panel appears ok, have VOICE and DSP ticked.Configuration panel pops up ok. I program the fmc to the point of COMPLETE.Now the snags appear.Examples:1. In the old button version, fs2crew would start by clicking on the clock. Now it's done from the config panel. The manual says the pre-flight events is optional. However, the only I way I figured how to get fs2crew running is by pressing the RUNPF button, and then pressing the FF buttn to start the clock. If I don't want preflight events, how do I start the clock to run? It seems to stand still.2. I have tried using both mike/speakers and headset options. But my voice is recognized with a delay. Sometimes my voice will be recognized after a minute or more, sometimes not at all. This disrupts the natural flow of things until things come to a halt. BTW all the fuel slps, weight disribution etc,come in on time. My room is quiet so it's not environmental problems.3. Briefing for the departure. In the old version there was a window which showed the stages of briefing. Now what am I supposed to say. I can't find any script to read from.That's as far as I got. I know I'll get through eventually. I just need to know why these snags are happening.Eytan OrnsteinMS Windows XP Home SP3Intel Core 2 CPU 4400 at 2.0 GHZ2GB RAM DDR3GeForce 9800 GT"Twin Monitors- Samsung 19" Syncmaster 931BF and Mag21"Thrustmaster T flight HOTAS XFS2004

Hi Eytan,First, the "old" button 767 version is very different from the "voice" 767 version. So throw all your old preconceived ideas about the old 767 version out the window when using the new 'voice version'. The SOPs used between the two products are fairly similar, but that's about the only similarity.Clock: The timer is only used or needed if you want to run the Pre-Flight events. Unlike the old 767 version, you do not need to 'start' FS2Crew by pressing any buttons. Running the Pre-Flight Events routine is purely optional. You do not need to start the 'clock'. Only start the clock if you want to do the Pre-Flight events. I suspect most users actually just skip it.Voice recognized with a delay: I never heard of that one before, so all I can do is guess: Check your mic sensitivity. Make sure it's not muted. Watch what's detected in the Green bar so you can see what the speech recognition engine hears. You ran the Voice Training I assume?Briefings: Since this is a voice product, you have to make the briefings now. Well, you don't have to, but some hard-core types will do it. Let me know about the voice recognition issue... that's the only real issue I see here.Cheers,

Hi Eytan,Clock: The timer is only used or needed if you want to run the Pre-Flight events. Unlike the old 767 version, you do not need to 'start' FS2Crew by pressing any buttons. Running the Pre-Flight Events routine is purely optional. You do not need to start the 'clock'. Only start the clock if you want to do the Pre-Flight events. I suspect most users actually just skip it.You ran the Voice Training I assume?Let me know about the voice recognition issue... that's the only real issue I see here.Cheers,

1. So the way to start fs2crew is just to say anything, like "any snags", and the clock will start running?2.By voice recognition you mean the control panel- sounds speech audio devices- speech properties- speech recognition- configure microphone?Eytan

1. So the way to start fs2crew is just to say anything, like "any snags", and the clock will start running?

No. If you want to run the Pre-flight events, you click on a button in the fs2crew configuration panel (right click on the VSI to open the panel).But, you don't have to run them. They are optional. You can just ask for the before start checklist straight away after starting fs2crew.

1. So the way to start fs2crew is just to say anything, like "any snags", and the clock will start running?2.By voice recognition you mean the control panel- sounds speech audio devices- speech properties- speech recognition- configure microphone?Eytan

Hi Eytan,1. Just print out the tutorial and follow it to the letter.2. Yes.Cheers,

The first thing I did is check the mike callibration, It detected my words and played them back. Great so far.Then I printed out the manual, ran fs9 with the 767 with the appropriate panel setings, and ran into the same problems.Well, If I can handle the complex ATR fs2crew procedure, then I'm optimistic about the 767 LOL.Page 26: "+45 Jetway connects (FSX only"), so it doesn't apply to me as I have fs9. So no point in saying "any snags with the plane", right?So I assume the next step will do the trick- the "requesting zero fuel weight" as this is not fs version dependent. Is this right?Nevertheless when I say that phrase my voice is not recognized.I did another trial run 5 hours ago. My voice was not recognized(tried many phrases). Minimized fs9 and went out. Came back later, maximized fs9. Lo and behold, suddenly all the phrases I had said hours ago ran in dozens of green text lines down the screen.So I am at a loss now.Eytan

Hi Eytan:1. You can still say "any snags with the plane" in FS9.2. "Requesting zero fuel weight"... make sure you have set Comm Radio 2 to the required frequency listed in the manual. 3. Last item: Weird one. I suspect maybe your FS window was 'out of focus' when you were making the commands... then when you put the FS window back in focus all the commands hit all at once. See if that's it.Let me know about #3... I'm curious about that.Cheers,

Ok. Same as before with fs9 loaded, 767 up with panel state, etc, etc. Good.Main panel opens up, config panel opens up. One thing I get right away is that the clock is only related to the pre-flight procedure.I start with saying "request zero fuel weight" and get an answer. Hooray!Then no load sheet comes on as promised. Also green text strips appear randomly indicating words that I had just supposedly uttered. But I never said anything!Words like- tons/ checked/on appear on the text.So maybe my mike is picking up noises triggering the text lines?This time I am using a headset. Mike is 5cms.from my lips. I callibrated it with both the SAPI and the Sound manager utilities with 'acoustic echo cancellation' and ' noise suppresion' ticked. Playback of my voice recordings was very clear, no echos.I usually run fs9 in windowed mode so I can undock sub panels and place them on my second monitor. I tried running it in full mode. All these trials produced the same results, i.e. fs2crew indicating words I'd neve said.I am a native English speaker, so word articulation isn't a problemEytan

Eytan, did you go through the voice training steps before you started using FS2Crew? (Bryan asked about this above, but I don't see your answer). This is a prerequisite for being able to use the voice recognition software successfully.If you have done this, how well does voice recognition work with other applications on your PC, e.g. dictation into notepad? (The procedure is described here: http://www.microsoft.com/windowsxp/using/setup/expert/moskowitz_02september23.mspx)

Eytan, check your mic volume sensitivity in the Windows Speech Recognition Panel. It might be too high. Remember if using XP to check *after* the FS2Crew Main Panel has loaded. The speech recognition can pick up all sorts of noises... coughs... yawns, etc.So don't be shocked if you see words you didn't say appear in the Green Bar. Thing to note is that FS2Crew was designed not to act on every word the speech recognition engine "hears".... It's context driven.Loadsheet should pop up. The time it should pop up is listed in the manual.Cheers,

I did the mike test from here-control panel- sounds speech audio devices- speech properties- speech recognition- configure microphone.The configuration is fine.IO also tested at - Sounds and Audio Devices-Voice- Test Hardware, and it was fine.The link to microsoft is old as it talks about SP1. So their tutorials shows windows that are different than mine.So I don't know what I can improve at my end.Maybe my mike is TOO sensitive, how do I lower that?Eytan

Hi There,p.12 of the manual ..... try turning the microphone 'level' right down

Hi There,p.12 of the manual ..... try turning the microphone 'level' right down

Agreed, try turning it down even more.Even better solution is to upgrade to Win 7.Win 7/ Vista have a higher version of SAPI than XP, and Win 7 is better all round.Cheers,

Ok, I give up!I tried all kinds of mike settings but nothing worked for me. I don't blame the software, as it's something faulty at my end.I uninstalled Voice Commander via the the programs-fs2crew2010-uninstall, which went ok. Prior to that, on the configuration utility I clicked the 'restore panel cfg etc...'. Also I deleted the fs2crew 2010 folder in the fs9 root directory as instructed.I thought the uninstall would have rolled back the settings to the original fs2crew for the 767. But upon reloading fs9 and the 767 tutorial flight KSFO=KLAX, the master panel made a no show. So I am back to the 767 without any fs2crew capabilities.I still have the original fs2crew LevelD 767 setup.exe, so I reinstalled it. But still no sign of the master panel. Ugh!How do I get my original situation back?Eytan

Ok, I give up!I tried all kinds of mike settings but nothing worked for me. I don't blame the software, as it's something faulty at my end.I uninstalled Voice Commander via the the programs-fs2crew2010-uninstall, which went ok. Prior to that, on the configuration utility I clicked the 'restore panel cfg etc...'. Also I deleted the fs2crew 2010 folder in the fs9 root directory as instructed.I thought the uninstall would have rolled back the settings to the original fs2crew for the 767. But upon reloading fs9 and the 767 tutorial flight KSFO=KLAX, the master panel made a no show. So I am back to the 767 without any fs2crew capabilities.I still have the original fs2crew LevelD 767 setup.exe, so I reinstalled it. But still no sign of the master panel. Ugh!How do I get my original situation back?Eytan

Hello Etyan,Did you print out the manual and read it word by word?When you re-installed the old 'button' 767 version, did you run the Level-D 767 Config Manager (not the FS2Crew one) and click "Save".That's a necessary step.Best,