1 hour ago, wiltzei said:

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.

I can't say I've ever tried background app max frame rate, so I will take a look and see if I can reproduce what you are experiencing and, if so, see what I can do about it.

Before I do, what FPS source are you using for the app - MSFS or RTSS? Have you tried both to see whether it works with one of them? I am thinking that of the two, RTSS should give you the right FPS as it is the same source as what CapFrameX uses.

9 hours ago, Reset XPDR said:

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.

Repost of a rehost of the screenshot, as it is not showing on my system today:

43 minutes ago, Reset XPDR said:

Repost of a rehost of the screenshot, as it is not showing on my system today:

Thanks! I just did a second flight, KPHX-KDEN. This time I didn't get the blurries, so for now it seems all good (I reinstalled AutoFPS and deleted usercfg.opt to reset my sim settings just to be sure). BeyondATC released an update last night that comes with a local voice model - I have a hunch this was costing me about 10-15 FPS and introducing some stutters vs using their cloud based voice generation. Have reported on their Discord but it seems that this was causing some performance issues on my system. When switching back to the cloud based option I get back my smooth SU4 performance and have taken AutoFPS off the radar for now in terms of causing issues.

11 hours ago, wiltzei said:

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.

I just tried this, with both MSFS and RTSS sourced FPS data, and my FPS always recovers in AutoFPS whenever I make MSFS the active app again.

Note, MSFS has to be the active window for the FPS to recover, not just showing on a screen somewhere, because having any other window with the focus keeps MSFS in background mode, and hence low FPS.

eg. Here is what it looks like with AutoFPS the active window and MSFS visible behind it ie. MSFS is still in background mode:

If I then click on MSFS to be the active window, AutoFPS will still be visible as I have the On Top option selected and FPS recovers.

As such, it looks like it is working as it should. Let me know if there is a specific way to trigger what you are seeing so that I can try and reproduce it.

Edited September 17, 2025Sep 17 by Reset XPDR

16 minutes ago, Speedbird 217 said:

Thanks! I just did a second flight, KPHX-KDEN. This time I didn't get the blurries, so for now it seems all good (I reinstalled AutoFPS and deleted usercfg.opt to reset my sim settings just to be sure). BeyondATC released an update last night that comes with a local voice model - I have a hunch this was costing me about 10-15 FPS and introducing some stutters vs using their cloud based voice generation. Have reported on their Discord but it seems that this was causing some performance issues on my system. When switching back to the cloud based option I get back my smooth SU4 performance and have taken AutoFPS off the radar for now in terms of causing issues.

I always get a bit nervous when I am on the cusp of releasing an update and something like this shows up and threatens it, so I am very pleased it turned out to be something else. Thanks for letting me know!

Edited September 17, 2025Sep 17 by Reset XPDR

In MS2024 I have FPS limited to 30 and then doubled to 60 using FSR3, and AutoFPS is running as shown below. It all seems to be working as expected, so why is the top of the screen shot below red when the rest of it seems to be green? For this test the plane was just sitting on the runway at @ KCOS, I was running at a low screen resolution of only 1920x1080, and I have a 7800 X3D and a 4070Ti Super. What could be wrong that leads to the red display?
Thanks,
Al

Edited September 18, 2025Sep 18 by ark

41 minutes ago, ark said:

In MS2024 I have FPS limited to 30 and then doubled to 60 using FSR3, and AutoFPS is running. It all seems to be working as expected, so why is the top of the screen shot below red when the rest of it seems to be green? For this test I was running at a low screen resolution of only 1920x1080.
Thanks,
Al

 

The red FPS seems to have something to do with the vsync being to an interval that is higher than your max frame rate, regardless of whether vsync is enabled or not, believe it or not!

eg. if I set mine up like yours (FPS limited to 30 and then doubled to 60 using FSR3) but with vsync interval set to monitor refresh rate (60Hz in my case), then I get the red FPS indication:

