Well, after much trying and frustration I have given up on FS2C for now. I have followed all suggestions on uninstalling/reinstalling PMDG and FS2C and still cannot get it to work properly. Wont detect window heat, pmps, seatbelts, cdu preflight complete or beacon all being accurate. Any command for the MCP (speed, alt etc) causes the chosen item to run away and I have to stop it with Cancel Last Command. Cannot contact ground crew (yes, I'm setting it up right). Ground crew will respond to "Ground from Cockpit" but not "Cockpit to Ground". Even tho it will answer Ground from Cockpit it will not go any further. Any call for engine start results in a Not configured for engine start from the FO. During landing when descent checklist FO claims the CDU is not set up. Choosing Flaps 30 in the briefing panel and in the CDU will not set up FS2C to land at flaps 30. Calling 30, Green Light will not trigger a reponse from the FO. Landing altitude is always spoken by FO as zero regardless of what I set. I am not a new user to FS2C so I am not a newbie with it. BTW, the green bar shows that all the proper words are being detected correctly. Anyone got any suggestions? For now I am going to disable my FS2C. Thanx.-Rick

Hi Rick,Are you 100 percent positive you have SP1C installed from the PMDG forum?The majority of the problems users experienced over the last week were the result of people only having SP1B installed.SP1C is only available in the PMDG forum as of now.That will clear up most of your issues.MCP Speed values: Remember to use the correct syntax. Sound out each number in full. Ie., "Set Speed Two Two Zero".Do not say "Set Speed Two Twenty"Make sure you run the voice training.Cockpit to ground: You're Audio Control Panel is probably not set up right. There are numerous threads on this. Simplest way is just to press "FLT" on the Captain's Audio Control Panel.Other stuff: You need to say "Flaps 30 Green Light".

It is surprising how many people dont have the SP1c update, even the ones that THOUGHT they had it. I read posts where people updated thinking it converted to the newest SP, only to find out that for some odd reason it was still SP1b. Check the "about" button in the FMC for the version. Also, I had my speakers turned up just a tad to much on one flight, and the FO went crazy with all my commands. I literally reduced volume one notch and it cleared everything up.However, I still cant get pushback no matter what. The ground crew responds with "All hatches and doors closed, bypass inserted, release parking brakes please", I release the brakes and nothing ever happens after that. Still trying to figure that one out, its got to be a flow error on my part somehow.

However, I still cant get pushback no matter what. The ground crew responds with "All hatches and doors closed, bypass inserted, release parking brakes please", I release the brakes and nothing ever happens after that. Still trying to figure that one out, its got to be a flow error on my part somehow.

Did you say "brakes released" ?

BWAHAHAHAHA! :( NO! :( How could I have missed that in like, oh I dont know, 30 tries! I think that will clear up my last problem. Off to test.Thanks Andreas

<sigh> I knew I'd get that response. :-) Info right out of the aircraft.cfg for the -600/700/////////////////////////////////////////////////////////////// PMDG 737NGx// // Current with Build: 1.00.3219///////////////////////////////////////////////////////and for the -800/900/////////////////////////////////////////////////////////////// PMDG 737NGx// // Current with Build: 1.00.3219///////////////////////////////////////////////////////so yes, I'm running 1c. As for wording, I have 3 or 4 other FS2C voice products and I know how to word things. They all work just fine. Why would I need to run the voice recognition again when I run the other FS2C voice products that work flawlessly? It's Windoze voice recognition I believe not FS2C recognition, right? And the green bar shows the proper phrases, like I said in my msg. As for voice control panel, I set Intercom ON in the rear overhead where the IRS switches are, speaker volume up and make sure the SVC light is lit. Like I said in my msg ground will respond "go ahead" to ground from cockpit but not cockpit to ground. Using the FLT results in the same. I've installed with admin rights. I'm fairly computer savvy (been in them for 25 yrs and I'm a programmer) so I understand software. Running Windoze 7 64bit, 8gig ram, Intel I7 quad. Kinda at a loss right now on this one....-Rick

Hi Rick,The voice control system in the NGX is the same as the one used in the other FS2Crew voice products. We still using Microsoft's Speech Recognition API (SAPI).So your results should be consistent across the board.I'm not sure why "cockpit to ground" is not registering for you. It works for me.Check your PM's. I'll help you via a Remote Deskstop so I can "see" the issue.Cheers,

email sent

woo hoo! After some time and help from Bryan we got it going. For those of you that are experiencing the same problems I mentioned above, try reinstalling FS2C without uninstalling it. Then active the panel updates. It seemed to work for me. Mileage may vary by state to state and country to country. :-) Thanx goes off to Bryan for being willing to help me out! Off to play!-Rick

woo hoo! After some time and help from Bryan we got it going. For those of you that are experiencing the same problems I mentioned above, try reinstalling FS2C without uninstalling it. Then active the panel updates. It seemed to work for me. Mileage may vary by state to state and country to country. :-) Thanx goes off to Bryan for being willing to help me out! Off to play!-Rick

Yes, Rick and I got sorted.Everyone... if you have SP1C installed, and the FO is still acting strange, re-install FS2Crew.Why re-installing works, I can't explain. But it worked for Big Rick so it might work for you, too.Cheers,