jrw4

Didn't we read sometime back that MSFS had gone through its 10 millionth user? I'm sure not all of them stayed active, but 2% seems like a low figure.

To the OP, are you using a monitor that provides for HDR10 and has HDR been turned on for both the terminal and Windows? If "yes" to that, has the monitor been calibrated as well? I have read that the calibration is more easily carried out in W11 than in W10, but can not be sure. Turning on HDR with an SDR terminal is a recipe for blown out highlights of the sort that you describe. Since I went with full HDR in MSFS, that problem has gone away. Cheers.

So long as you have installed the FSLTL base models correctly installed in your community folder using the FBW Installer app, it should work fine. Presumably you would need to uninstall the AIG models as well. Give it a try and please let us know how it works.

I believe the term "Scenery Gateway" refers back to that created for XPlane 11(?) some years ago. https://gateway.x-plane.com/ This made it possible to use the XP World Editor to modify and update the default airports to a higher standard. From my perspective, it worked surprisingly well in creating 3D airports that were superior to what originally were quite rudimentary XP airports. It would seem that this would be harder to do in MSFS, because the quality of the defaults is significantly better than that which existed in XP before the Scenery Gateway. Having said that, I would guess that the vast MSFS community would, if the World Hub ever becomes available along with a relatively straightforward airport editor, do a great job in upgrading the default airports. This is not a trivial effort for Asobo, however, because in addition to creating the necessary software systems, it would also need to provide ongoing curation for submitted upgrades as well. Not a small job......

Interesting advice, but how does one do this given how dynamic the CPU and GPU loads seem to be in different modes of flight? The graphics settings needed to match CPU and GPU load would be very different sitting on the ramp at KELM, for example, vs. final approach at KJFK. Absent dynamic graphics settings, how does one do this?

Just to clarify, WU12 refers to the World Update that includes NZ. Perhaps you were referring to SU11 (the current stable system update) or SU12 (the current beta). BTW, I would agree completely that the most direct line to a solution is likely to run through the Fenix Discord.

Just for our edification, Texture Resolution and DX version seem to require a reboot. Any others?

👍 Thanks.

Could you share the route? It would be interesting to try.

Thanks. Why don't you file a ticket with PMDG and see how they respond? That looked like a 70-80 degree turn at M.78 with a 40 kt wind starting as a tail wind and ending as a cross wind. I feel that overall LNAV did a good job of tracking the course without wandering or overshooting the new course. I'm totally ok with that behavior, but I guess that the turn could have been initiated earlier at a lesser bank angle, etc. I try to fly realistic routes out of Flight Aware or Edi-Gla and I can't recall having to deal with such a sharp turn at cruise, but I sure wouldn't say that it doesn't happen. If that's "degraded" it must have been very good way back when. Let PMDG know about it and suggest a fix.

Getting back on track, I closely followed the LNAV behavior on a flight at at FL380 and M.78, zooming in to the maximum resolution of the ND. I was unable to confirm the behavior the OP described. At course turns as large as 25 degrees, the LNAV closely followed the magenta line with a smooth roll into a bank of 15-20 degrees and no overshoot or hunting after the new course was established. Not sure if that helps. Perhaps someone could suggest a specific instance in which degraded behavior was observed and others could check whether this is generally the case. Best wishes.

I just checked the FCOM and here's what it says regarding the Bank Angle Selector To the extent that the back course of the LOC might be considered a VOR mode, your observation is consistent with that definition. I believe that much of the discussion in this thread refers to LNAV mode, i.e., lateral navigation guidance is provided by the FMS. The referenced role of the Bank Angle Selector does not provide for its limiting the angle of bank when in LNAV mode. The FMS itself calculates the required bank angle based on the relevant conditions of flight, e.g., speed and altitude. Whether it does so correctly seems to be in question.

But someone earlier in this thread said that there was a problem with DME arcs. There seems to be some confusion here.

So I did try an approach with a DME arc, the ILS RWY 7R at KDAB after a short flight over from KJAX. I flew the OMN transition with a 90 degree turn at OMN and another at HANAV, the IAF for the DME arc. From just north of OMN, the approach was flown at the flaps up maneuver speed for the B737, which was around 190 kts, with flaps 1 being deployed as I approached the localizer course. Overall the LNAV seemed spot on. The right angle turns were taken at 30 degrees of bank, and the turns on the DME arc were taken at around 20-25 degrees, with a gentle roll in and out. I did not observe overshooting and the need for corrective turns at any point. The PMDG FMC does not yet permit curved segments, so the DME arc was represented by a set of short straight line segments defined by pseudo waypoints. PMDG has reported that an updated system that permits curved LNAV segments is in the works, however. It would be interesting to see videos of the LNAV system's misbehavior.

