September 10, 201015 yr Gday Bryan,First off thanks for the awesome product.I got it a couple of days ago and after a couple of voice training sessions it was all working fairly well for the first flight. However during preflight of my second flight which started positively, FS2Crew slowly stopped recognising what i was saying to the point at which during engine start it would not recognise any word at all and i could not get the FO to start the other engine. I proceeded without FS2Crew and then ran some training sessions in the cruise, and it started to work a little better, so i did some more however then the issue worsened again and now it wont recognise any of the flap calls and most autopilot calls except vnav, lnav and Hdg Hld. I have been fiddling with the sensitivity settings to try and get it going but it doesnt make a difference. I also deselected the "background adaption" option in the voice settings as i suspect this may have caused its loss of calibration. I have no idea where to go from here.I run XP and i have a Creative Fatality headset so i dont think thats the problem. Im aussie though, would that make a difference?Thanks,Tom
September 10, 201015 yr Think i may have fixed it, it all just started working on descent, had to fiddle around with the profiles through cause it didnt realise we were in the cruise. But yeh all worked well in the end. False alarm :)Cheers
September 11, 201015 yr Commercial Member Think i may have fixed it, it all just started working on descent, had to fiddle around with the profiles through cause it didnt realise we were in the cruise. But yeh all worked well in the end. False alarm :)CheersGlad you got it sorted.Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 12, 201015 yr Or not. Next flight i did it wont recognise one word i say. Cant even get it going with the first "any snags with the plane". Is there some secret to the voice recognition. Does it not work with XP very well or is it my accent. I might have to downgrade back to the button version :(
September 12, 201015 yr Okay so i reinstalled Fs2crew, starts okay after running about 5 voice training sessions, then slowly gets worse until it really is unusable as you can repeat yourself 10 times and sometimes it will eventually recognise what you say, which is not viable for commands like gear up and thinks that need to be done immediately. Iv tried fiddling with the sensitivity and what not. I dont really understand, is it XP? Can i have no background noise at all? (I have tried, improves results marginally) The green bar will continuously pick up words like "auto" and "on" instead of sentence commands. I dont really know what to do from here. Any advice would be appreciated, at the moment it seems like its forgetting all the voice training i did after every restart and during every flight. Is it supposed to be working consistently or is this normal?Sorry if i seem agitated, its just disappointing that i cant get it to work now, despite the fact that my first flight was fine..Tom
September 12, 201015 yr Commercial Member Hi Tom,If the first flight was fine, you must have done something different on the subsequent flights.Code generally doesn't degenerate over time by itself.I'd start by double checking your microphone settings/ audio drivers.XP is no problem as many of the users use XP.Be sure to re-check your mic sensitivity "after" you load the FS2Crew Main Panel. "After" is important.Try turning it down way low.Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 13, 201015 yr Hmm okay. I have gone over the mic settings thoroughly. So can you just confirm for me that a lower sensitivity setting and a lower volume is better? Also could you just describe the settings i should be making in terms of the command accuracy and response time (the second setting bar)?One of the issues im having is that instead of it recognising the phrase commands like "Are you ready for the departure breif'" or "Were ready for the pushback and engine start", it recognises single words like "auto". Or sometimes it recognises nothing at all, particularly frustrating when im trying to drop the gear or control the flaps during departure and approach. During cruise i can get most of the commands to work well however the recognition falls during departure and approach.Finally, should i have my speaker volume competely muted? I have a pretty good sound system so i enjoy having the external volume going as well as the headset especially during takeoff as the sub adds a lots of atmosphere, but is a prerequisite for the use of this software for all external sound to be muted?Thanks for all your support, im really keen to get it working consistently as the product has a hell of potential :)Cheers,Tom
September 13, 201015 yr Commercial Member Hi Tom,You should be getting recognition results well over 90 percent.What kind of mic do you have?Stand-alone microphone or USB headset?Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 13, 201015 yr I use a fairly top range headset (Creative Fatality 1 Gaming Headset) however it is not USB, it has two sound card jacks one for the mic and one for the headphones. Would this make a difference? I know you can purchase adapters so convert the headset jacks into USB, should i snag one of them? Cheers
September 13, 201015 yr Commercial Member I use a fairly top range headset (Creative Fatality 1 Gaming Headset) however it is not USB, it has two sound card jacks one for the mic and one for the headphones. Would this make a difference? I know you can purchase adapters so convert the headset jacks into USB, should i snag one of them? CheersYou could try it, but I doubt it would make much difference.If you want to spend money on something, it's time to dump XP and upgrade to Windows 7.Windows 7/Vista ships with a higher version of the SAPI speech recognition engine than XP.As mentioned, assuming your system is operational, there's no reason you shouldn't be getting over 90 percent plus accuracy results.Your situation is hard to trouble shoot because you said everything went well on your first flight, and things degraded from there...That suggests either you're not following procedures (I'd try running the tutorial flight again to the letter to ensure you're doing things in the expected way) or your system is dieing.Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 13, 201015 yr Success! I made sure i dropped the mic volume after opening the panel and i got great results in the last flight, and that was with background noise! I dont doubt that W7 would yeild even better results so ill defiently look into upgrading. Nah the systems fine, i keep tabs on its health pretty well.One question though, on final, for some reason it didnt switch to landing mode so i switched it manually, which was no problem, i was just wondering what is the trigger for the landing mode?CheersTom
September 13, 201015 yr Commercial Member Success! I made sure i dropped the mic volume after opening the panel and i got great results in the last flight, and that was with background noise! I dont doubt that W7 would yeild even better results so ill defiently look into upgrading. Nah the systems fine, i keep tabs on its health pretty well.One question though, on final, for some reason it didnt switch to landing mode so i switched it manually, which was no problem, i was just wondering what is the trigger for the landing mode?CheersTomHi Tom,Glad you got it sorted.Regarding setting the mic volume lower "after" you open the FS2Crew main panel... that's an XP only thing. If you upgrade to Win 7, you won't need to do that.Landing mode: Not sure, you may have forgotten to respond to the last checklist item in the Approach checklist.Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
September 14, 201015 yr Okay well ill keep you posted on how it goes. Yeah iv been considering upgrading to W7 for a while now as there are a lot of advantages for the setup im running, particularly the FTX scenery that i use, ill have to give it some thought. Thanks again for the quick support :)Cheers mate,Tom
September 14, 201015 yr Okay well ill keep you posted on how it goes. Yeah iv been considering upgrading to W7 for a while now as there are a lot of advantages for the setup im running, particularly the FTX scenery that i use, ill have to give it some thought. Thanks again for the quick support :)Cheers mate,TomHi Tom,I have to reduce my mic volume to get great results on XP64. If you watch the mic volume when you first display the FS2Crew main panel, you will notice it jumps up to nearly maximum. Its not an FS2Crew problem, its the SAPI engine in XP.I use a tool that can automate the process of setting the mic volume, called nopey. You can get it here: http://nsis.sourcefo...em_setting_toolTo use it, create a directory called nopey and extract the program into it. Then open a command prompt and go into the nopey directory. e.g. cd\nopey and enter the following:nopey info sndtreethis will then display a list of your sound devices with its identifier. You can then create a text file using notepad called micvol.bat in the nopey directory (make sure no .txt extention is added to it) and enter into it the following:nopey.exe volume <id>=<value>where <id> equals your sound device and <value> is a number from 0 to 65536 which represents the voume to set the device to. E.g. to set it to 75% the value would be 65535*0.75 which equals 49151e.g.nopey.exe volume 14=49151You can create a shortcut to the batch file on your desktop and as soon as you have displayed the FS2Crew panel, just click on the shortcut and your mic volume is instantly set. Saves alot of messing about in the long run - more time for flying Best wishesSteve Stephen Munn
September 14, 201015 yr Commercial Member Hi Tom,I have to reduce my mic volume to get great results on XP64. If you watch the mic volume when you first display the FS2Crew main panel, you will notice it jumps up to nearly maximum. Its not an FS2Crew problem, its the SAPI engine in XP.I use a tool that can automate the process of setting the mic volume, called nopey. You can get it here: http://nsis.sourcefo...em_setting_toolTo use it, create a directory called nopey and extract the program into it. Then open a command prompt and go into the nopey directory. e.g. cd\nopey and enter the following:nopey info sndtreethis will then display a list of your sound devices with its identifier. You can then create a text file using notepad called micvol.bat in the nopey directory (make sure no .txt extention is added to it) and enter into it the following:nopey.exe volume <id>=<value>where <id> equals your sound device and <value> is a number from 0 to 65536 which represents the voume to set the device to. E.g. to set it to 75% the value would be 65535*0.75 which equals 49151e.g.nopey.exe volume 14=49151You can create a shortcut to the batch file on your desktop and as soon as you have displayed the FS2Crew panel, just click on the shortcut and your mic volume is instantly set. Saves alot of messing about in the long run - more time for flying Best wishesSteveFantastic find, Steve!Thanks for sharing that! I'm going to add that to the manuals.Still, people should be upgrading to Win 7... XP is ancient!Cheers, B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
Create an account or sign in to comment