18 hours ago, Reset XPDR said:

These are the 2D settings I use pretty much everywhere, with system FPS capped to 60 and MSFS on default Ultra, that work well, including complex airports:

VR is the same, except target FPS is 40 for motion reprojection to bring it to 80 FPS.

i guess missed the lod step in previous builds. So the LOD step will only change in increments of 5 at a time, i take it. I find the TLOD changes to be the biggest hits on cpu

39 minutes ago, Sonosusto said:

i guess missed the lod step in previous builds. So the LOD step will only change in increments of 5 at a time, i take it. I find the TLOD changes to be the biggest hits on cpu

Yes, 5 is the default LOD Step for FPS Cap mode and I find it works very well. During the initial seek on the ground in this mode, it will increment LOD by steps of 50 so that it can quickly determine whether any extra TLOD on the ground is warranted but thereafter it will use whatever you have set in LOD Step.

  
 

14 hours ago, Reset XPDR said:

As mentioned on github, 0.4.5.2-test2 available here should hopefully resolve this issue to your satisfaction by now allowing settings reduction recovery to occur on the ground in non-expert mode, provided that ground speed is < 25 kts (ie. you are taxiing or stationary, but not taking off or landing).

I tried this out on a couple of flights and works great for my use case. Thanks for your time and effort on this! Much appreciated. As I said, this app is genius and a god send for those of us wanting to balance visuals with FPS.

ps. I'm using TLOD default of 400 as I want that in case I forget to run your app 🙂 but your app seems to handle it well.  When I'm flying in VFR your app is usually increasing my TLOD to around 600 now (not quite as high as I saw yesterday but plenty high enough) and when I land, and the FPS drops below the target for a short time the reduced settings kicks in, which is as I would expect, and then after about 30 seconds (guess?) of taxing at low speed, it seems to recover and I'm back to defaut until I take off and TLOD ramps up with the added FPS headroom.

I will be getting my airliner setup next week and will test it with IFR and night flying to see how that works. Will report back!

Edited July 18, 2025Jul 18 by Virtual-Chris

17 minutes ago, Virtual-Chris said:

 ps. I'm using TLOD default of 400 as I want that in case I forget to run your app 🙂 but your app seems to handle it well.  When I'm flying in VFR your app is usually increasing my TLOD to around 600 now (not quite as high as I saw yesterday but plenty high enough) and when I land, and the FPS drops below the target for a short time the reduced settings kicks in, which is as I would expect, and then after about 30 seconds (guess?) of taxing at low speed, it seems to recover and I'm back to defaut until I take off and TLOD ramps up with the added FPS headroom.

You could just use the IFR profile, despite doing VFR flights, as this has a less aggressive TLOD profile in non-expert mode and would balance out your very high default MSFS TLOD. Alternatively, you can venture in to expert settings and customise it exactly how you like, with 6 profiles available to use. For the latter I suggest you read the readme on what each setting does and try not to change too many settings at once.

5 hours ago, Reset XPDR said:

You could just use the IFR profile, despite doing VFR flights, as this has a less aggressive TLOD profile in non-expert mode and would balance out your very high default MSFS TLOD. Alternatively, you can venture in to expert settings and customise it exactly how you like, with 6 profiles available to use. For the latter I suggest you read the readme on what each setting does and try not to change too many settings at once.

Tonight I ran your app in the background so I could get more immersed, and then at the end of the evening, I looked in the log to see what had transpired, it was targeting 88FPS and while I was flying, it was logging FPS over 100 and TLODs as high as 800 and I was surprised to see a LOT of log entries like this... where it was seemingly detecting an outlier FPS and increasing logging...

