As mentioned in my (and not) previuous post... it should work also without VNAV engaged!

"Sylvain is right Ryan, even not selecting LVL CHG or VNAV, when at acceleration height and selecting Bug Up speed on MCP the FD should command a nose down pitch towards that selected speed. That's how it's done, it's clearly shown on FCOM and SOP's worldwide."

I'm always refere to Raw Data.... No Auto Pilot angaged apart TO/GA.....

Raw data usually means no F/D. Just for clarification: You're setting 220 in the MCP, and the F/D is commanding a climb at 240. What does the bugged speed on the tape say?

As mentioned in my (and not) previuous post... it should work also without VNAV engaged!

Hmmmm. My FCOM says:

With VNAV armed after takeoff, VNAV commands acceleration to:• last MCP speed (V2) + 20 kts until acceleration height• if an engine failure is detected, target speed will be last MCP speed (V2) +20 kts if the airplane is at that speed or greater, or the existing speed if theairplane is between V2 and V2 + 20 kts• the flap placard speed minus 5 kts• 230 kts or less when leading edge flaps are not fully retracted• 250 knots with flaps retracted• the active target speed• waypoint speed constraints, or• the speed restriction associated with the origin airport, whichever is morerestrictive.

Matt,... sorry for Raw Data with FD.... my flight instructors should kill me..... (I mean no Autopilot, just TO/GA) The speed value set as Bug UP into MCP at acceleration height is the same shown by the magenta bug on PFD... example 220 kts but the Flight Director commands a pitch up/down in order to fly at 240 kts.Is it normal?About FCOM you cosider a T/O with the VNAV engage .... but without....?However... I think that is a very very small thing.... just few people point it up... and look the great job around the NGX... I can say that was just my curiosity understand the issue and not absolutly a complain!so.... thanks to everyone that gave me an opinion about and to Roberts, Ryan and all the PMDG staff for the great product.

Roberto,OK, after some playing around with this I think I figured out how you are seeing this but it is occuring because SOP for the aircraft is not being followed as outlined in a couple of the previous posts. Basically you are departing with TO/GA mode active, no active flight plan or altitude restriction set in the MCP so the aircraft remains in the TO/GA mode for an extended period of time instead of transitioning to ALT ACQ or VNAV as it normally would in the real world. With that scenario I was able to duplicate the MCP + 20 FD indication in TO/GA until pitch mode transition occurred. Under normal circumstances, the issue would never be seen because the Autoflight system would have transitioned to VNAV or reached an Altitude restriction on the departure forcing a change to ALT ACQ if not operating in VNAV. That being said, I have submitted the item to the team to take a look at to verify the correct operation. At this point I would say any changes to this are unlikely to make the SP1B update but we can look at it for a future update if the fault is confirmed.