2 hours ago, Reset XPDR said:

It's alright. I was excited for you, and perhaps a bit jealous 😄

Btw : I use Lossless Scaling on the Left view client ( 1x 4K ) for Vsync only. Framerate limited inside FS24 to 30.  In FS24 I use FG. Monitor at 60 hertz.
What do I set Target FPS too ? 30 or 60 ? I want 60 FPS onscreen.

On my server ( 2x 4K ) I use Lossless Scaling to double the FPS on the Right view monitor. The app runs on that monitor. Framerate limited inside FS24 to 30. On the Front view monitor (main) I use FG. Also monitor at 60 hertz. What do I set Target FPS too ? 30 or 60 ? I want 60 FPS onscreen.

Thanks 

Edited July 20, 2025Jul 20 by GSalden

1 hour ago, GSalden said:

Btw : I use Lossless Scaling on the Left view client ( 1x 4K ) for Vsync only. Framerate limited inside FS24 to 30.  In FS24 I use FG. Monitor at 60 hertz.
What do I set Target FPS too ? 30 or 60 ? I want 60 FPS onscreen.

On my server ( 2x 4K ) I use Lossless Scaling to double the FPS on the Right view monitor. The app runs on that monitor. Framerate limited inside FS24 to 30. On the Front view monitor (main) I use FG. Also monitor at 60 hertz. What do I set Target FPS too ? 30 or 60 ? I want 60 FPS onscreen.

Thanks 

To be honest, I'm not really sure how your multi monitor and client server arrangement works with the app but the simplest way to tell what target FPS to set it to observe what FPS the app is telling you it is reading and base it on that.

58 minutes ago, GSalden said:

Btw : I use Lossless Scaling on the Left view client ( 1x 4K ) for Vsync only. Framerate limited inside FS24 to 30.  In FS24 I use FG. Monitor at 60 hertz.
What do I set Target FPS too ? 30 or 60 ? I want 60 FPS onscreen.

On my server ( 2x 4K ) I use Lossless Scaling to double the FPS on the Right view monitor. The app runs on that monitor. Framerate limited inside FS24 to 30. On the Front view monitor (main) I use FG. Also monitor at 60 hertz. What do I set Target FPS too ? 30 or 60 ? I want 60 FPS onscreen.

Thanks 

My guess would be have a look what AutoFPS receives as the FPS from the sim and what scaling it reports being in use (LSFG/FG Active). I would do a takeoff in a demanding area and see if it drops below either 30 or 60, depending on what AutoFPS reads. If it is stable at 30 or 60 pretty much all the time, I would cap it just below it to reduce stutters etc. 

Or try what I have done to make life as easy as possible. Image below. With so many different config on each monitor I am impressed that you are able to have control of it all. I have enough with my single monitor 🙃 Have seen some videos on your youtube before and took a look today as well, and it looks like it runs very well, and you are basically where I was a week or so ago, eager to finetune to get everything out of your system. Of course adjust accordingly when it comes to TLOD values, but feel free to give it a go. 

37 minutes ago, Reset XPDR said:

To be honest, I'm not really sure how your multi monitor and client server arrangement works with the app but the simplest way to tell what target FPS to set it to observe what FPS the app is telling you it is reading and base it on that.

After some tests it appears that I set the FPS to what I want it to be. To be sure I set 58 as Target fos on both server and client.

I lowered the max planes at Amsterdam to 28 and set TAA back to Quality and now I have a little extra headroom.

On the Leftview pc I left TAA enabled as it can handle one 4K monitor.

39 minutes ago, Benjamin H said:

My guess would be have a look what AutoFPS receives as the FPS from the sim and what scaling it reports being in use (LSFG/FG Active). I would do a takeoff in a demanding area and see if it drops below either 30 or 60, depending on what AutoFPS reads. If it is stable at 30 or 60 pretty much all the time, I would cap it just below it to reduce stutters etc. 

Or try what I have done to make life as easy as possible. Image below. With so many different config on each monitor I am impressed that you are able to have control of it all. I have enough with my single monitor 🙃 Have seen some videos on your youtube before and took a look today as well, and it looks like it runs very well, and you are basically where I was a week or so ago, eager to finetune to get everything out of your system. Of course adjust accordingly when it comes to TLOD values, but feel free to give it a go. 

My heaviest test environment is Amsterdam Schiphol + PSXT Live Traffic + Amsterdam Landmarks.

With Lots of Clouds and the city of Amsterdam nearby with all its canals ,this is a perfect testing environment.

Like you and many others I want the best views, with a good framerate and as much detail as possible…

It now looks good again 

3 hours ago, GSalden said:

My heaviest test environment is Amsterdam Schiphol + PSXT Live Traffic + Amsterdam Landmarks.

With Lots of Clouds and the city of Amsterdam nearby with all its canals ,this is a perfect testing environment.

Like you and many others I want the best views, with a good framerate and as much detail as possible…

It now looks good again 

