On 4/27/2024 at 4:19 PM, motishow said:

any news or updates?

No major updates of late but I have been working on a decrease cloud quality option in Auto TLOD automation mode that gets triggered on GPU load as reported by the GPU-Z companion app that must be running. This decreases cloud quality when your GPU load gets above a user set threshold (default 95%) and recovers your clouds when a user set lower threshold (default 80%) is achieved.

This may be useful for those running FPS caps, like I do now, and are hence using Auto TLOD automation mode with fixed TLOD and OLOD schedules. If anyone really wants to try it out, let me know and I will put up a test build on github.

Edited April 30, 20242 yr by Reset XPDR

4 hours ago, Reset XPDR said:

No major updates of late but I have been working on a decrease cloud quality option in Auto TLOD automation mode that gets triggered on GPU load as reported by the GPU-Z companion app that must be running. This decreases cloud quality when your GPU load gets above a user set threshold (default 95%) and recovers your clouds when a user set lower threshold (default 80%) is achieved.

That’s really clever and probably better than the previous approach. This will probably not come as a surprise, but I’d love to test it! 

And btw AutoTLOD works great. 

As requested @Cpt_Piett, AutoFPS v0.4.2.11-test can be downloaded here.

Summary of changes since v0.4.2.10:

• Added decrease cloud option for AutoLOD automation method with user definable cloud reduction and recovery GPU loads. Requires GPU-Z companion app to be running in order to provide the app with GPU load information.
• Revised GPU-Z gpu load reading to be 5 second average
• GPU-Z can now be started at any time and show GPU load in the app
• App will now remember whether it was visible in previous session and will restore that state on next startup.
• Moved sim value logging feature from mainwindow to LODController module so that if enabled sim values will be recorded even if app window is hidden.
• Fixed issue where MSFS could be incorrectly detected as being paused when over water at a near constant speed due to rounding.

Feedback is welcome.

 

Edited May 1, 20242 yr by Reset XPDR

41 minutes ago, Reset XPDR said:

As requested @Cpt_Piett, AutoFPS v0.4.2.11-test can be downloaded here.

Thanks! Btw the link is here (think you forgot to include it): https://github.com/ResetXPDR/MSFS2020_AutoFPS/releases/tag/v0.4.2.11-test

41 minutes ago, Reset XPDR said:

Feedback is welcome.

As always, I’ll report back 😊

Edited May 1, 20242 yr by Cpt_Piett

27 minutes ago, Cpt_Piett said:

Thanks! Btw the link is here (think you forgot to include it): https://github.com/ResetXPDR/MSFS2020_AutoFPS/releases/tag/v0.4.2.11-test

Oops, I'm out of form for posting new updates 😄Thankfully I can still edit my post so I have fixed it. Thanks for pointing it out! 👍👍

47 minutes ago, Reset XPDR said:

Oops, I'm out of form for posting new updates 😄Thankfully I can still edit my post so I have fixed it. Thanks for pointing it out! 👍👍

No worries! You'll get back into it in no time 😄 

It's working!

Screenshot should be pretty self-explanatory. Since I have a 4090, I had to increase the resolution to 6144x3240. 

Edited May 1, 20242 yr by Cpt_Piett

5 minutes ago, Cpt_Piett said:

No worries! You'll get back into it in no time 😄 

It's working!

Screenshot should be pretty self-explanatory. Since I have a 4090, I had to increase the resolution to 6144x3240. 

That's good to hear. The code to change cloud quality is the same as before but the trigger mechanism for this mode is GPU load not FPS, so it was only some minor tweaking to get it working.  The UI change was the most effort.

32 minutes ago, Reset XPDR said:

That's good to hear. The code to change cloud quality is the same as before but the trigger mechanism for this mode is GPU load not FPS, so it was only some minor tweaking to get it working.  The UI change was the most effort.

It's pretty efficient too - GPU load went from 100 to 93. Difference between high and ultra is not huge:

Edited May 1, 20242 yr by Cpt_Piett

8 hours ago, Reset XPDR said:

The only time the app should ever set the clouds on startup is if either the app or MSFS didn't shut down properly last time and it attempts to restore the last saved cloud quality setting. Otherwise, it will not set cloud quality ever on startup if decrease cloud quality is unchecked.

If it happens again, please message me a copy of the contents of the app's log file so I can see if I can work out what is going on.

Aahh in that case then I wonder if its because I ask Add-Ons linker to close the app for me (like I do with most apps), it might not be closing properly that way perhaps. I'll keep it in mind and test next time, thanks 

no matter what I try I have big stutters when the app changes TLOD.

 

I am using 0.4.2.10

Maybe I have some strange settings in MSFS compared to others With FG.

Using a 7900XTX monitor display on 60 HZ with freesync and in Game VSync enabled. I can see the app reads the FG FPS but I have tried 57 fps, autotarget and many other things, keep getting this big stutters related to TLOD changes.

 

7 hours ago, pilotter said:

no matter what I try I have big stutters when the app changes TLOD.

If you have sensitivity set too high, this can happen. I’ve set it to 5. 

I do get stutters occasionally when TLOD is changing, especially flying over Europe. Others have reported Europe as a “problem-area” stutter-wise, regardless of AutoFPS.

9 minutes ago, Cpt_Piett said:

If you have sensitivity set too high, this can happen. I’ve set it to 5. 

I do get stutters occasionally when TLOD is changing, especially flying over Europe. Others have reported Europe as a “problem-area” stutter-wise, regardless of AutoFPS.

sensivity is on 5, always wondered why Europe and US are so heavy on fps. New Zealand is the easiest on fps for me 🙂

@Reset XPDR

 

Maybe a little idea as a feature:

Would it be possible to program the window so that you can open and close the window from the "general" option part onwards so that only the small part "Sim Values" would be visible?

Of course you also have the Use Expert Options ticked aswell

Edited May 2, 20242 yr by mobiel

9 hours ago, mobiel said:

@Reset XPDR

 

Maybe a little idea as a feature:

Would it be possible to program the window so that you can open and close the window from the "general" option part onwards so that only the small part "Sim Values" would be visible?

Of course you also have the Use Expert Options ticked aswell

I'll have a look at it but I have to declare that UIs are my kryptonite so I'll try my best but no promises.

A workaround I already use for this is I just position the app window on my screen so that the bottom part is off screen to achieve a similar effect, so you may want to try this in the interim.

New test version 0.4.2.12-test available here

Changes in this version:

• @mobiel Added the ability to progressively hide parts of the UI when the app window is double clicked anywhere that is not a control. The first double click will hide the expert settings section (if applicable), the second will hide the general settings section and a third double click will restore all hidden settings sections.
• Added LOD Step Size setting to allow users experiencing stuttering issues with AutoTLOD automation mode to try different LOD step sizes. The default value is 5.
• Fixed bug introduced in 0.4.2.11-test that caused VFR profile changes to be saved to IFR profile when using AutoTLOD automation method.

First double click:

Second double click;

Edited May 3, 20242 yr by Reset XPDR