Having really enjoyed the FS2Crew for the PMDG JS4100, I thought I would go back and try the PMDG 737NG version (SP1.1).All basically works great except for a couple of items :-VNAV and LNAV will not switch on - the Green bar and FO both confirm my command but the switch is not turned on. I have rechecked the PMDG 737NG Key assignments and they are both correct, MCP Press VNAV Ctrl+Shft+J and MCP Press VNAV Ctrl+Shft+J. At the time I am hand flying with the AP off, all other switches appear to work fine.VREF quite low - the FMS shows Vref of 146kts at Gross Wt 140.0, but FO gives Vref of 135kts. Could FS2Crew be geeting the wrong Gross Wt from somewhere ?Glen

Having really enjoyed the FS2Crew for the PMDG JS4100, I thought I would go back and try the PMDG 737NG version (SP1.1).All basically works great except for a couple of items :-VNAV and LNAV will not switch on - the Green bar and FO both confirm my command but the switch is not turned on. I have rechecked the PMDG 737NG Key assignments and they are both correct, MCP Press VNAV Ctrl+Shft+J and MCP Press VNAV Ctrl+Shft+J. At the time I am hand flying with the AP off, all other switches appear to work fine.VREF quite low - the FMS shows Vref of 146kts at Gross Wt 140.0, but FO gives Vref of 135kts. Could FS2Crew be geeting the wrong Gross Wt from somewhere ?Glen

Hi Glen,There's no SDK for the old PMDG 737, so we can't read much info directly.VREF is FS2Crew's guesstimate. We can't read the exact figure out of the FMC.For VNAV and LNAV... double check the assignments match those required by FS2Crew as listed in the manual.Also try engaging VNAV/LNAV manually. The aircraft may not have been configured properly to accept an LNAV/VNAV engagement in the first place.Cheers,

BryanMany thanks for such a quick response :( Regarding the Vref, I thought that may be the case, just checking I wasn't doing anything wrong.The Vnav and Lnav is a different story I know these should work. The key assignment details above in my first post are from the FS2Crew Ops manual version 1.1. I have double checked them against the PMDG 737NG 'key assignment' menu within FS2004 and they are correct. When I call for LNAV at about 500 ft I get the correct response from the FO, but the switch stays off until I click it - it then goes on immediately. Same thing happens with the VNAV after flaps up - both click on OK ??Apart from rechecking the key assignments which I have done, I suppose there is nothing else I can do ?Glen

BryanMany thanks for such a quick response :( Regarding the Vref, I thought that may be the case, just checking I wasn't doing anything wrong.The Vnav and Lnav is a different story I know these should work. The key assignment details above in my first post are from the FS2Crew Ops manual version 1.1. I have double checked them against the PMDG 737NG 'key assignment' menu within FS2004 and they are correct. When I call for LNAV at about 500 ft I get the correct response from the FO, but the switch stays off until I click it - it then goes on immediately. Same thing happens with the VNAV after flaps up - both click on OK ??Apart from rechecking the key assignments which I have done, I suppose there is nothing else I can do ?Glen

Hi Glen,Could something be intercepting the keypress FS2Crew sends to the aircraft?If, for example, you have the Squawbox text entry window "in focus", it will intercept the keypress FS2Crew sends to activate LNAV/VNAV, etc.Other than that, it should work.Best,