7 hours ago, scotchegg said:

Don’t know if this has been discussed before, but I have an issue with cockpit shadows / occlusion (frankly, I’m not sure what but the cockpit shadows / lighting lose their depth) switching off and on near or on the ground. Am I the only one seeing this?

Is this with AutoFPS running? If so, what broad settings are you using?

I've been playing around testing dynamic settings with AutoFPS and have discovered a few things:

1. Dynamic settings reduces more than just LODs and also seems to reduce ground texture quality and possibly other settings when it gets really aggressive, resulting in blurry scenery not far from your aircraft.
2. Point one is evidenced in that you can have dynamic settings turned off then see what FPS you get eg. 60. If you then set dynamic setting target frame rate much higher, say 100, it can magically get your FPS up to that but it does that by dumbing down the scenery far greater than just reducing LODs would do.
3. To further complicate the issue, I am finding that SU4 scenery is quite blurry just outside your TLOD range circle, even without dynamic settings turned on. As such, it hard to tell what is causing what when blurriness is encountered.
4. Dynamic settings seems to work wonderfully when an FPS limit is used and it is set to that limit. I think it does so because there is performance overhead left over, so it doesn't attempt to reduce LODs when FPS is being achieved, but does start to march them down when FPS starts to decline, even a little, which is the behaviour I was hoping it would exhibit.
5. On the contrary, with an uncapped FPS it seems to be all over the place when it decides to activate. Even if you set your dynamic settings target FPS 5-10 FPS below the average grouping of your uncapped FPS, dynamic settings can activate sometimes and other times not and I am yet to work out what makes it tick in such instances.

Given these observations, for now I have decided to revert non-expert settings to disable dynamic settings like it used to do previously, as it is not really fair to expose non-expert testers to such oddities, especially since many of them are only on the test version because they want SU4 beta compatibility and probably don't really want to be my guinea pigs 😄 .

As I would still like to experiment some more with dynamic settings' effect on AutoFPS, and perhaps others do too, I will keep dynamics settings being able to be enabled in expert mode. I might also come up with a way to quickly enable/disable it and perhaps increment/decrement the associated target frame rate in the AutoFPS UI, so that it is easy for users and I to experiment with, even if such UI controls don't survive into the formal release version. 

Stay tuned for test version(s) to be updated with the aforementioned changes.

Edit: Test23 has been release which switches dynamic settings from auto-enabled to auto-disabled in non-expert mode, as it originally was. The UI update is a tomorrow job.

Edited September 13, 2025Sep 13 by Reset XPDR

Yeah same as my findings then with the texture resolution dropping, I also noticed the Trees LOD was far closer with Dynamic + AutoFPS whereas with just AutoFPS that was further away from the aircraft.

I'm not a huge fan of the internal Option so would welcome a way to quickly turn it On/Off via a tick box or something, but personally I think I prefer just the standard AutoFPS doing it's magic and nothing else.

Of course it's hard to tell whether Asobo have finished with this feature or whether they're actively working on it or will do in the future, which is another reason I'd personally want to avoid it as who knows what they might break with it and thus make AutoFPS act strange at the same time.

Thanks for the update. I still prefer autofps + dynamic settings on my system, which is a lower spec PC. I think for systems like mine it works best (when you are willing/have to sacrifice eye candy for performance in some scenarios).

Edited September 13, 2025Sep 13 by agent00729

23 hours ago, Reset XPDR said:

Is this with AutoFPS running? If so, what broad settings are you using?

Yes, only seems to be happening with AutoFPS running. Using default VFR (not expert) with FSR2 at 60fps.

Edit; just to repeat, it only happens near or on the ground.

Edited September 14, 2025Sep 14 by scotchegg

As mentioned yesterday, I have now updated the app to provide test controls for dynamic settings in expert mode so that it is easy to change them within the app without having to go into the MSFS menus. As there are a lot of users on this test version who are only on it because of SU4 support, and hence may not have an appetite for other testing activites, I have made it so that you will need to enable test mode in the app, which is similar to how it was done for experimental features except the key is called TestMode, in order to see these controls. Even without these controls, you can still change dynamics settings in the the MSFS settings menu while in a flight, it just makes it much easier to do via the app and quickly see before/after changes.

Of specific relevance to this from the release notes:

• Added dynamic settings quick enable/disable, and increase/decrease buttons when enabled, in test mode.
  • Test mode is activated by setting the TestMode key in the app's root folder common config file to "true".
• Added Test annotation to app window title for test app versions when in test mode.

2 minutes ago, scotchegg said:

Yes, only seems to be happening with AutoFPS running. Using default VFR (not expert) with FSR2 at 60fps.

Edit; just to repeat, it only happens near or on the ground.

