That’s a problem on the Navigraph side. I fly to Gdańsk from Kraków frequently in real life and although most of the time we land on 29, both the RNP11 and the VOR11 flight path angle in our charts and on the FMC match. You could maybe send a query to the Navigraph team for them to correct the position of the RW11 point
In a real situation such a discrepancy on the flight path angle would immediately disqualify to fly an RNP approach. One of the requirements for flying an RNP is that the angles between the chart and the FMC are within ±0.1º. I’d say in the sim I wouldn’t freak out about it and I would still shoot the approach. But you say that you’re high on profile. That’s the part I don’t understand. If you’re flying VNAV, you’ll be on path according to what’s on the FMC. It’ll just be during your altitude vs distance checks along the final approach where there will be a difference and if the angle in the FMC is lower than on the chart, you wouldn’t be high, you should be slightly low on every altitude/distance check.
Make sure your FAF is at the correct distance and that it has the correct altitude (GD801, 5.4nm from the runway at 2500ft). The problem here is that the chart does not contain a MAPt just an MDA so it’s up to the database provider to add a RW point that results in the correct flight path angle. In the simulated world this isn’t a big deal as long as you don’t bust your minimums if you don’t become visual. If you’re visual just follow the PAPI knowing that the MEH is 62ft. This means that the PAPI is 3.5º but it’s designed for a larger airplane so you may see 3 reds. In real life, like I said, the FMC and the chart must be within ±0.1º or else you can’t do this approach.
Note that this is only a requirement on RNP/RNAV approaches. This means that instead of the RNP11 to EPGD, you could shoot the VOR11 completely legally even with that GP angle discrepancy.
That’s the problem with the replay tools. They don’t remember anything, not even the position of the cockpit PFD fpm, etc. Watching the replay from the cockpit is a waste of time. The spoilers, though, they remember most of the time, but on that particular one, they didn’t. You’ll notice I mentioned that too. I wish we could get a good replay tool that takes not of all these including flaps, lights, nosewheel swivel, etc. The X-Plane 11 replay takes not of all these even including engines (off or on). The old flight recorder of FSX did all that too.
And I was using the payware app FS Playground to record my replays, then playing it over and over from different angles.
this morning i have had this surprise. I am on SU10 Beta 1.27.17.0 on dx11 (but this happen also with dx12). I have tried to reload more times MSFS 2020 but the result does not change.
The last time i used the PMDG 737-600 was about 1 month ago and i was on SU10 beta first version and all work correctly.
Looks like and issue with internal lod config. Possibly a missing or corrupt file so a reinstall of the aircraft is likely your best bet. I’m assuming other aircraft are fine?
Do you have the visible Pilot or Copilot Avatar installed by chance? I get the pixalated cockpit after PMDG 737 updates with the mod installed, so I remove it and fly solo until the next Pilot/Copliot Avatar update comes out.
Just kidding, this is the basic 3D model that is loading in first while the real cockpit follows one or two seconds after.
It definately should load, but the SU10 Beta might have caused some bug that prevents loading the ultra high quality LOD.
The problem is there is no uninstalling an SU so it looks like the PMDG 737 will be grounded for a week or so until the final version of the SU update release comes out. Thanks for the warning I will not try install the Beta update!
This is an issue with the visible Copilot third party addon, and well-documented on the PMDG forums. I would suggest to remove it, and it should go back to normal.
I’m on SU10, and this is not a SU10 issue. I’ve not heard of this type of LOD issue with SU10.
Which simbrief profiles do you guys use for 737-8? I saw some on flightsim.to (184 PAX) but its MLW is above 66t which makes it a cat D airplane - am I correct? Is PMDG 737-8 MLW more than 65,3t by default (66361 kg)?
Hm this might be some instrument panel shadow glitch… not all shadows are thrown accurate sometimes the sun shines through panels and throws shadows on for the illumination angle impossible areas.
The approach category of an aircraft is based on its approach speed - not directly on its weight. If a given aircraft could potentially have a minimum approach speed of 141 knots or greater (at a certain weight), it is class D, even if that same aircraft (when lightly loaded) might have an approach speed of considerably less than 141 knots. It must observe class D minimums on every approach it flies, even if on a given day, it is capable of flying an approach at less than 141 knots.
The 737 seem to have better wings with more lift, when loading my 737 cargo ship with 70 tons MTOW it rotates at 110 knots, my half-empty Airbus rarely takes off below 141-145 knots.
Hey mate , i bought that 737-800 as well but it says it is in the market place and it shows in the community folder but its not installed, can you help me there?
yes I confirm the copilot mod is the cause. I removed the mod as suggest from PMDG support center and the 737 is back. Thank you to everyone helped me and in particular to PMDG support center who has answered me even on sunday. Great client support.
