PMDG 737 Discussion (PC Version) (Part 1)

v3.0.44 out now.

PMDG 737-600/700/800 Update to 3.00.0044

0011898: [Systems - Hydraulic] EDP Low Pressure lights come on to late in start (rsrandazzo)
0012029: [AFDS - Pitch Modes] Level change down : provision for FS atmoshpere “bursts” pumping pitch up/down (emvaos)
0012002: [Virtual Cockpit - Geometry/Textures] VC Clipping and assorted finds (vscimone)
0010744: [FMS - Route/Legs Pages] Wrapping ETA and time differences around 0000z (emvaos)
0012006: [FMS/AFDS - VNAV] CRZ phase revival even within geometric descent (emvaos)
0011655: [AFDS - Thrust Modes] Provisions and refinement of A/T speed mode in SU10+ turbulence (emvaos)
0010628: [AFDS - Thrust Modes] New AT SPD mode system (emvaos)
0012005: [External Model - Geometry] Cabin lighting tone down needed after SU10? (jbrown)
0011992: [External Model - Geometry] Pilots not shown on extenral view (jbrown)
0011993: [AFDS - Pitch Modes] Oscilattions when using V/S for descent. (emvaos)
0011996: [Virtual Cockpit - Geometry/Textures] Small fap on the ceiling of VC, (vscimone)
0011976: [Virtual Cockpit - Geometry/Textures] VC Vertices cleanup (vscimone)​
additiona: provisions for stability with known SU11 changes.

https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/224012-02nov22-pmdg-737-for-msfs-new-updates-released

No tablet/EFB yet but from the man-

“we are mostly focused on the 900 and tablet implementation. The tablet goes into testing this week, and the 900 probably a week from Friday…”

2 Likes

And I was on the fence about spending $800 on the MCP for my home cockpit lol

1 Like

■■■■ it about 40 mins into a flight. Might have to do the return leg…

1 Like

Yes it was needed, they listened. Much better with this update.

And overall i like this update. Looking around the cockpit seems much more “fluid” than before. The plane feels like it’s dancing on air (and resources).

Well I am doing the return flight! feels very smooth so far. Back to Edinburgh from Asturias. It was very gusty when I left, so I am looking forward to experiencing the new handling.

Still a problem with some 737 animations. This also occurred with the previous version.

I installed various official liveries trough the PMDG operations Centre v2.0.1.2174. But only the KLM version seems to have fully functional animated behavior (Flaps, Speedbrakes / Slats and Tail-rudder).
When I select the other liveries (Ryanair, Alaska Airlines) the animations (and functions) don’t work.

Though the Operations Center I already reinstalled these liveries (after deleting them). But I end up with one (KLM) fully functional livery while the other (verified) liveries don’t seem to work.

I’d appreciate to hear if other members have the same problem or I have to dig deeper to find what’s causing this.

You will have the disparity until you update both LNM and the PMDG database. Do you have a Navigraph subscription? If so you can update both.

So busy flying GA, i really need to take the -600 out for a spin. Love that thing.

Clean Boeing is happy Boeing! :smiley:
Now after having my new cockpit overhaul finished (upload of the newest version will be tonight) I made my first Boeing maiden flight from Juneau airport to Ketchikan (PAKT), Alaska.

And it was a good first Boeing maiden flight. It was not possible to lure out all three cats because when switching on the second autopilot the first one always went off, but a single-channel autoland.

I love that new floor. PMDG should have really send someone down there with a toothbrush to polish all these rivets and metal parts, because I had to do all the cleaning.

First some screenshots from the flight, the interesting questions afterwards…

All systems nomimal. My two flight guests back there seem to be happy too.

Absolutely LOVE that vertical awareness display! I can even see the glide path to the airport, and the altitude I should be on the waypoints - PERFECT!!!

Gliding down the glideslope…

Get the cats ready, the weather outside looks like a Cat2 landing :cat2:

Love the native American style of this airport!

Mulder and Scully have officially arrived and can now begin their investigation about the Saskquatch sightings in this area.

Now a few questions about the Boeing… it seems to be impossible to switch on both autopilots, they just change between right and left autopilot - how is this done to have both activated?

There are two buttons on the autopilot panel, VOR/LOC and APPR APPROACH, which one is pressed first when doing an ILS landing, and it what distance to the ILS sender?

