Hello Bryan,I have a very annoying problem (the first and only one I´ve ever had with one of your products) wich drives me mad :I load the cold and dark panel state, do all the preflight stuff, do the departure brief, read the Pre-Flight checklist, call for "Before Start procedure", and read the "before start checklist", everything works perfect, FSCrew mode changes to "S.Crew/ENG START", so far so good now is when the trouble starts : I command "Start 4 and 3", but nothing happens, checking the green display confirms that the engine start commands are not recognized, not even the manual start commands "Start engine 4". The FO obviously does not continue his flows, so I start the engines myself and swap to "Before Taxi Mode" and command "Flaps 20" and there is no response /action either, so i set flaps manually and call for "before takeoff checklist", suddenly my first officer comes alive again and from there it works flawlessly.My speech-engine works almost 100 % accurate (after 4 training sessions).In fact there are no problems with the Level-D or even with the J41 Versions.After installing /uninstalling several times (hotfix applied)with Antivirus and firewall deactivated, this problem still goes on and i don´t know what else i could try ? Your help would be greatly appreciated.FS-Version :9.1OS : XP SP3PMDG-FS9 PAX and CARGO (fully updated)Headset : 1 normal and 1 USB-Logitech (tried both, with the same result)Let me know if you need any further detailsBest regardsLars Stahmann

Once the FO appears to stop responding, have you tried turning the voice engine off then back on again? ( I know...massive cliché!) Also you don't happen to be running a Creative USB soundcard do you? I saw something similar to this during testing but wrote it off as system specific as nobody else could reproduce the issue.

Once the FO appears to stop responding, have you tried turning the voice engine off then back on again? ( I know...massive cliché!) Also you don't happen to be running a Creative USB soundcard do you? I saw something similar to this during testing but wrote it off as system specific as nobody else could reproduce the issue.

Yes, i switched it off and on several times ( sorry forgot to mention)also the speech engine and microphone are perfectly configured, in fact as i mentioned the other Voice commander versions i own work great. NO, i have a simple Trust 5.1 soundcard.Btw, thanks for your answer.

Hi Lars,Please do this.Load the PMDG 747 and open the FS2Crew Main Panel.Don't do anything else at this point.Now just say "Start 4 and 3" using different inflections in your voice until you see it recognized in the green bar.I'm pretty sure this is just a pronunciation issue.Cheers,

Hi Lars,Please do this.Load the PMDG 747 and open the FS2Crew Main Panel.Don't do anything else at this point.Now just say "Start 4 and 3" using different inflections in your voice until you see it recognized in the green bar.I'm pretty sure this is just a pronunciation issue.Cheers,

Hi Bryan, thanks for your answer. I did what you suggested, but without success, in fact i just realised that there are only a few commands recognized . Just after that i fired up the Level-D version and did the same : believe it or not but every available voice command was perfectly recognized and displayed on the green bar. Do you have any clue on that ?RegardsLars Stahmann

Hi Brian I have the exact same problem as Lars with engine start and flaps.I also have the LDS and MD80 versions they work great no problems.Frank

Hi Frank and Lars,The speech recognition system used in the 747 is the exact same code as the system used in the Level-D and MD80.It's identical, so your situation is hard to explain, since, in theory, your results should be the same.I know on my machine and my beta testers machine's the results were the same across all versions of FS2Crew Voice Control.As a test, try turning off all ambient background noise from the PMDG 747 so you have total silence in the room except for your voice.Also ensure you print out the manual and use the PMDG 747 specific commands.Remember that the commands themselves are different from those used in the LDS 767 or Maddog version.Also, if using XP, make sure you check your mic sensitivity *after* the main FS2Crew panel loads.Cheers,

Hi Frank and Lars,The speech recognition system used in the 747 is the exact same code as the system used in the Level-D and MD80.It's identical, so your situation is hard to explain, since, in theory, your results should be the same.I know on my machine and my beta testers machine's the results were the same across all versions of FS2Crew Voice Control.As a test, try turning off all ambient background noise from the PMDG 747 so you have total silence in the room except for your voice.Also ensure you print out the manual and use the PMDG 747 specific commands.Remember that the commands themselves are different from those used in the LDS 767 or Maddog version.Also, if using XP, make sure you check your mic sensitivity *after* the main FS2Crew panel loads.Cheers,

