Fantastic add-on for our loved NGX!However, I seem to have some issues (from the beginning):1. When we are going through the 'Before Start Checklist', a lot of elements are answered by 'Are you sure about that?' (i.e. Anticollision lights; they are actually on)2. I cannot contact ground for pushback. I used exactly the same method as shown in the updated manual (radio stack on Captain's side not the overhead as I was doing yesterday). The only he responds 'Go ahead' to is 'Ground from cockpit' (if I say 'Cockpit to ground' he doesn't respond), but then whichever of the pushback commands I use, nothing happens.3. Since the pushback didn't work, I ask the F/O to start engines (after announcing the starting sequence depending on whether air is connected) and he responds 'We're not properly configured for engine start'.4. When I taxi onto the runway and say 'Take-off' he says 'Transition altitude' and changes QNH to 'STD'5. When I roll on the runway, the 'V-speeds' he announces are lower than the ones set by FMC (he announces them before they are on the airspeed tape)6. Checklists after and including 'After Take-off Checklist' he goes through on his own (Maybe this is how it should be!)7. I cannot get the F/O to control the MCP. I say 'Set heading 130' but the heading doesn't change and nothing happens (the same with speed, vertical speed, altitude). When I say 'Select heading select' it engages heading select mode, but when I want to change the value in any of the MCP parameters, I cannot. I can change the COMM frequency using voice thoughThanks in advance

Hi,Very similar to my problems that i had before.Please look here for a possible solution:http://forum.avsim.net/topic/365698-set-heading/

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!

Fantastic add-on for our loved NGX!However, I seem to have some issues (from the beginning):1. When we are going through the 'Before Start Checklist', a lot of elements are answered by 'Are you sure about that?' (i.e. Anticollision lights; they are actually on)2. I cannot contact ground for pushback. I used exactly the same method as shown in the updated manual (radio stack on Captain's side not the overhead as I was doing yesterday). The only he responds 'Go ahead' to is 'Ground from cockpit' (if I say 'Cockpit to ground' he doesn't respond), but then whichever of the pushback commands I use, nothing happens.3. Since the pushback didn't work, I ask the F/O to start engines (after announcing the starting sequence depending on whether air is connected) and he responds 'We're not properly configured for engine start'.4. When I taxi onto the runway and say 'Take-off' he says 'Transition altitude' and changes QNH to 'STD'5. When I roll on the runway, the 'V-speeds' he announces are lower than the ones set by FMC (he announces them before they are on the airspeed tape)6. Checklists after and including 'After Take-off Checklist' he goes through on his own (Maybe this is how it should be!)7. I cannot get the F/O to control the MCP. I say 'Set heading 130' but the heading doesn't change and nothing happens (the same with speed, vertical speed, altitude). When I say 'Select heading select' it engages heading select mode, but when I want to change the value in any of the MCP parameters, I cannot. I can change the COMM frequency using voice thoughThanks in advance

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!

HI Guys,first off have a look at these two topics and they should fix most, it not all of your current issues,..http://forum.avsim.net/topic/365650-hot-fix-1-coming-all-read/http://forum.avsim.net/topic/365698-set-heading/

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!

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!

Do you have any external hardware installed ?VoXatc/fspax or any other addon software that makes entries to the panel config ?

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...

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...

Disable FS2Crew from the configuration shortcut on your desktop, you should have a check-mark on both button and voice, then enable voice only (should have an x)

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!

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!

Try next :1. Load FSX then NGX is not your default aircraft.2. Try ro Reinstall Fs2Crew.3.Open Fs2Crew inside FSX then you in 2D Panel in NGX.

Just an update....Hopefully this will also help some users...If you're having weird issues like the FO won't start the engines, etc, try using the "House PMDG Livery" when you load FSX.Another user from the Button forum had some weird issues.He was using a livery in the livery he found in the Avsim library called the "Bandit".When he switched to the PMDG House livery, the issues all of a sudden went away.When he tried using that "Bandit" livery again, his weird issues came back.So everyone try that: If having weird problems, try using the PMDG House Livery!Some of the 3rd party ones that are not officially endorsed by PMDG may be causing weird issues with NGX.

SOLVED!And now what I owe to the community:1. Uninstall FS2CREW2. Uninstall NGX (delete the NGX folder in FSX's PMDG folder and files in SimObjects)3. Restart your PC (I also used a freeware 'CC Cleaner' to clean the registries)4. Install NGX 800/900 then 600/700, then update each one of them with Service Pack B, and then again both of them with Service Pack C5. Install FS2CREW and enable the voice control6. Load onto a gate in a PMDG House livery and enjoy!All of my issues have been solved by simply reinstalling FS2CREW and NGX. It worked with no more issues in the PMDG House livery as well as in EasyJet's B737 from PMDG's website (I haven't tried any others yet, but I am sure they'll all work now). Be advised that perhaps not all of these steps have to be exactly the same, but this is just what helped me to solve my issues. Unfortunately my FSX has very explicitly asked me for a fresh reinstall by very nicely crashing to desktop at FL360, so reinstalling now (NOTHING TO DO WITH FS2CREW!; It just needs a reinstall every now and then); I'd have to do it before Cross The Pond anyway - the day when 737 stays in hangar and gives way to its bigger cousins.Thanks for your help and I hope that this will help at least one person who struggles.Regards

 

SOLVED!And now what I owe to the community:1. Uninstall FS2CREW2. Uninstall NGX (delete the NGX folder in FSX's PMDG folder and files in SimObjects)3. Restart your PC (I also used a freeware 'CC Cleaner' to clean the registries)4. Install NGX 800/900 then 600/700, then update each one of them with Service Pack B, and then again both of them with Service Pack C5. Install FS2CREW and enable the voice control6. Load onto a gate in a PMDG House livery and enjoy!All of my issues have been solved by simply reinstalling FS2CREW and NGX. It worked with no more issues in the PMDG House livery as well as in EasyJet's B737 from PMDG's website (I haven't tried any others yet, but I am sure they'll all work now). Be advised that perhaps not all of these steps have to be exactly the same, but this is just what helped me to solve my issues. Unfortunately my FSX has very explicitly asked me for a fresh reinstall by very nicely crashing to desktop at FL360, so reinstalling now (NOTHING TO DO WITH FS2CREW!; It just needs a reinstall every now and then); I'd have to do it before Cross The Pond anyway - the day when 737 stays in hangar and gives way to its bigger cousins.Thanks for your help and I hope that this will help at least one person who struggles.Regards

Glad you got it sorted ! Happy flying

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???

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?