but if I now disable FSR3 so that I can enable vsync to then reduce the vsync to half refresh rate (30Hz for my system), disable vsync (doesn't actually matter if you do or not) then reenable FSR 3, then the FPS goes green.

 Interestingly, reducing vsync interval even further to one third makes my FPS go red again. Go figure!  😂

Edited September 17, 2025Sep 17 by Reset XPDR

At some point during flight (I’m not sure when), with autofps + dynamic settings enabled, my in game settings got completely reset to something I’ve never set it before (random things at ultra and random things enabled, like parked aircraft, even though I never have it on as I use beyond atc). I think it might have happened when I disabled the ability for autofps to reduce ai traffic in autofps custom settings, but I’m not sure. Whatever happened, it even changed my target fps in dynamic settings to match my max frame rate. I changed everything back to my previous in game settings and somehow everything seems smoother and more crisp graphics (continuing to combine autofps + dynamic settings)? It might be a placebo, I’m not sure. I have since turned off the ability for autofps to reduce settings in poor conditons and  increase LOD in favorable conditions. Also, nights are noticibly darker (as they should be, although maybe that has to do with today’s glitch in real world weather?). I’m not sure what happened.

Edited September 18, 2025Sep 18 by agent00729

29 minutes ago, Reset XPDR said:

if I now disable FSR3 so that I can enable vsync to then reduce the vsync to half refresh rate (30Hz for my system), disable vsync (doesn't actually matter if you do or not) then reenable FSR 3, then the FPS goes green.

Very interesting, and strange. I was able to duplicate your results on this.

Thank you!

Al

38 minutes ago, agent00729 said:

At some point during flight (I’m not sure when), with autofps + dynamic settings enabled, my in game settings got completely reset to something I’ve never set it before (random things at ultra and random things enabled, like parked aircraft, even though I never have it on as I use beyond atc). I think it might have happened when I disabled the ability for autofps to reduce ai traffic in autofps custom settings, but I’m not sure. Whatever happened, it even changed my target fps in dynamic settings to match my max frame rate. I changed everything back to my previous in game settings and somehow everything seems smoother and more crisp graphics (continuing to combine autofps + dynamic settings)? It might be a placebo, I’m not sure. I have since turned off the ability for autofps to reduce settings in poor conditons and  increase LOD in favorable conditions.

Settings reduction, as the name suggests, can only ever reduce settings down and when you disable settings reduction, change one of the custom settings or exit a flight then the app reverts to whatever they were set to when you started a flight, so I am not sure what happened in your case. Also, the only time the app will change the target FPS for dynamic settings if you have enabled TestMode in the common config file and have changed it yourself on the up and down buttons presented, otherwise the app only ever reads, not writes, what this target FPS is set to.

If you want, you can message me the log and I will take a look to see if anything untoward looks like it happened.

Edited September 18, 2025Sep 18 by Reset XPDR

2 minutes ago, Reset XPDR said:

Settings reduction, as the name suggests, can only ever reduce settings down and when you disable settings reduction, change one of the custom settings or exit a flight then the app reverts to whatever they were set to when you started a flight, so I am not sure what happened in your case. Also, the only time the app will change the target FPS for dynamic settings if you have enabled TestMode in the common config file and have changed it yourself on the up and down buttons presented, otherwise the app only ever reads, not writes, what this target FPS is set to.

If you want, you can message me the log and I will take a look to see if anything untoward looks like it happened.

Ok no problem! Where can I find the log? Thanks for the support. 

Just now, agent00729 said:

Ok no problem! Where can I find the log? Thanks for the support. 

In the folder %appdata%\MSFS_AutoFPS\log. Also, when messaging me it, you have to copy paste the contents as you can't attach such files on this site.

New fs beta available

 

And the latest beta breaks AutoFPS again...

14 minutes ago, Speedbird 217 said:

And the latest beta breaks AutoFPS again...

If you mean because of an Simconnect Exception 31 Detected error when you run AutoFPS immediately after MSFS has updated, then follow the first instruction on the pop up that appears and that should fix it:

1. If MSFS was recently updated, restart MSFS first to allow it to finish rebuilding WASM modules, then restart this app.

If it is something else let me know specifically what it is, otherwise it is working fine on my system after an MSFS 2024 and app restart.