This can be a side effect of settings reduction kicking in. The simplest way to avoid it if it is happening too often is reduce your target FPS, and/or TLOD Min Base if in Expert mode or your default MSFS TLOD if in non-expert mode. You can also disable settings reduction in expert mode, but to be honest if it is kicking in too often it is really telling you that your settings are too ambitious for your hardware and flight scenario.

I can’t thank you enough for creating this little piece of magic. It’s a literal game-changer. I just stick with auto fps as it performs much better than why I try putzing around in expert settings. I flew all day yesterday and never once had low fps or really bad prolonged stutters. 

On 9/12/2025 at 2:33 PM, Reset XPDR said:

Sorry, I must have missed your original message in all the mayhem trying to get the new SU4 beta working with the app. I still use the last known good driver for the 4000 series that came out just before the 5000 series did, namely 566.36, with great success. If you've found something that works well, stick with it!

No, you didn't miss anything -- all is good. And I have switched to also using the Nvidia 566.36 GPU driver and there are no stutters as long as HAGS (Hardware Accelerated GPU Scheduling) is off. For some reason on my Win11 system (AMD 7800-X3D, 4070Ti Super, 64GB RAM, 4TB NVMe) turning on HAGS definitely introduces small stutters despite using AutoFPS. Don't know why, and it's kind of surprising since it seems the general recommendation is to turn HAGS on to reduce the load on the CPU.

 

Al 

Edited September 16, 2025Sep 16 by ark

I have been testing with both Auto OLOD and Dynamic settings turned on and when I do they appear to be interfering. For example, I set OLOD to 200 in the sim and in Auto FPS at 200 locked below 2,000 feet. But when on the ground, with both enabled, my OLOD starts at 103 and goes lower from there, even though my FPS is where I set it. It doesn’t matter where I’m at in the sim.

However, if I disable Auto LOD, Dynamic Settings does not lower it from 200 and I still maintain the same FPS. So I’m not sure why, but perhaps AutoFPS prioritizes TLOD over OLOD? Increasing above my TLOD setting at the expense of OLOD even though I have the minimum/maximums set. 
 

My TLOD is set to 200 Max with the option set to go higher. It will rise to 400 but drop my OLOD below 100, even though OLOD Minimum is set to 100 at altitude and 200 at Base. 

Edited September 16, 2025Sep 16 by Gulf76

2 hours ago, Gulf76 said:

I have been testing with both Auto OLOD and Dynamic settings turned on and when I do they appear to be interfering. For example, I set OLOD to 200 in the sim and in Auto FPS at 200 locked below 2,000 feet. But when on the ground, with both enabled, my OLOD starts at 103 and goes lower from there, even though my FPS is where I set it. It doesn’t matter where I’m at in the sim.

However, if I disable Auto LOD, Dynamic Settings does not lower it from 200 and I still maintain the same FPS. So I’m not sure why, but perhaps AutoFPS prioritizes TLOD over OLOD? Increasing above my TLOD setting at the expense of OLOD even though I have the minimum/maximums set. 
 

My TLOD is set to 200 Max with the option set to go higher. It will rise to 400 but drop my OLOD below 100, even though OLOD Minimum is set to 100 at altitude and 200 at Base. 

Auto OLOD, when enabled, normally follows a strict altitude/OLOD schedule and the only time it may vary from that is if settings reduction kicks in an imposes a LOD reduction of up to 50% for both TLOD and OLOD. If anything, the introduction of dynamics settings should be doing the opposite of what you seem to be saying in that, when enabled, you should no longer get any visible OLOD reduction because dynamic settings is managing it instead.

The best way for me to assess what you say you are experiencing is for you to message me the contents of your associated log file, located in %appdata%\MSFS_AutoFPS\log, and I will take a look at it.

Just sent it. 

Did something change/break with the last 1-2 test builds?

I'm having some issues since yesterday:

On the previous test build, yesterday I noticed that for the first time I had a lot of "object popping" when changing views. I have off-screen terrain pre-caching on Ultra and never noticed this before, but when taking off from KPHX last night objects and tiles were very visibly loading/popping in every time I changed view direction.

Today the latest test build installed and on my first flight with it the object/tile popping was even more apparent than yesterday. In addition, I had significant TLOD issues. I flew KBOI-KPHX and when I loaded into KBOI at the gate I immediately noticed that the mountains in the distance looked quite blurry. When I started my taxi and was approaching the runway the taxiways/ground textures also got very blurry and when I lined up on 10R the textures got even more blurry and it looked like TLOD 10. When I switched off AutoFPS it went back to normal. Throughout the flight I noticed that the ground didn't look quite as crisp as I remembered it from previous flights despite cruise TLOD sitting at 400. When I was approaching KPHX the terrain/object popping re-appeared very visibly and was now even happening right in front of me - looking out straight the window to the runway ahead I could constantly see objects popping in below and ahead of me. When I was getting closer to the runway it got very blurry again (like in KBOI) and it actually degraded in front of my eyes, i.e. it looked fine initially, then it got more blurry and then even worse. By the time I started my flare it looked like TLOD 10 again and the runway was just one grey blurry mess but during the flare I then got a pause and it loaded back in looking ok. During taxi to the gate I had constant switches between blurry and non-blurry taxiways, changing in front of my eyes again (one moment the same stretch of taxiway was fine, 1 second later it got blurry, 10 seconds later it started to recover again).