There was a major update to the lateral guidance system that was made in the update published on 23 July 2022. I don't recall any further updates involving that aspect of the model.

Hard to say, but I have gone back to DX11 because the use of DX12 on my system results in an unacceptable Render Latency value over 100 mS. I am running stutter-free at Ultra settings at 4K at all but the most complex airports locked at vSync of 30 fps. At those complex airports, I will go back to High End graphics settings. And that's with FSLTL running as well. System info in the signature. I'm not a tweaker, so I tend not to fuss with the individual settings, but just use those provided by MSFS. I aslo make use of the convenient image scaling settings in GeForce Experience (horror of horrors to the tweaker community), which allows me to set Render Resolution and Sharpen values easily. We all have different ideas of what is acceptable quality and performance in our flight sims. Find yours and have fun.

By any chance do you have a video of this LNAV behavior? I haven't tried a DME arc recently, but will now look to do so.

By "floating", I meant non-vsync. Since you reported further down in the thread that you had determined that your system was main thread limited, it means that vsync is actually off. If it were on, you would always see that you were GPU limited, or at least that 's what I see when I turn on vsync. So my suggestion would be that you turn on vsync and limit your frame rate to 30 fps, at least as an experiment. If you can get your monitor to display 30 fps, then run vsync at 100% of the monitor rate. If it can only run at 60 fps, then use 50% of the monitor frame rate. And just to confirm, if you fly into/out of default airports, do you see the stuttering?

Default airports? Bespoke? Add-on? Are you running with some sort of vsync at a fixed fps or floating? Have you tried other settings than ultra for the graphics? Have you tried this with aircraft less demanding than the Fenix? There seem to be a lot of things that can make MSFS run oddly. When something like that happens I try not to work from the top down and change one thing at a time, because that can take forever. I just revert to the basic system with an empty Community folder and work my way up.

Not that hard to find https://navigraph.com/apps/charts/ingame-panel Very useful for the VR folks especially, but also good for streamers. I'm strictly a 2D simmer, so I use use the Navigraph iOS app. Nice to have choices.

As noted in some previous discussion, I also use Webroot and have found it to be remarkably trouble free. However, its firewall only monitors outgoing traffic. Windows Defender continues to provide inbound firewall protection. Its explained here: https://answers.webroot.com/Webroot/ukp.aspx?pid=17&app=vw&vw=1&solutionid=1301&t=You-want-to-know-if-SecureAnywhere-is-compatible-with-another-firewall#:~:text=The Webroot firewall monitors data,traffic coming into your computer.

All of these are great ideas, but perhaps it might be good to back off for a moment and try something easy. Clear out the Community folder, set the graphics to mid-range (yeah, I know it's crazy), and fly from/to default MSFS airports in a C172. Go back to DX11 (DX12 is still in beta), and let us know how it goes. How's the stuttering? If you still have it we need to look elsewhere. You can always try a clean install of MSFS, too. I once had to back up to that in order to resolve CTDs and I have had no problems since. If that doesn't work, you may need to reinstall the OS from scratch and install MSFS first. BTW, I don't recall anyone asking what you were using for security. Is it Windows Defender or something more exotic? There have been reports of one or another AV causing problems. Good luck with this one. There's no shortcut to doing systematic debugging. Please let us know how you solved the problem.

There's an excellent series of new YT videos by 737ng Driver that looks in some detail at the correct operation of the HUD. It starts with this overview and then goes on to address the correct usage of the HGS in various phases of flight, including instrument and visual approaches. Remarkably, it's possible to use this system for manual control of ILS approaches all the way down to Cat 3A minima. Amazing!

I run a 3070ti with an i7-11700K and it performs admirably on a 4K screen with HDR. I typically lock the sim frame rate to that of the monitor, which I set to 30 fps. My favorite airliner is the PMDG 737, and it runs stutter free at all but the most complex default airports with settings at ULTRA. If I'm flying around KJFK, EHAM or EGLL, or running FSLTL with higher traffic levels, I might go to HIGH-END to ensure stutter-free performance. Of course, things would be different if I wanted 60 fps performance. There are enough postings on this forum by folks having problems achieving that level, but the 4000 series nVidia cards seem to get past that barrier. I have a friend who was an nVidia engineer, and he has promised to explain to me how this works, but at the moment, it's all black magic to yours truly. Have fun.

Thank you!