...
FPS:113 Day FGAct:True Pri:TLOD TLOD:817 TLODRng:400-820 OLOD:300 AGL:1953 FPM:-8 
FPS:111 Day FGAct:True Pri:TLOD TLOD:817 TLODRng:400-820 OLOD:300 AGL:1954 FPM:36 
Outlier FPS detected. Logging FPS for 10 seconds after last outlier detected. 
Raw FPS: 54.3, Filtered Average FPS: 55.8 (T-1)
Raw FPS: 45.8, Filtered Average FPS: 56.7 (T0)
(repeats several times)
...

This outlier FPS detection and added logging was happening A LOT.

Is this ok? Thoughts?

2 hours ago, Virtual-Chris said:

Tonight I ran your app in the background so I could get more immersed, and then at the end of the evening, I looked in the log to see what had transpired, it was targeting 88FPS and while I was flying, it was logging FPS over 100 and TLODs as high as 800 and I was surprised to see a LOT of log entries like this... where it was seemingly detecting an outlier FPS and increasing logging...

...
FPS:113 Day FGAct:True Pri:TLOD TLOD:817 TLODRng:400-820 OLOD:300 AGL:1953 FPM:-8 
FPS:111 Day FGAct:True Pri:TLOD TLOD:817 TLODRng:400-820 OLOD:300 AGL:1954 FPM:36 
Outlier FPS detected. Logging FPS for 10 seconds after last outlier detected. 
Raw FPS: 54.3, Filtered Average FPS: 55.8 (T-1)
Raw FPS: 45.8, Filtered Average FPS: 56.7 (T0)
(repeats several times)
...

This outlier FPS detection and added logging was happening A LOT.

Is this ok? Thoughts?

Yes, that is a test version logging hangover from the 0.4.5.1 test phase to show when FPS glitches were occurring, which with MSFS 2024 is currently a lot, and how the app responded to them. You'll see that only dips lasting 3 seconds get included in the average FPS. Anything shorter than that gets discarded, which has helped make the app much more robust with MSFS 2024 FPS glitching shenanigans.

I might remove it from the next test version, but still keep it for Test Mode which is a different thing, as it is no longer applicable to the current test scope. As such, ignore these entries if you want.

Edited July 18, 2025Jul 18 by Reset XPDR

On 7/17/2025 at 2:56 PM, Reset XPDR said:

Yes, 5 is the default LOD Step for FPS Cap mode and I find it works very well. During the initial seek on the ground in this mode, it will increment LOD by steps of 50 so that it can quickly determine whether any extra TLOD on the ground is warranted but thereafter it will use whatever you have set in LOD Step.

Got it. Kind of works like dynamic lod but more "polite" on cpu resources, it seems. Especially for people like me with a 7800x3d and 4090 but have a ton of apps running (rass, batc, gsx, fsrealistic) with traffic running. 

I test everything at kjfk or eglc first with traffic. 

What is your hz rate on your monitor? Do you fps cap anywhere else? I set me hz monitor to 100hz and fps cap to 50 (in msfs2024 cfg). Just curious how to make everything smooth, no stutters. Thanks for helping us with this.

On 7/16/2025 at 7:37 PM, Reset XPDR said:

These are the 2D settings I use pretty much everywhere, with system FPS capped to 60 and MSFS on default Ultra, that work well, including complex airports:

VR is the same, except target FPS is 40 for motion reprojection to bring it to 80 FPS.

The image does not display for me. Could I see those settings please?

Brilliant program, don't know why I waited so long to use it. I have minimalist approach to FS where less is better, no tweaking, no FPS monitoring, just fly. But this makes for less effort. Flying 2020, and not using AutoFPS in expert mode. I used to stay at TLOD of 200 and drop it when in complex areas. Now I am frequently at TLOD of 400 and don't have to touch a thing. The only other program I use 100% of time is AIG. Two of the best all time programs happen to be freeware.

5 hours ago, Sonosusto said:

What is your hz rate on your monitor? Do you fps cap anywhere else? I set me hz monitor to 100hz and fps cap to 50 (in msfs2024 cfg). Just curious how to make everything smooth, no stutters. Thanks for helping us with this.

