Hi,

 

This isn't a huge problem, but with my installation of FS2Crew Voice (SP1) for the NGX, I cannot make the F/O recognize my reading off takeoff speeds during the before start checklist. I notice via the green bar that my voice commands are being input properly; I see "V one one two zero", "V R one three four, and "V two one four zero", etc, being correctly interpreted on the green bar. I also pause for a second between takeoff speed read outs as specified in the user manual. After reading off the V 2 speed, however, the F/O never responds. I've tried pausing longer and shorter during call outs, but there is still no response after the V2 callout. Again, my voice commands are being correctly interpreted on the green bar.

 

I am also certain that FS2Crew is in the correct mode, i.e., the "before start checklist mode", during this time. I am only reading off Takeoff speeds when prompted by the F/O.

 

Strangely, during my voice read outs for the MCP settings during the before start checklist, everything goes perfectly. Here too one must pause between read outs, but for whatever reason it works quite well for the V 2, Heading, and Altitude read outs during the MCP part of the before start checklist. I only have trouble with the takeoff speed callouts.

 

Thank you,

 

John Thomas

Hi John,

 

The problem is that "Altitude" needs to come last, not V2.

 

Altitude XXX is the trigger, not V2.

 

 

 

FO: MCP:

 

CAPT: V2 ONE FOUR ZERO … {pause for a second}... HEADING TWO TWO ZERO… {pause for a second}… ALTITUDE ONE TWO THOUSAND

 

Note: You’re reading V2, Heading and Altitude as they’re dialed in on the MCP.

Bryan, I think John's question regarded the takeoff speeds, not the MCP response. The MCP works fine for me but I have the same problem as John in that V1, Vr, and V2 don't seem to be recognized although the green bar shows the proper response. I generally just followup with "set" to proceed with the checklist.

 

Another question...it appears that I have to set the FO's altimeter mode from in hg (my default) to Hpa if I'm flying outside the US. Is this correct?

 

Aside from the takeoff speed issue (minor) everything has worked flawlessly since SP1 ... a really great product! I comend you for the excellent followup to user questions and overall customer support. Thanks.

 

Richard Johnson

Are you guys using XP or Win 7?

 

 

I think I may know what it is

 

Check you PMs.

 

That is correct on the FO's altimeters.

 

I'll change that in V1.2. so you don't have to do that for him.

Bryan, I think John's question regarded the takeoff speeds, not the MCP response.

 

Yes, just the takeoff speeds portion of the before start checklist is where I'm experiencing the problem. The MCP portion of the before start checklist works fine.

 

Bryan, I'm using Win 7 Ultimate 64 bit.

 

Thanks,

 

John Thomas

John,

 

PM me with your email address.

 

We'll see if V1.2 helps your situation.

 

Cheers,

Bryan,

 

I'm also using win7/64 bit.

 

Thanks,

 

Richard Johnson

Same here Bryan. Win7x64 ultimate.

Eric.

I just upgraded this in V1.2, which I'll probably release in a day or so.

 

Cheers,

Great. Thanks Brian.

 

One other minor thing I've noticed is that when the FO is ready for the approach checklist, if any command is recognized as "set" (even if I cough into the mike) I get approch checklist complete despite not calling for the checklist. Don't know if this is my issue or a slight bug.

 

Thanks in advance.

 

Richard

Hi Richard,

 

That's possible. If the mode says "Approach" and you say "set" (or 'set' is somehow heard by the system), the FO will be triggered to say "Approach Checklist Complete".

 

I'll eliminate that possibility in V1.2 so you must call for the approach checklist first no matter what.

 

 

Cheers,

Thanks! What a great world it would be if everyone responded with your kind of customer service.

 

Richard