MANY PAYWARE AIRPORTS CAUSE STUTTERS!

To see the LOD problem with the scenery that causes stutters, turn on Developer Mode (General Options/Developers/On). From the new window menu bar, drop down Debug and tick Debug Model LODs. In the tool window that pops up, tick LOD face count and Display name in addition to the default LOD size. For each model in view you will see the following: (Name of the creator), LOD[0,3], the current screen size of that model and the count of faces that need to be drawn to display it. Most airports will be very cluttered, so you can restrict the display to a particular group by typing in a few letters of the desired object's name - such as part of the creator's company name or whatever. Most 3rd party developers precede their object names with the company name short form (also tick "Use short name"). You'll find that most of the "stutter-generators" show as LOD[0,0] meaning there is only one Level of Detail model available - usually an extremely detailed model. LOD[0,3] is the most detailed of four levels of detail (numbered from 0 as are most computer indices). The screen size is the percent of the vertical size of your screen that a sphere encompassing the model takes up. 100 means that the model is currently taking up 100% of your vertical screen. This number can to to 999%, and the object disappears when it is less than about 1%. I've dumped lots of freeware and payware on general principles when I see only one LOD for a model. Think a little and you will see why taking off past the main terminal that has only one LOD causes stutters. Once you pull away from the object even 50 feet, you do not need a high level of detail. Think about it. IMHO a terminal filled with high face count empty waiting area chairs is just silly! A zillion people milling about has nothing to do with hand-flying an ILS approach in a storm. Thank you very, very much for this video.

Many developers these days make them guilty of too much detail in their scenery. Like interior features which in my opinion we don't really need.

This is such a detailed and informative analysis of the stutters, clearly describing the issue. I really hope Asobo/MS and third party dev see this. People have been yelling "stutters" like headless chickens for far too long. We know now. Thanks for this video mate, top notch content.

Terrific video. Absolutely, 100% true on all points. Newark is the biggest stutter offender. Also, you didn't test this, but FSLTL and similar injector add ons worsen this phenomenon during the last 300 feet on short final.

Don't use rolling cache. The rolling cache is prone to corruption and needs to recycle all too often. Another one is the various cache and shader files. Deleting them regularly also helps a lot.

Well explained. Let's hope your video catches the powers that be attention. This issue Needs to be addressed and resolved!

Good video but people have to understand the key component in a gaming rig or laptop is the processor. The is the engine of it all. When you run payware, your running files not native to the scenery msfs has in the sim. When your GPU and memory are pulling from different application and the payware scenery and the aircraft and the voice inside 1 mile, it is taxing your processor like crazy. A rig must have a consistent range of hardware. Meaning just cause you have a 4 cylinder engine in a Corvette doesn't mean it will be just as fast. Your want high end then 4090 with i9 or razen 9 amd with 32 gb to 64gb of ram. 4090 in and i5 you want get the top proformance. It will be a bit better but not top. Add-ons are resource consuming. Work with your settings.

everyone on the forums should see this video, I dont know how many threads Ive seen related to this

Something they might be doing (i do develop MSFS scenery) is they might be using a set number for LODs distance on all models, so instead of each piece of scenery or building changing LOD at different distances to make the transition smooth absolutely everything is loading a higher LOD at the same time as you approach.

Recording software on approach and take off, may cause additional load on system resources? Since the recording software is not Asobo its 3rd party. Just my thoughts.

Hoping that Developers take note of this excellent practically detailed video! Thank you.

I agree with what you say and love your philosophy about Quality First and not money.

I never had FS2020 encryption files until Asobo's update 1.37.19.0 auto installed June 18, 2024, release notes stated: No Content - No Fixes???? Why Microsoft Simulator does not notify users FIRST before they automatically download updates is beyond their intelligence. The reason is these updates will MESS-UP the simulator files after it reboot/restarts. THEY TELL USER IN THE RELEASE NOTES to uninstall ALL Community Folder content prior to 'their auto-update' or it will mess-up user's sim. Duh... an option to delay these updates (until user has moved community content) would be appropriate!! THANK YOU ASOBO

I have been having this problem ever since I got MSFS early last year. For me, my standard "test flight" to see how good my system is, is to fly from London City to Heathrow in the Fenix A320. I have the iniBuilds EGLL and the Orbx EGLC. I basically never get the stutter on take off, but I do get them on approach/landing, however I don't get them at the freeware Gatwick. Last year I bought a GTX 4080 graphic card and I thought that would fix everything, but it didn't. I, like you, tried turning all the settings down, clearing cache, using Auto FPS, turning AI traffic off and all the rest. Nothing worked. Recently on the MSFS Developer live stream I asked them about this and they said "the memory optimisation in sim update 15 will fix this". I downloaded the update on Friday and in my testing I would say while there's no FPS difference, the stuttering has been reduced a bit. I then updated to the latest iniBuilds EGLL version 3.1.0, which is supposed to include optimisation improvements. Again, I would say there was a slight improvement. I am now at the point where I get one big stutter over the top of the city of London, then I get a few very tiny stutters high on approach (barely noticable), and I get one more medium sized pause at about 300ft. It's not perfect, but it's just about playable now. I really hope they keep working on this, but I'm fed up of waiting for it to be fixed, and I think now it's just about good enough for me to do flights into Heathrow.

Hi, many thanks for making this video, addressing an issue that is quite game braking. At least it makes the experience worse. By the way, what tools are you using for replay and landing performance measurement? And finally, your landings are great!

Im with you. I, too, am not convinced 2024 with magically fix the stutter issues. I have approx 200 custom airports, and have noticed the load times and general reduction in performance. Im running a 4070, and still face performance issues. I fly the fenix a320 and inibuilds a300 most of the time.

Great Job!

Yes yes yes. Your analysis is 100 percent correct. I have too faced this and can confirm. I removed all the 3rd party airports and my sim is absolutely butter smooth. This is really disgusting because 3rd party addon devs are not bothered about stutters. Even some bigger name devs airports are stuttering. I have stopped adding any 3rd party airports almost completely.

Great video, at last i don't feel alone. I use varjo aero with 4090 and it's doing my head in

I used to have to optimise Free and Payware in FSX and I still have to do it in MSFS. Some developers don't follow the SDK, maybe they made products for FSX and continue to use the same techniques for MSFS 'just because it's how they work'. Laziness is never an excuse but most of the developers don't fly like we do, or they might spot the issues. Just imagine if developers started following the SDK and optimising their products. Not all are at fault but many could deliver better optimised products that cause less crashes and/or stutters.