Hello Guys!First of all, i am enthusiast flying the PMDG 737, a very outstanding panel/airplane.I have been flying this panel for more 1 month and half, and i have installed last patch, SU1-1.After installing this upgrade, i discovered that:1 - If i activate VNAV just after takeoff (when i am still below 1000 feet), everything runs ok and the whole flight will'be regular.2 - Instead, when i activate VNAV during climb (i.e. above 4000 ft or more) i get unable to activate VANV and the message "CHECK MCP ALTITUDE" appears on the FMS' scratchpad.At this point, i wonder: what's the correct procedure to use VNAV during a flight?Thanks in advance for your help!

Yup, I get the same thing. I did a search here, but couldn't find any reference to this.Mike F.

>Yup, I get the same thing. I did a search here, but couldn't>find any reference to this.>>Mike F.When you're in a climb, you need to make sure that the altitude set in the MCP altitude window is higher or equal to the altitude that VNAV will be trying to attain.Thus, if you're at 4000 climbing but your MCP altitude window is set to 4000 or lower, VNAV will not engage.Additionally, if you've already climbed higher than a constraint in your flight plan when you try to engage VNAV, it will not engage.so if you're on course to a waypoint with a 3000' constraint, and you're at 4000, you need to remove the constraint before you select VNAV.

>Thus, if you're at 4000 climbing but your MCP altitude window>is set to 4000 or lower, VNAV will not engage.....>so if you're on course to a waypoint with a 3000' constraint,>and you're at 4000, you need to remove the constraint before>you select VNAV.Thanks for your suggestions, but it stills goes bad and "CHECK MPC ALT" appears on the scratchpad :(

>Thanks for your suggestions, but it stills goes bad and "CHECK>MPC ALT" appears on the scratchpad :(So where is your MCP altitude set at this point? Higher then the actual altitude? If not do so!

>>Thanks for your suggestions, but it stills goes bad and>"CHECK>>MPC ALT" appears on the scratchpad :(>>So where is your MCP altitude set at this point? Higher then>the actual altitude?Affirmative, my MCP ALT was set to 35000, and constraint at TOP was 290/120.I start thinking VNAV is still bugged.

Heo!Can you paste a screenshot showing your MCP and FMC LEGS or PROG page.Regards, Nejc

>Can you paste a screenshot showing your MCP and FMC LEGS or>PROG page.Hi Nejc!!!!!Here's some pics about my takeoff from LIMF for LIMF-LIRN, FL 350:The takeoff:Again takeoff:Just After takeoff:Climbing for departure TOP5A:Selecting VNAV:

HiNicolaI just tested your flight with my Maschine, worked fine for meI took some shots as well but I am not able to make ti smaller so I cannot post them. I will try to comment to your screenshots anywhay:No 1 looks fine so far, as one can assume a V1 speed shown in the PFD I assume that you did hat preflight work till it said "preflight complete" On the ND You have the rose mode active, If you

>Hi>Nicola>and the VORLOC Button is selected Whys that??Hi,I selected VORLOC because TOP5A departure: to perform this DP, i have to intercept radial 168 inb TOP VOR. For speeds, in the pictures i forgot to set climb speed, anyway i have just tried again,but always same error.I give up :(

Same problem here. I did a flight recently from KSAN to KOAK. The flight plan entered into the FMC was KSAN LNSAY2.FALCC SLI LAX RZS J501 BSR.HADLY2 cruising at FL350. Departed rwy 27 as per the SID and MCP altitude was set to 4000. I flew the a/c to the OCN 155 radial via the heading and speed hold control and up to 4000 using v/s. As soon as I leveled off at 4000 for the altitude crossing at CLSTR the FMC reported VREF speed not selected. I reset MCP alt to 8000 after crossing CLSTR as per the SID and the FMC and pressed VNAV and received the CHECK MCP ALTITUDE message on the FMC. VNAV could not be selected. I commenced the climb without using VNAV to 8000. After crossing MAFAN at 8000 I reset MCP to 35,000 and again pressed VNAV. Same thing, CHECK MCP ALT. Continued climb using v/s. On climb a/c went into a 7000fpm dive for no apparent reason. During climb EICAS displayed G/A not CLB. During cruise CON not CRZ. Once reaching cruise altitude I was able to engage VNAV after several attempts. VNAV would not follow the descent profile. It would try to descend as soon as I reset MCP altitude. And I could not engage autoland. Maybe I am doing something wrong, but after seeing this post I wonder. I have the latest FS9 upgrade SU1-1 and this is the first flight since 1-1. I did not see this before. Thanks in advance for any insight.Best RegardsKaleb

This is the same type of departure procedure I'm using, and have the same problem every time. Cannot select VNAV, FMC says to check MCP alt, plus the CLB and CRZ FMC buttons become inactive (although the DES button still works). Additionally, the descent path deviation indicator shows up, although the aircraft is still climbing.MCP altitudes are correctly set, no constraints.Mike F.

Just looking at your screen shots, you are showing a ERR at TOP on you climb page. You have your MCP set for one altitude yet your FMC is set for a completely diferent altitude.If you have a contraint in the Legs portion of your takeoff, that is what you would dial on your MCP. Now, if you blow through that constraint, VNAV will kick itself off.To get VNAV to engage again, you will need to be Below or AT the constraint altitude. Since your MCP is not set there, it's not likely going to happen.I asked Anthony if he could increase the slop factor for overshoots in another thread, but I'll suspect that this is probably the number one problem people are getting into as FS9 seems to be a tad sloppy with the aircraft models (not just PMDG, ALL FS9 Aircraft).Ray

Actually I've had similar problems when departing from Nairobi, Kenya for a test flight. The airport elevation is a little above 5000ft msl, I had set up everything as usual, no alt/costr. in the legs page, cruize FL350, set 35000ft in the MCP alt window but could absolutely not engage VNAV after take-off, nor ever. The same message "check MCP altitude" appeared on the FMC scratchpad. Tried it 3 or 4 times, and everytime wtih the same result. Regards,Bjorn

Hi guys! I got just the same VNAV problem.i got no constraints at all set in the FMC. When i take off i have set my MCP alt to 9000, beacause the SID says to level off at 9000ft until futher ATC instructions. ( I'm flying in norway, and it's different here because you have no waypoints to set constrints at). However, i activate VNAV at about 4000 feet. When the aircraft gets to 9000 feet it levels off with MCP SPD and ALT HOLD (wich should be FMC SPD and ALT HOLD, but that's a nother problem) and VNAV disconnects. Futher i set 33000 in the MCP alt window (my CRZ altitude) when i then activate VNAV, the FMC says "CHECK MCP ALT", VNAV will not egnage and i cannot open the CRZ and CLB page on the FMCI'm telling you guys that VNAV is still bugd. It should be possible for me to go from 9000ft to 33000ft by pressing VNAV again, the real 737-NG can do that! Roar Nicolaisen