Is it normal that the APP light on the autopilot panel goes out while the autopilot is accurately following the glideslope down to the runway with the diamonds visible on the primary flight display?

When the top of descent came, the Boeing did not started to descent with VNAV and LNAV on on the autopilot. Why did it stay on the same altitude instead of sinking to the RUYOC wapoint? I had to descent manually just like in the Airbus.

Looks like I need some some livery with style, how about an Evers Air Cargo livery…

2 Likes

I do have a Navigraph subscription but when I’m logged in and try to unlock a cycle I seem to need a monthly subscription (10EU?) is that correct or am I trying to login on a classified section of the site?

you do need a subscription, either via monthly or yearly payment. That way you’ll get the new AIRAC cycle database every 28 days.
Updating the PMDG databases goes via the Navigraph Navdata Center app that will be installed when you have a subscription

1 Like

The only time the system will allow both autopilots to be engaged is when performing a CATII or CATIII ILS approach. It requires both Nav receivers to be tuned to the same ILS frequency, both course selectors set to the localizer course, and both localizer and glideslope signals must be received and captured before engaging the second autopilot.

Yes, it is normal for the light in the APP button to go out once both localizer and glideslope have been captured.

The aircraft will not automatically descend in VNAV unless you set a lower altitude that your current altitude before reaching the calculated top of descent point (TOD).

2 Likes

Thanks :+1:, I didn’t know that. I’ll consider subscribing.

So just like in the Airbus the altitude of the waypoints means not much because the altutide is set fully manually with the autopilot panel?
Hmmm…
But there should be an easy way to make the 737 follow the added altitudes, or to enter waypoint altitudes as constraints not allowing the 737 to fly deeper than that.

And I have noticed a real immersive and nice audio feature in the 737!
When the volume control knobs for marker, NAV, ADF and SPKR (speaker) are fully turned up, one can hear the morse code of the ILS beeping!
This is so cool and I miss this feature in the Fenix:

When receiving a VOR (I guess VOR navigation is possible too in a rather old 737 but I am still learning to fly her and I don´t know how VOR navigation is done yet) the VOR antennas probably give off a morse code too that become audible when getting closer.
I know how to implement a VOR as a navigation waypoint into the MCDU of the Airbus, but I have to watch some YouTube tutorials how this is done in a 737 :smiley:

The altitude of the waypoints do mean a lot. The only thing setting the altitude on the MCP is a guarantee that the aircraft does not go to an altitude that is not (yet) cleared by ATC.

The altitude constraints in the FMC matter, and are adhered to when using VNAV. Let us say you are about to descend on a STAR, beginning at FL350. Assume the STAR has multiple waypoints with speed or altitude restrictions, with the last waypoint having a restriction of 4000 feet.

In both the 737 and the A320 you could dial the altitude selector to the restriction of the last waypoint, (4000 feet) before reaching the calculated top of decent point. In the 737, the aircraft will automatically begin descending at TOD. In the A320 you have to manually initiate descent at TOD by pushing the center of the altitude selector knob.

In both models, the aircraft will honor any programmed altitude restrictions in the FMC. If a particular waypoint halfway through the STAR has a restriction of 16000 feet, the aircraft will level off at 16,000 feet before reaching the waypoint, and will then resume descent once the waypoint has been passed.

4 Likes

Unfortunately I’m still experiencing some porpoising. No longer always on climb-out, so that’s good, but on a Seattle-New Orleans flight I encountered some turbulence at FL200; before that the climb was smooth, but after that, and for at least the next hour, the up-down pitch action was constant.

1 Like

Is it possible to edit the default lodes panel states? In particular, I’d like to change the one that loads when you start a flight on approach (click on a runway and set as destination, which takes you to a long final with the aircraft configured for landing).

I’d like to change the configuration it’s sets up as and change some of the switch positions too. But not sure if that’s possible.

How did you get the vertical awareness display to show? I can’t find it anywhere, I was just thinking about this feature the other day, I used it a lot in the Zibo 737 but haven’t found it in the PMDG yet.

You must enable VSD in the aircraft options (somewhere in the display options if I remember correctly) and then you keep pressing the CTR on the EFIS panel till you get the visualization.

1 Like