graves84

Thanks Damien- Working perfectly now!

Hello again-FS2Crew has been running FLAWLESSLY for me- your tech support has been top notch! My new "bug" was discovered when running RC4 and FS2C at the same time. All features for both programs work, but I'm noticing that when ATC is talking or another call sign, the volume drops to where I can't hear anything...just the chatter from RC4. The volume returns to normal settings when the chatter stops, or when I hit the "Q" button twice. I'm wondering if anyone else is experiencing this or has a fix...I've been resorting to the FSX ATC engine in the mean time, and everything has been running fine. You guys have an AWESOME product- I couldn't be happier with it... not to forget the support!

SP1C is like MAGIC! Worked perfect- thanks for the link! Awesome support all around, glad there's a fix with a great team behind it- thanks Bryan and Damien!

Bryan- since your email and my reply, I realized I only did b. Loading C now and should have my answer soon!

So after uninstalling FS2Crew, the NGX 600-900s (ran uninstall through PMDG's installer), then deleting PMDG files from simobjects folder, and running CC cleaner, I restarted my computer, and re-installed everything as recommended above. I started at the gate in the 900WL version, and selected the "Cold/Dark" state. From there, got through the before start procedure when things acted up again. The FO still said we weren't configured, and set the ALT to STD. Not sure where my hang up is coming from...any ideas?

Been away from my computer for a bit...I'm re-installing everything as suggested...when looking at PMDG's Service Pack updates, I can only find 1b. Is 1c part of it or should I be looking elsewhere???

I never had button mode enabled...but I confirmed there was a check. Then confirmed Voice was enabled. Tried doing this and restarting computer. No luck. I'm still experiencing the same 6 problems I mentioned above... I've tried the EXT AIR start and found the same issue where the FO says we're not configured. Confused, but I know there's a fix out there somewhere!

Hardware is Saitek X65F and Saitek Pro Flight Rudder Pedals. I also use Track IR5 with hat clip.I have RADAR Contact 4.3 and FS Build version 2.4. FS build allows me to create a flight plan and put it in as a coded or company route. I've tried inputting a flight plan without FSB and still have issues...

Thanks for the quick reply! Still having problems though....1) During my Pre-Flight checklist, the FO sets the altimeters to STD. He also does this during my REP when I call "takeoff."2) I've set my cockpit to the 2D default setting as recommended in your first link. Still having same problems. The FO is getting through his checks and when I call "Start Engine ____," he goes through the flows and stops after turning the packs off, and says "We're not configured for engine start." This is using the APU for start option- I have not tried it with the EXT AIR start yet...Since my FO won't start the engines, I have to run his before taxi flows (first part). I've been then switching to "Select TO Flaps" and the FO does fine after that...3) Still no luck with the ground crew. It only recognizes "Ground from cockpit," and no other commands. Using the exact syntax and getting proper green bar with proper phrases. Panels set properly, and tried both methods in manual... No luck.4) When doing the Before Start CL, I get to the CDU Preflight challenge and the FO always comes back saying "you might want to check that." I'm setting it up per the PMDG tutorials and selecting the TAKEOFF REF page as prescribed in step 2 of the Before Start/ Captain flows. 5) The MCP. The FO will recognize: VNAV, LNAV, HDG Select, FLT LVL CHG, and CMD A or B prompts. (Want to reiterate to others reading that when you call for the AP to be turned on, your controls must be neutral.) When trying to change a heading, speed, course, or altitude, I'm using the exact required phrase per the FS2C manual, getting the green bar and confirming it matches exactly what I say, and I'm still be ignored by my FO:-/6) Still having random calls with the V Speeds on TO roll. The FO seems to call them as they appear from the top of my HUD, rather than when I'm actually passing through them...Other than these quirks- FSCrew2 has made the best plane in flight simulation even better. Best product support I've ever had!

dodos9-I'm having the exact same issues as you- Getting a hold of the ground crew has been a real challenge. Even after running my speech training and going through all of the commands. I use AES, and have tried it with and without it selected on the FS2C panel. Same thing- only responds to "ground from cockpit." If I try the other ways to say it, I get the green bar with the correct instructions, but no response. I've tried both methods explained in the manual. I've also found that during the FO's pre flight flow, he is not testing the TCAS. No biggy to me- but I'm curious if I missed something or if there's a glitch.I get the "are you sure" when the FO asks for the CDU pre-flight. Following the PMDG tutorials, I'm pretty sure that it's complete! He changes my altimeters to STD after running the Before Start Procedure. I'm very puzzled why he thinks we're not configured for start as well...I've been starting them after that point, and manually selecting the "Flaps" option. From there, it's been fine getting to the runway. I have not found issues with the REP call- I have noticed the FO does not extend the retractable landing lights, so I've been doing that. His speed calls have been occurring early for me as well. After take-off, it's fairly smooth sailing...except for the MCP troubles, I haven't come across any other glitch. I get the green bar with proper instructions for altitude, speed, heading and radio freq. changes- but nothing happens. I don't experience any of these issues with my iFly737 or PMDG 747. Hoping there will be a hot fix soon!