I have FS2Crew for B737 Wilco.I'm flying now and command "heading 270" has been given. But programm understood it like "heading 470" and now heading selection just rotating without stop because it trying reach hdg 470.And I know that if I'll stop spech engine (to stop hdg bug rotation) I'll lost voice of copilot.Could you please fix it?

I have FS2Crew for B737 Wilco.I'm flying now and command "heading 270" has been given. But programm understood it like "heading 470" and now heading selection just rotating without stop because it trying reach hdg 470.And I know that if I'll stop spech engine (to stop hdg bug rotation) I'll lost voice of copilot.Could you please fix it?

Make sure you say heading two seven zero clearly and distinctly.In the 767 version I learned some new techniques that I will port over to the 737 to ensure the system cannot attempt to "act" a heading like 470.FYI, you can turn VOICE back on after you turn it off to stop a runaway.Best,

Thanks Bryan. Waiting for fix.But I'm sure I gave normal command :) And how system can identify TWO like FOUR....What about "push to talk" button? The "mute" button unusable because if speech engine will hear some noise from TV or from something else (I always have problemm with thrim sound like "shhh shhh shhh" and speech engine ident it like "Off"). Please do "push to talk" function ;) I gave you my money :)

I can't reproduce the '2' being interpreted as '4'What's your accent?Are you using XP?

Actually I don't know what's my accent (I'm from Belarus), but "2" (I think) always prononce like "too" ;)Yes, XP.Probably I told you before.. it's could be better if when captain says some command like "heading 240" then copilot have to repeat command "heading 240" and captain have to confirm like "checked" or "yes"... something like this. So if copilot will receive "yes" then he will execute command, if "No" or "Negative" then he will do nothing or will say "Sorry?" ;)Waiting for "push to talk" button :) hehe

Actually I don't know what's my accent (I'm from Belarus), but "2" (I think) always prononce like "too" ;)Yes, XP.Probably I told you before.. it's could be better if when captain says some command like "heading 240" then copilot have to repeat command "heading 240" and captain have to confirm like "checked" or "yes"... something like this. So if copilot will receive "yes" then he will execute command, if "No" or "Negative" then he will do nothing or will say "Sorry?" ;)Waiting for "push to talk" button :) hehe

Hi,I sent you a PM. I compiled a new version of the gauge for you so that if the speech recognition system somehow hears heading 420 it won't act the command.Please contact me for the gauge.Also, since you're using XP, be sure to check your Voice Volume on the Windows Speech Recognition panel *after* you load the FS2Crew Main Panel. It may have been reset to full volume.Cheers,

Regading volume (recording level) - everything's ok, it's not change (I understand what you mean).I'll check gauge.

Thank you Bryan. That gauge help and hdg not accept commands more than 360 deg any more.But push to talk button still require ;)

Hi,actually the same thing happened to me. I didn't command any heading commands, so it mustbe some swedish which have sounded likeheading >360 degrees.It also seems that this occupies F/O and hewas not able to set flaps or execute any other commands.Checklist were still running but no commands.I tried to command heading below 360 likeheading 180, 240 etc, but it didn't help.RegardsMatts Falck

Hi Matts,Be sure to check your microphone 'sensitivity'. If you get into a "stuck" situation, just click the VOICE button once (to turn off the Speech Engine). The sim will pause for a second. Then turn Voice back on.Cheers,

Oki, thanks/Matts

Hi,Last week I had exactly the same issue with the 400, causing me to manually fly from FL360 to landing :( I understand there is a fix for this? (other then resetting the voice engine)Egbert

I tells that better if copilot will repeat lestened command immediatly and then will execute after your confirmation like "yes" or "check" ;) but nobody whants listen me :Whistle:But gauge received from Bryan helped with this hdg trouble. Thx Bryan.and... what else... Sounds. Yes.. some sounds has not same (equal) level. They not normalized I think... I would like to help fix it with CoolEdit programm but sounds not in normal wav format unfortunatelly

Hi,Last week I had exactly the same issue with the 400, causing me to manually fly from FL360 to landing :( I understand there is a fix for this? (other then resetting the voice engine)Egbert

Hi Egbert,It's not a fix per se because it's not broken. It's a change to the gauge file I made so that if the speech recognition accidentally hears a value greater than 360, it won't act on it.Email me for the updated gauge.Cheers,

I tells that better if copilot will repeat lestened command immediatly and then will execute after your confirmation like "yes" or "check" ;) but nobody whants listen me :Whistle:But gauge received from Bryan helped with this hdg trouble. Thx Bryan.and... what else... Sounds. Yes.. some sounds has not same (equal) level. They not normalized I think... I would like to help fix it with CoolEdit programm but sounds not in normal wav format unfortunatelly

Hi Albert,1. Confirming commands... neat idea, but most users I suspect wouldn't like it.2. Sounds: The FS2Crew audio engine uses stereo sound to simulate sound coming from different positions. Perhaps the 'imbalance' that you're hearing can be attributed to that.Cheers,