My monitor is a 6 year old TV, so maxes out at 60Hz (which is fine for flight simming IMO). As such I set my FPS to 60 in the global profile in nVidia Control Panel. In any case, I don't really use MSFS in 2D mode except for initial flight load in and testing of my app. More often than not I am not running LSFG and just turn on Vsync at half monitor refresh, which gives me 30 FPS locked and is plenty enough for navigating menus. It also keeps my system running cool and quiet until I actually need the horsepower when I switch to VR.

3 hours ago, Rob G said:

The image does not display for me. Could I see those settings please?

I've posted it up in my github discussion area for this app release here. Please let me know if you still can't see it.

3 hours ago, Reset XPDR said:

My monitor is a 6 year old TV, so maxes out at 60Hz (which is fine for flight simming IMO). As such I set my FPS to 60 in the global profile in nVidia Control Panel. In any case, I don't really use MSFS in 2D mode except for initial flight load in and testing of my app. More often than not I am not running LSFG and just turn on Vsync at half monitor refresh, which gives me 30 FPS locked and is plenty enough for navigating menus. It also keeps my system running cool and quiet until I actually need the horsepower when I switch to VR.

The timing of your reply to the question you quoted couldn't have been timed better with what I have spent a few good hours on the last couple of days. Me and ChatGPT have had our discussions back and fourth on my setup that almost matches yours perfectly. My monitor is 60Hz fixed refresh rate and can almost be classified a memorobilia since it doesn't have any built-in sync functions so my goal was to find a setup for my hardware that worked well, and the end result is nothing else than incredible to be honest, so if you have the time and the patience, I can recommend giving ChatGPT a go since for me it has resulted in a near perfect No G-sync/vSync/TAA/30 to 60 setup. Many minor changes over the last days, but in the end it was just to tune every aspect perfectly for my setup. In short, RTSS Async FPS limiter 0.010 below my refresh rate, LLM on (this made it all come together and flattened my frametime), vSync on in NVCP (off in-sim). This is for MSFS 2020, but I could really not have dreamed about a better outcome. 

2080Ti, 7800X3D (PBO -20), 32GB DDR5 6000Mhz RAM

 

 

Edited July 20, 2025Jul 20 by Benjamin H

50 minutes ago, Benjamin H said:

The timing of your reply to the question you quoted couldn't have been timed better with what I have spent a few good hours on the last couple of days. Me and ChatGPT have had our discussions back and fourth on my setup that almost matches yours perfectly. My monitor is 60Hz fixed refresh rate and can almost be classified a memorobilia since it doesn't have any built-in sync functions so my goal was to find a setup for my hardware that worked well, and the end result is nothing else than incredible to be honest, so if you have the time and the patience, I can recommend giving ChatGPT a go since for me it has resulted in a near perfect No G-sync/vSync/TAA/30 to 60 setup. Many minor changes over the last days, but in the end it was just to tune every aspect perfectly for my setup. In short, RTSS Async FPS limiter 0.010 below my refresh rate, LLM on (this made it all come together and flattened my frametime), vSync on in NVCP (off in-sim). This is for MSFS 2020, but I could really not have dreamed about a better outcome. 

2080Ti, 7800X3D (PBO -20), 32GB DDR5 6000Mhz RAM

 

 

Thanks for that. As mentioned, I usually only use 2D to set up for VR so more applicable to others than me.

BTW, I note you are using DynamicLOD 4.7, which has been superceded by 0.4.8 which has better FPS averaging and some other fixes, none that affect core functionality, so I suggest you update to that.

11 minutes ago, Reset XPDR said:

Thanks for that. As mentioned, I usually only use 2D to set up for VR so more applicable to others than me.

BTW, I note you are using DynamicLOD 4.7, which has been superceded by 0.4.8 which has better FPS averaging and some other fixes, none that affect core functionality, so I suggest you update to that.