Bryan,when i fly with voice commander, all Flight Simulator sounds come through my headset and the speakers turned off, precisely to avoid background noise.The only thing you can find in my computer-room are 2 PCs and both are so quiet that you can barely hear them. that´s the only noise in the room.The first thing i do after buying a new voice commander version is printing out the manuals, then i do 2 or 3 flights following the manual step by step, including all the preflight stuff untill i get used to it and this applies to all versions i own, needless to say that i know the specific voice commands for the different versions. Sorry for this explanation, but just want to make you see, that i do everything you recommend, in fact (and sorry to insist on that) all other versions work 100%.The "sensitivity-issue" is not an issue for me, as my settings are not altered after FSCrew starts.I followed that issue in the forum and i´m well aware of that.Well, nothing more to add from my part, i guessed the code was the same so the more dissapointing it is for me to see that this version doesn´t work for me. Will have to fly the Level-D instead.RegardsLars Stahmann

Bryan,when i fly with voice commander, all Flight Simulator sounds come through my headset and the speakers turned off, precisely to avoid background noise.The only thing you can find in my computer-room are 2 PCs and both are so quiet that you can barely hear them. that´s the only noise in the room.The first thing i do after buying a new voice commander version is printing out the manuals, then i do 2 or 3 flights following the manual step by step, including all the preflight stuff untill i get used to it and this applies to all versions i own, needless to say that i know the specific voice commands for the different versions. Sorry for this explanation, but just want to make you see, that i do everything you recommend, in fact (and sorry to insist on that) all other versions work 100%.The "sensitivity-issue" is not an issue for me, as my settings are not altered after FSCrew starts.I followed that issue in the forum and i´m well aware of that.Well, nothing more to add from my part, i guessed the code was the same so the more dissapointing it is for me to see that this version doesn´t work for me. Will have to fly the Level-D instead.RegardsLars Stahmann

Hello,I also have the same problem with the voice command for engine start and the flaps I have tried 5 flights, using the manual as a guidance, and also using my headset not to be unnoyed by noise. Mike sensitivity has been checked and recheckedI do not know what to do, and by the way I have an creative sound card, and also use other voice command product from FS2CREW.Cyrille de Lattre

Hi Lars and Cyril,The product has a fair number of users now, and there's no reason why it shouldn't work for you.Please email me at:admin ***at*** fs2crew.comWe'll do a Remote Desktop so I can see it first hand. But, as mentioned, if the 767 works for you then, then in theory the 747 should, too.However, I have theory I'd to test on your machine.Cheers,

Hi Bryan, I have exactly the same problem as those guys with engine start,also does not recognise LNAV VNAV or autopilot on,seems to recognise everything else,is it maybe an XP thing,or anything to do with the before start procedure or checklist flows,do they have to be run exactly as in the manual?...Bryan.

Hi Bryan, I have exactly the same problem as those guys with engine start,also does not recognise LNAV VNAV or autopilot on,seems to recognise everything else,is it maybe an XP thing,or anything to do with the before start procedure or checklist flows,do they have to be run exactly as in the manual?...Bryan.

Hi Bryan,Are you saying "Select LNAV" or "Select VNAV" or "Select Autopilot On".It needs to be said exactly like it's written in the manual.I'm investigating the engine start issue now... I think I may know what's causing it... hopefully I'm right. I'll know soon.Cheers,

UPDATE:With the help of Cyrille, I identified the issue!!!It affects only XP users, not Vista/Win 7 users.Problem was with the Grammar file.It's a very easy fix, and I'll release Version 1.2 in 24 hours.All the best,

UPDATE:With the help of Cyrille, I identified the issue!!!It affects only XP users, not Vista/Win 7 users.Problem was with the Grammar file.It's a very easy fix, and I'll release Version 1.2 in 24 hours.All the best,

I just came home from work and saw the post, so i can get my "Queen" out of the hangar for tomorrow ! Do you still need me to email you ? Sorry but i have no internet at work.Thanks to you and Cyrille for your great helpRegardsLars

I just came home from work and saw the post, so i can get my "Queen" out of the hangar for tomorrow ! Do you still need me to email you ? Sorry but i have no internet at work.Thanks to you and Cyrille for your great helpRegardsLars

No prob, the trick is in the grammar file, when you say "start 4 and 3", it should be written "start four and three", like for the 767 voice commander. So is for the flaps setting, and probably for the trim setting. This is for XP only, not for 7 and vista, Bryan pointed that pretty fast...Cyrille