June 7, 201510 yr Good to hear, I had much better results once I ran through the speech recognition program another time Chris Smith
June 7, 201510 yr Author Good to hear, I had much better results once I ran through the speech recognition program another time I ran through the speech reongnition a couple of times, but correcting the errors did it for me. The flight today was perfect, no problems at all from start to finish..
June 8, 201510 yr Commercial Member I ran through the speech reongnition a couple of times, but correcting the errors did it for me. The flight today was perfect, no problems at all from start to finish Perfect! B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
June 8, 201510 yr Author Spoke too soon, my co pilot starting dropping the ball right after gear up. He never selected NAV, kept questioning IAS 185 "with are you sure," and never did any of his climb checklist to the line functions, which I had to do. Could this be because I was over 1,000 feet before I had a chance to say "Flaps 0, SET IAS 185, climb checklist to the line"?
June 8, 201510 yr Author One more problem, several times I have called for flaps 5 at the appropriate time, and the co pilot responds with "flaps 5" but never moves the flaps lever. Am I supposed to move it myself?
June 8, 201510 yr That is very odd. I don't fly the Q400 but never, ever had this issue with the NGX. Do you ever see an SDK error? Chris Smith
June 9, 201510 yr Commercial Member One more problem, several times I have called for flaps 5 at the appropriate time, and the co pilot responds with "flaps 5" but never moves the flaps lever. Am I supposed to move it myself? No, the FO is supposed to do it. Make sure you're not using any external hardware that can override the FO. Do you see the words "FAIL" on the FS2Crew Main Panel? By the sounds of it you do. If so, you don't have the latest version of the MJC Dash 8 installed on your computer. You'll need to download the latest version. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
June 9, 201510 yr Author No, the FO is supposed to do it. Make sure you're not using any external hardware that can override the FO. Do you see the words "FAIL" on the FS2Crew Main Panel? By the sounds of it you do. If so, you don't have the latest version of the MJC Dash 8 installed on your computer. You'll need to download the latest version. I have the latest version of the Q400 and never see any " Fail" error. . I have most of the problems sorted out, but not all Whenever I read the altimeter setting, I always get " are you sure" multiple times. I just use skip now when that happens. Despite adding words to the dictionary both on and arm, and pronouncing "arm" Rrm , with the R exaggerated, it would still think I said "on". I finally edited arm in the dictionary and spelled it out letter by letter A-R-M so instead of saying arm when it is called for I just spell a-r-m and it inserts arm into FS2Crew correctly. I will work on this some more today.
June 9, 201510 yr Are you commanding "FLAPS 0, I A S ONE EIGHTY FIVE, CLIMB CHECKLIST TO THE LINE". after to FO has announced "ACCELERATION" based on the MDA bug set during the pre-flight?
June 9, 201510 yr Author Are you commanding "FLAPS 0, I A S ONE EIGHTY FIVE, CLIMB CHECKLIST TO THE LINE". after to FO has announced "ACCELERATION" based on the MDA bug set during the pre-flight? I may have jumped the gun on issuing that command and did it before the acceleration prompt. I tried it early this morning, waited for the "acceleration" prompt and everything worked.
June 9, 201510 yr From the manual... After passing the acceleration altitude, speak in as a single phrase: "FLAPS 0, I A S ONE EIGHTY FIVE, CLIMB CHECKLIST TO THE LINE". There is a tutorial flight, if you didn't know http://www.support.fs2crew.com/help/manuals/default.aspx#pageid=flows4 Sounds like you have most of your issues worked out though Chris Smith
June 9, 201510 yr Author From the manual... After passing the acceleration altitude, speak in as a single phrase: "FLAPS 0, I A S ONE EIGHTY FIVE, CLIMB CHECKLIST TO THE LINE". There is a tutorial flight, if you didn't know http://www.support.fs2crew.com/help/manuals/default.aspx#pageid=flows4 Sounds like you have most of your issues worked out though Yes I did the tutorial flight dozens of times, and am finding out that most of the problems I have had were with the speech recognition misspelling the words that I say. I found out what I think is the last one today, "select nav" not working on takeoff. I went to the Cockpit voice recorder log in FS2 Crew and saw that when I said " select nav" it spelled nav as nhave instead of nav. That is why the co pilot ignored the command. I added the two words "select nav" in the dictionary for voice recognition as one word, and now it gets it right every time.
June 10, 201510 yr Author Ok, I probably have spent in the last week over 40 hours working with this program, and the problems I am having are directly attributable to the windows speech recognition For instance, no matter what I do , including using the dictionary in speech recognition, I cannot get the program to recognize crosscheck. It gives me coarse. crosse, krause, etc, but not crosscheck. That is the reason that it keeps making me repeat the altimeter setting until I finally give up and say skip. So what I decided to do is to go into the dictionary in the Speech recognition program, and there you can add a word like crosscheck. It then gives you a chance to record it, but when I record it I say a totally different sounding word, in this case "altimeter" Now you also have to block that word in the dictionary from being used which is simple, you just spell altimeter, and say Prevent this word from being used. . Now when I say "altimeter", instead of spelling out altimeter, it spells "crosscheck" in notepad which is the way I can check to see if it is working. For "Select Nav" , the other response I had a major problem with, I used the word "navigate" . So I went to the dictionary, put a new word in "Nav select" and when it asked me to record it, I said " navigate". Now everytime I say Navigate, it spells out "sel nav" . So now when I want to select Nav in the autopilot I just say " Navigate" You just have to remember the substitute word you are using to take the place of the problematic work that speech recog is having a problem with. And you also have to make sure that the substitute word is blocked from being used in the " Prevent a word from being dictated " menu in the Speech Recog dictionary. Hope that makes sense.
June 10, 201510 yr Commercial Member It gives me coarse. crosse, krause, etc, but not crosscheck. It's not possible for FS2Crew to give you "krause" or "crosse" because those words are not in FS2Crew speech list of possible words. For "Cross Check" you need to say "Set Cross Check".... don't forget the 'set' part. B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
June 10, 201510 yr Author It's not possible for FS2Crew to give you "krause" or "crosse" because those words are not in FS2Crew speech list of possible words. For "Cross Check" you need to say "Set Cross Check".... don't forget the 'set' part. Exactly, and the way I say it is 2992set, crosscheck, or now 2992set, altimeter.
Create an account or sign in to comment