Hi All, I'm having good success with voice recognition, but I'm experiencing a possible bug. When I call "start engine one" the FO turns the engine start switch right to CONT. If I call again he turns it further to the right (FLT). I have to select GND with the mouse. When I call "start engine two" he turns that one correctly to the left (GND). Anybody else have this issue? Thank you, Greg D.

Hi All, I'm having good success with voice recognition, but I'm experiencing a possible bug. When I call "start engine one" the FO turns the engine start switch right to CONT. If I call again he turns it further to the right (FLT). I have to select GND with the mouse. When I call "start engine two" he turns that one correctly to the left (GND). Anybody else have this issue? Thank you, Greg D.

I didn't have this issue when I was trying to get my first flight done earlier.

I didn't have this issue when I was trying to get my first flight done earlier.

We never experienced that during beta testing.However, because we're using simulated mouse clicks, sometimes your screen resolution can affect the ability of the FO to accurately place his simulated mouse click on the pop-up mini panel.Here's something to try:We're going to make the mini pop-up panel a bit bigger for you.Do this:1. Open the panel.cfg file for your PMDG 700 and 800 models.2. Find WINDOW 19. It will be near the bottom.[Window19]file=737NG_Overhead_Background_1280.bmpfile_1024=737NG_Overhead_Background_1280.bmpsize_mm=1280,960window_size_ratio=1.0position=8visible=0ident=1002window_size=0.200, 0.200 <---- WE'LL CHANGE THIS LINE!Change the highlighted line to:window_size = 0.400, 0.400That will make the mini-panel for the overhead panel bigger, and reduce the liklihood of the FO's simulated mouse click missing its mark.Let me know if that little mod works for you.Best,

Let me know if that little mod works for you.

Worked great! I actually prefer the larger window too. It helps me keep an eye on what this guy is doing. Now I need to better understand the interaction with the FO/MCP/AUTOPILOT. My latest flight was 100% through "gear-up". Once I call "set climb thrust" and "set flaps up speed", I get a reply, but no noticeable input on the N1 or MCP from the F/O? Is he just reading back what he recognizes or is he supposed to be adjusting? When I call for "autopilot on" who is supposed to turn it on?I read the section about autopilot and voice control and I thought I understood, but I cannot get the FO to adjust any setting on the MCP while autopilot is still off, even though voice is recognized.Thank you for your awesome customer support! Best Christmas gift to myself in a long time!Lovin' it,Greg D.

Glad you're loving it. Do help spread the word.As for your issues, double check that your keyboard assignments match up with the list.That'll solve it right there. And make sure nothing could be intercepting the keypresses FS2Crew sends, such as having another window in focus that accepts text input.Best,