6 hours ago, f.skywalker said:

Smal information.

v0.4.4.3-test1 gives me allways medium clouds and set my clouds allways to medium.

Nothing relating to clouds changed in 0.4.4.3-test1. Are you setting your clouds before you start AutoFPS, because changing them after it is running will not stick? If you are still having an issue, message me your log file.

This has been such a wonderful program!   My mid-level machine is so smooth... even VR is improved!  No way I can swing a new GPU.  Thank you Reset!    Question from the "I overlook the obvious" department.  Do I need to run GPU-Z everytime prior to AutoFPS?

1 hour ago, Reset XPDR said:

Nothing relating to clouds changed in 0.4.4.3-test1. Are you setting your clouds before you start AutoFPS, because changing them after it is running will not stick? If you are still having an issue, message me your log file.

I go  back to 0 4.4.2 and no Problems.  Next time when i get this problem  i give you the logfile.

Frank from EDDM

1 hour ago, R1200RTPilot said:

This has been such a wonderful program!   My mid-level machine is so smooth... even VR is improved!  No way I can swing a new GPU.  Thank you Reset!    Question from the "I overlook the obvious" department.  Do I need to run GPU-Z everytime prior to AutoFPS?

If you want VRAM overflow protection you do. If you set GPU-Z up as the readme recommends, you never have to worry about explicitly running it as it will always be there in the background:

• Recommended GPU-Z settings are to minimise on close, load at windows startup (minimised), and to minimise to the system tray on the general tab, and refresh sensors while GPU-Z is in the background on the sensors tab.

29 minutes ago, f.skywalker said:

I go  back to 0 4.4.2 and no Problems.

I did the same this afternoon.  In my go-to aircraft, the Hjet, only with my custom cockpit camera views, I started with 4.4.3 experiencing what I could only describe as micro stutters when calling a view that zooms in on any particular portion of the panel. The zoom came in microsecond increments instead of smoothly.  To confirm, I exited, rebooted my system, then tried the same starting 2024 environment.  Same result.  I then reverted to 4.4.2 RC, rebooted. Started the same flight, same conditions. Back to smooth camera transitions.

I prefer to stay with 4.4.2 RC and forego any testing and reporting.  I spend too much of my available time trying this and trying that. Time to log some serious hours.

I absolutely love this app, fully support it. It is now essential. Can't do without! I do at this point fear over-engineering.  Just being honest and supportive.

32 minutes ago, fppilot said:

I did the same this afternoon.  In my go-to aircraft, the Hjet, only with my custom cockpit camera views, I started with 4.4.3 experiencing what I could only describe as micro stutters when calling a view that zooms in on any particular portion of the panel. The zoom came in microsecond increments instead of smoothly.  To confirm, I exited, rebooted my system, then tried the same starting 2024 environment.  Same result.  I then reverted to 4.4.2 RC, rebooted. Started the same flight, same conditions. Back to smooth camera transitions.

I prefer to stay with 4.4.2 RC and forego any testing and reporting.  I spend too much of my available time trying this and trying that. Time to log some serious hours.

I absolutely love this app, fully support it. It is now essential. Can't do without! I do at this point fear over-engineering.  Just being honest and supportive.

This is strange because the only thing that changed in 0.4.4.3-test1 that could remotely affect smoothness is that log sim values is now enabled by default, but that event only happens every 10 seconds and could not possibly induce microsecond increments.

Nonetheless, if you have found a version that you are happy with stick with that, noting that if a future MSFS version breaks app compatibility then you may be required to update.

I'm making good progress on Phase 2 of the new FPS Cap automation mode, namely in non-expert mode to have the app automatically detect when an FPS cap is in use then to use FPS Cap automation mode automatically, thus improving the utility of non-expert mode. It does this by monitoring the FPS over the settling period then considers an FPS cap is in use if FPS is very stable right around the target FPS that has been set.

Fear not those using expert settings as it lays dormant in this mode. Also, the trigger conditions are pretty tight, with no more than +-1 FPS peak over the settling period and no more than 0.1 FPS average fluctuation, so unless your setup is that stable it currently will not activate.

Here's what it looks like when activated:

I am still tweaking the activation logic, which may currently be a bit tight, and the base settings compared to the FPS sensitivity automation mode is has always used to date, but it is looking very promising. Stay tuned.

22 hours ago, Reset XPDR said:

This is strange because the only thing that changed in 0.4.4.3-test1 that could remotely affect smoothness is that log sim values is now enabled by default, but that event only happens every 10 seconds and could not possibly induce microsecond increments.

OK. So back to 4.4.2 RC and all is well. Removed all MSFS addons and upgraded again to 4.4.3 T1.  All still well.  Reinserted same addons.  Still good with 4.4.3 T1.  Go figure.  Thank you for the challenge.

This 2024 is really fickle.

Looks like 4.4.3 T1 needs an update along with the latest version of Lossless Scaling.  With LSFG 3.0, the app only shows x1 when I have Lossless set to X2 or X3.

1 hour ago, rjack1282 said:

Looks like 4.4.3 T1 needs an update along with the latest version of Lossless Scaling.  With LSFG 3.0, the app only shows x1 when I have Lossless set to X2 or X3.

Thanks for bringing this to my attention. It should be a relatively simple update so I hope to have a test version out with it in a day or so.

@rjack1282I've managed to get it working and detecting the multiplier with LSFG 1.1, 2.3 and 3.0, including custom multipliers, but test2 is not quite in a state to release yet due to other changes in progress. In the interim, just set your target FPS to be what it would be without LSFG running and everything should work as normal.

2 hours ago, Reset XPDR said:

@rjack1282I've managed to get it working and detecting the multiplier with LSFG 1.1, 2.3 and 3.0, including custom multipliers, but test2 is not quite in a state to release yet due to other changes in progress. In the interim, just set your target FPS to be what it would be without LSFG running and everything should work as normal.

Thanks a lot.  That is work-around I have been using and it basically works exactly the same that way anyway.

0.4.4.3-test3 is now available to download here. There's quite a few changes in it, but they basically boil down to:

• LSFG detection is now working again, even if you wish to choose ridiculously high custom multipliers like pictured.
• A new FPS Cap TLOD automation method has been introduced, which is essentially a specific configuration of the existing Auto TLOD method, that works well with FPS caps (eg, Vsync, VR motion reprojection).
• Non-expert mode will use the new FPS Cap mode if the FPS being read over 10 seconds is stable at the target FPS, but will fall back to FPS sensitivity otherwise. This feature is a work in progress but seems to be working well so far.
• Status line update to show FPS Cap mode when active and auto decluttering when info would otherwise overflow the line.

As always, feedback on these changes is welcome.

Edited January 11, 20251 yr by Reset XPDR

4 hours ago, Reset XPDR said:

0.4.4.3-test3 is now available to download here.

Hi, the download gives the test 2 version, not test 3. Also, when I run the test 2 version I get a MSFS compatibility test failed pop up and the app closes.

Edited January 11, 20251 yr by Harrier77

Hi, everyone,

I've downloaded the 0.4.4.3-test3, but it seems it's the previous version test2 instead.

Greetings