monitor your cpu core usage, especially core 0 and see if it maxes out (100% load) during these stutters.

On 9/12/2024 at 10:11 AM, SimianFlu said:

have you found any solution

Kind of. Not going back to Adelaide worked for me.. 😉

11 hours ago, SimianFlu said:

As for AutoFPS, it massively degreaded visual quality (ie. tuned down clouds to High with no option to change it) with no performance benefits whatsoever.

I never used it but use its predecessor DynamicLOD and of course this app won't ever add performance directly but will reduce the single greatest impact on the CPU in our hardware which is TLOD.  From AGL1500 on down TLOD is at 70 but it increases pretty aggressively up to 200 at 10K feet.  I chimed in because I DO NOT have what you describe at all and yet run my native frame rate at 40-45 so a good 33-50% higher than you are setup and all but TLOD are always maxed.  I have Photogrammetry on and have the rolling cache disabled.

38 minutes ago, Noel said:

I never used it but use its predecessor DynamicLOD and of course this app won't ever add performance directly but will reduce the single greatest impact on the CPU in our hardware which is TLOD.  From AGL1500 on down TLOD is at 70 but it increases pretty aggressively up to 200 at 10K feet.  I chimed in because I DO NOT have what you describe at all and yet run my native frame rate at 40-45 so a good 33-50% higher than you are setup and all but TLOD are always maxed.  I have Photogrammetry on and have the rolling cache disabled.

Hmm is there a setting in AutoFPS not allowing it messing with the cloud settings? (in general, any settings except TLOD / OLOD?) because it turns everything down to high and never restores

9 hours ago, molleh said:

monitor your cpu core usage, especially core 0 and see if it maxes out (100% load) during these stutters.

will do. Run the whole hwinfo package to check against thermal throttling (was none), will check the core load too

35 minutes ago, SimianFlu said:

Hmm is there a setting in AutoFPS not allowing it messing with the cloud settings? (in general, any settings except TLOD / OLOD?) because it turns everything down to high and never restores

Don't use it but others will chime in.  I like the simplicity of this app better it's only looking at TLOD and OLOD and are far and away the most relevant for impact in our CPU, and in my case it's always the CPU that comes into play for performance issues:

Release v0.3.3 · Fragtality/DynamicLOD · GitHub

I'm using an older version and don't know what he added for this one.

12 hours ago, SimianFlu said:

UPDATE: it seems Vatsim was the culprit indeed. vPilot in its sheer genius was using every possible aircraft model I had installed, including PMDG and such. Limited mappings to only FSTL aircraft (man, that was a lot of clicking.. some presets like "only use models of low complexity" would be welcome). and it seemed to help - departed KATL and landed at KDCA with both FSTL and Vatsim traffic and ultra details and was okay.

As for AutoFPS, it massively degreaded visual quality (ie. tuned down clouds to High with no option to change it) with no performance benefits whatsoever. I guess YMMV depending on system used. Also despite claiming that it only temporarily (for the time it is run) changes MSFS graphics settings if you follow the instructions, it turned out not to be the case. All that being said, no complaining and all the honor to the devs of both vPilot and AutoFPS, as these kind of apps are incredibly difficult to develop and are completely free. 

Will keep you posted how the situation evolves.

there is a manual of sorts and it shouldn't necessarily degrade clouds.

read the github instructions 

some of us are actively testing the new versions and it has done wonder. 

the issue is as your on final, the sim is loading every single object in existence at the airport or city your close to. cant exactly control that. but what you can control  (autofps) is the terrain and object level of detail. object level of detail drags my fps down too

Edited September 13, 20241 yr by Sonosusto

Do you use ISLC (Intelligent standby list cleaner)?  On long flights, memory can become overwhelmed and cause issues at final destination.  ISLC is a background app that will monitor and clear the memory standby list according to the configured options parameter you set.

Not sure if this is your issue or not but thought I would suggest it.

4 hours ago, jaxgator said:

Do you use ISLC (Intelligent standby list cleaner)?  On long flights, memory can become overwhelmed and cause issues at final destination.  ISLC is a background app that will monitor and clear the memory standby list according to the configured options parameter you set.

Not sure if this is your issue or not but thought I would suggest it.

I use it on both my MSFS pc’s. 

Alr, so I took of from EDDF again where it was >40 other pilots. Way more fluent this time (after forbidding vpilot to use other models than FSTL) but there was still some (way less but still) stuttering after just getting airborne. Oddly enough, cpu usage never reached 100%

 

ps - busy day at EDDF tonight xD

Ok, AutoFPS is not bad at all! Arrived at CYYZ stutter-free. Also I think default FSTL settings needed some reducing

6 hours ago, SimianFlu said:

Way more fluent this time (after forbidding vpilot to use other models than FSTL) but there was still some (way less but still) stuttering after just getting airborne. Oddly enough, cpu usage never reached 100%

I think the correct word there is "fluid" and not "fluent"

I find the default FSLTL settings are pretty hard on performance.

CPU not reaching 100% is no guarantee you won't get a stutter.  I think with the lower FSLTL settings and AutoFPS you'll be much better off.

I tried everything to get rid of stutters on short finals and landings at some airports, especially Nice (LFMN), to which I often fly. I am using AutoFPS, but I still get stutters at this airport, even with TLOD set at 20, no traffic and blue sky, all kinds of caches deleted. Of course, it happens when flying heavy aircrafts, not GA airplanes.

Recently, one fix seems to have noticeably reduce, if not eliminate this issue, a fix recommended on FENIX base knowledge :

Lag on touchdown fix

If you experience lag on touchdown, try the following fix.

Why is this happening? - When you land and your wheels touchdown, that is when the Default Asobo ground services spawn in, you can verify and see for yourself by going into a small airport that obviously carries airliners (so its easier to find the ground services since theres only a few gates) You will find a marshaller and a pushback tug and possibly other things. 

---

What is the fix? - Go into your aircraft.cfg file

• Community\fnx-aircraft-320\SimObjects\Airplanes\FNX_320_CFM\aircraft.cfg
• Community\fnx-aircraft-320\SimObjects\Airplanes\FNX_320_IAE\aircraft.cfg

Look for the word "Services" in brackets [Services]

Change all the values from 1 to 0 EXCEPT JETWAYS. This will prevent the default services from activating. Keep in mind you will need to do this for each plane you use and each variant you use because they all have their own aircraft.cfg and after each update.

I did the same for the PMDG 737/800.

Another solution to test is to load the arrival airport before loading your departure airport, but it seems that it only works if they are relatively close from each other.

 

For other kinds of stuttering, I seems to me that 2 settings are the most important : TLOD (and not Objects LOD) and weather clouds. If you get stutters, reduce then both drastically before doing anything else and see what happens.

Edited September 14, 20241 yr by danhenri

One thing I've noticed at some airports is that the cars in the parking lots are not static parts of the scenery but are dynamic models that get loaded in and are different each time you fly in.

The interesting bit is that sometimes they change constantly, even while you're sitting on the ramp looking at them. At a few airports I've noticed they change several times per second. I imagine that has to cause a hit on performance.