That is true, but as you say, might be applicable to others, and that is always something I have in mind when I reply to others. Wouldn't be applicable to anyone if the reply isn't made, but I have to admit that I might have read your reply a little fast, guess it is due to the fact that there in fact is others that hold on to good old monitors. Mine is a Dell U2711 which does a more than good job for me, but getting there when it comes to settings isn't the easiest I would say when you have no sync capabilities in the monitor and for some can lead to an expensive new purchase of a monitor with those capabilities when they can't get the settings tuned, so if someone saves a good bunch of money from the reply coincidentally, I would just be happy.

Thanks for the reminder, the notification has been seen throughout and for a while, and the changes sounds good. I do of course have AutoFPS installed as well, but I can't do anything else then thank you for keeping both of them updated, since some of us likes to do some manual work still and be a little bit more in control. I have found my "set and forget" steps with DynamicLOD, but AutoFPS is also in use frequently. The VRAM that is available is meant to be used (but a buffer is of course being kept to avoid stutters). Target FG FPS is 59, and even though it is very tight, the cloud quality adjustment works well when it is needed once in a while. 



Haven't fiddled to much around with AutoFPS to be honest, but I am very open for suggestions that can give me somewhat the same behaviour as my DynamicLOD is set up. One of the reasons for staying with DynamicLOD is that I have my VRAM under control, and haven't taken the time to read if I need GPU-Z to achieve the same control and similar steps with AutoFPS.

1 hour ago, Benjamin H said:

That is true, but as you say, might be applicable to others, and that is always something I have in mind when I reply to others. Wouldn't be applicable to anyone if the reply isn't made, but I have to admit that I might have read your reply a little fast, guess it is due to the fact that there in fact is others that hold on to good old monitors. Mine is a Dell U2711 which does a more than good job for me, but getting there when it comes to settings isn't the easiest I would say when you have no sync capabilities in the monitor and for some can lead to an expensive new purchase of a monitor with those capabilities when they can't get the settings tuned, so if someone saves a good bunch of money from the reply coincidentally, I would just be happy.

Thanks for the reminder, the notification has been seen throughout and for a while, and the changes sounds good. I do of course have AutoFPS installed as well, but I can't do anything else then thank you for keeping both of them updated, since some of us likes to do some manual work still and be a little bit more in control. I have found my "set and forget" steps with DynamicLOD, but AutoFPS is also in use frequently. The VRAM that is available is meant to be used (but a buffer is of course being kept to avoid stutters). Target FG FPS is 59, and even though it is very tight, the cloud quality adjustment works well when it is needed once in a while. 



Haven't fiddled to much around with AutoFPS to be honest, but I am very open for suggestions that can give me somewhat the same behaviour as my DynamicLOD is set up. One of the reasons for staying with DynamicLOD is that I have my VRAM under control, and haven't taken the time to read if I need GPU-Z to achieve the same control and similar steps with AutoFPS.

As you say, you need to run GPU-Z if you want full VRAM protection with AutoFPS. 

The settings you have made in AutoFPS are pretty much the equivalent of what you have in DynamicLOD, with the exception that with TLOD Base+ checked that TLOD can actually go to double TLOD Top, so 800, over 15000 ft in your case if performance conditions are favourable, which could push your VRAM harder than your Dynamic LOD settings do. 

If you want to make it as close to your Dynamic LOD settings as possible, you could either uncheck TLOD Base+ so that the TLOD Base and Top values are strictly adhered to or you could leave it checked and reduce TLOD Top to 200 and let it go up to 400 if performance conditions are favourable, which should be most of the time given how well tuned your setup is.

Like with my recommendation for DynamicLOD, I suggest you update to the latest AutoFPS 0.4.5.1 app version as it is much more resilient to FPS glitches and has other progressive fixes as well. Have both apps set to auto update will keep these apps updated to the latest stable versions.