I never had any of those issues before. I'm on SU4 and don't use dynamic settings in the sim (though it almost felt like it was somehow forced on in the background perhaps, even if the sim showed it as off?). I also noticed that my FPS were higher than usual - I normally aim for 80 in all scenarios and would get 80-90 at airports but in KBOI I saw 120 when I had the blurries and in KPHX I was also 90-100 with the blurries. When this happened I checked AutoFPS but it was showing TLOD 400 in the air when the ground was blurry and 100 on the ground when it looked like it was actually TLOD 10.

Any ideas? Settings below:

Feature request / bug report. App Version 0.4.5.5 / FS24 SU3 Rivatuner / 7.3.6.28010

Issue: When nVidia "Background application max frame rate" mode is activated (I do dev work), AutoFPS fails to acquire correct FPS from sim upon activating the FS24 window; It stays in low LOD modes.

My background FPS is set to 20, and AutoFPS sees that value.

Weirdly, I'm able to see correct FPS from another app (CapframeX), which uses Rivatuner as well.

Settings: NFR / 50 / VFR defaults / Auto target checkbox off

Expected behaviour: AutoFPS to revert back to expected LOD mode behaviour whilst Flight Sim is the active app.

Edited September 17, 2025Sep 17 by wiltzei

2 hours ago, Speedbird 217 said:

Did something change/break with the last 1-2 test builds?

I'm having some issues since yesterday:

On the previous test build, yesterday I noticed that for the first time I had a lot of "object popping" when changing views. I have off-screen terrain pre-caching on Ultra and never noticed this before, but when taking off from KPHX last night objects and tiles were very visibly loading/popping in every time I changed view direction.

Today the latest test build installed and on my first flight with it the object/tile popping was even more apparent than yesterday. In addition, I had significant TLOD issues. I flew KBOI-KPHX and when I loaded into KBOI at the gate I immediately noticed that the mountains in the distance looked quite blurry. When I started my taxi and was approaching the runway the taxiways/ground textures also got very blurry and when I lined up on 10R the textures got even more blurry and it looked like TLOD 10. When I switched off AutoFPS it went back to normal. Throughout the flight I noticed that the ground didn't look quite as crisp as I remembered it from previous flights despite cruise TLOD sitting at 400. When I was approaching KPHX the terrain/object popping re-appeared very visibly and was now even happening right in front of me - looking out straight the window to the runway ahead I could constantly see objects popping in below and ahead of me. When I was getting closer to the runway it got very blurry again (like in KBOI) and it actually degraded in front of my eyes, i.e. it looked fine initially, then it got more blurry and then even worse. By the time I started my flare it looked like TLOD 10 again and the runway was just one grey blurry mess but during the flare I then got a pause and it loaded back in looking ok. During taxi to the gate I had constant switches between blurry and non-blurry taxiways, changing in front of my eyes again (one moment the same stretch of taxiway was fine, 1 second later it got blurry, 10 seconds later it started to recover again).

I never had any of those issues before. I'm on SU4 and don't use dynamic settings in the sim (though it almost felt like it was somehow forced on in the background perhaps, even if the sim showed it as off?). I also noticed that my FPS were higher than usual - I normally aim for 80 in all scenarios and would get 80-90 at airports but in KBOI I saw 120 when I had the blurries and in KPHX I was also 90-100 with the blurries. When this happened I checked AutoFPS but it was showing TLOD 400 in the air when the ground was blurry and 100 on the ground when it looked like it was actually TLOD 10.

Any ideas? Settings below:

Looking through the release notes, there's no change I can see that would cause such a drastic drop in visual quality, especially if the LODs the app was indicating were being set were as high as you say. You say dynamic settings was, which would be evidenced by TLOD and OLOD staying named that way when you were in a flight session, but even if it was it shouldn't be dumbing down the graphics that much, although it could if its target frame rate was set very high.

The quickest way to tell what is going on when the graphics degrade like this is to go into the MSFS settings and cross check that LODs and dynamic settings are currently set the way AutoFPS says they are. eg. here's a screenshot I did earlier today showing the settings matching between the app and MSFS, noting that I intentionally have dynamic settings enabled:

Let me know if they are any different.