Sounds good, and I really enjoy the level of knowledge that this whole topic has to offer. Even though there is always the risk of ruining something that runs well, I feel that a lot of us that take part in these discussions has the capacity to actually extend the saying "if it ain't broke, fix it until it is", "and then be able to revert our changes and it ain't broke again". 
 

One thing you might try on your vSync+LSFG monitor. Use RTSS Front Edge Sync and set it to your actual refresh rate divided by 2 and then subtract 0.010 from that value and set that as your FPS limit in RTSS and disable the one within MSFS 24. I tried LSFG also during my extensive testing, but encountered artifacts. Not terrible artifacts, but in 2020 the framegen mod works pretty much without artifacts for me, but the smoothness was almost as good with LSFG. I enabled vSync for LSFG in NVCP (made a new profile), prefer maximum performance and sync mode set to vSync within LSFG as well. VSync on-off within 24 I am not sure of, but what I learnt was to enable settings as few places as you actually need so they don't interfere with eachother. 

Edited July 20, 2025Jul 20 by Benjamin H

MSFS_AutoFPS version 0.4.5.2, a minor maintenance update, has just been formally released and is available for download here. Thanks to those who participated in the test phase of this release, particularly @Jerryyyyy over on github.

Executive Summary

This release improves Auto Target FPS functionality, Auto Settings Reduction and future MSFS 2024 update compatibility. It also addresses several minor bugs and stability issues, particularly around TLOD transitions and app version tracking.

Summary of Changes

Auto Target FPS System — Improved auto FPS recalibration, with per-profile support and automatic disabling of incompatible features like auto settings reduction and TLOD Base/Min +.

Auto Settings Reduction — Enhanced responsiveness and stability during flight by excluding settings changes in critical phases and accelerating recovery timing under safe conditions.

Testing & Diagnostics — Disabled FPS outlier event logging in non-Test builds, retaining it exclusively for Test Mode where targeted telemetry validation is still required.

Bug Fixes & Resilience — Resolved edge-case behaviours including day/night TLOD transition bugs, settle timer reactivation, and app version tracking anomalies for more predictable operation.

MSFS 2024 Offset Compatibility — Expanded search range and added fallback logic to ensure robust offset detection and config recovery across simulator updates and custom configurations.

Please review the updated readme here, which provides a detailed description of the app, installation, features and settings, before asking any questions or raising any issues about the app.

 

Bonjour... problème de mise à jour avec install.NET runtime Desktop. Je n’ai jamais eu de problème avec les mises à jour précédentes... merci

42 minutes ago, mgrandjean said:

Bonjour... problème de mise à jour avec install.NET runtime Desktop. Je n’ai jamais eu de problème avec les mises à jour précédentes... merci

Nothing  changed with the installer in this version, so it should be working. Try manually installing the latest .NET 8 runtime first from here before trying the installer again.

41 minutes ago, Reset XPDR said:

Nothing  changed with the installer in this version, so it should be working. Try manually installing the latest .NET 8 runtime first from here before trying the installer again.

THANK YOU...problem solved by reinstalling NET 8.0. This situation is strange. A big THANK YOU for your program and generosity

Edited July 24, 2025Jul 24 by mgrandjean

Thanks again for this amazing app!

Not really sure what changed in 0.4.5.1 but it was amazing. I had TLOD 50 at/below 2000feet and 200 TLOD, Auto OLOD was left on at 200. I used FPS variance of 2%...

get this....even at KJFK, Beyond ATC traffic (all set to 5 and 7 enroute) it was amazing. GSX, Raas, active sky and head tracking.....hardly a stutter. This was in the fenix. I did turn off visible passengers in GSX which makes a huge difference for the fenix. 

THANK YOU AGAIN! 

1 hour ago, Sonosusto said:

Not really sure what changed in 0.4.5.1 but it was amazing.

IMO, the change to the new windowed moving average FPS was one of the most significant improvement ever made to the app, making it much more resilent to MSFS stuttering shenanigans. I am very pleased you are finding it helpful.

Edited July 28, 2025Jul 28 by Reset XPDR

Not sure if this is an issue or by design but when I run with FPS Tolerance mode everything is good when I keep the AutoFPS window on top. The moment I minimise it or bring the sim to the front it seems to stop updating the LOD.

For example, I had TLOD on 100 on the ground and was climbing out. When I checked the AutoFPS window at around 8,000 AGL it was still showing LOD 100 but once in focus started to show the incremental steps of raising the LOD. I let it get to around 240 and refocused the sim. Climbed to cruise and opened AutoFPS and it was still on 240 but with the focus on it I could now see it climb slowly to 400. Worth noting that it doesn’t just jump up from 240 to 400 but still shows it going up in increments. That to me suggests there’s an issue?

Any ideas or am I doing something wrong?

1 hour ago, Speedbird 217 said:

Any ideas or am I doing something wrong?

Would probably be helpful to post what version of Auto FPS you are using and in what sim(s)?

Al

Edited July 29, 2025Jul 29 by ark