1 hour ago, Reset XPDR said:

My goal is to keep the UI as uncluttered as possible, even when I add new features, which I think I have acheived with non-expert mode where it looks pretty much the same as when I first made the app over a year ago, yet it is significantly more complex and capable in what it does behind the scenes. In fact, I will probably keep the exact same UI for non-expert mode, ie radio buttons for IFR and VFR, even if I introduce a drop list for extra profiles in expert mode.

Is there a basic guide as I couldn't quite understand aspects of the Readme?

Areas I'd like to understand is the different Auto Methods and why each may work better than others?

I understand Auto TLOD is probably like the original mod but it's the FPS variants I don't understand.

Same for Auto Target FPS or manually entering a fps. Is this when the app is meant to start making adjustments? 

My TLOD min is set to 50 but even on the ground and getting smooth frames it often drops to 25.

Finally I know we had discussions on the VRAM+ when it is enabled does it override everything? Even if I manually select Custom on the Reduction Selection Suite and manually choose certain items it drops them all

Edited April 22, 20251 yr by cj-ibbotson

53 minutes ago, cj-ibbotson said:

Is there a basic guide as I couldn't quite understand aspects of the Readme?

Areas I'd like to understand is the different Auto Methods and why each may work better than others?

I understand Auto TLOD is probably like the original mod but it's the FPS variants I don't understand.

Same for Auto Target FPS or manually entering a fps. Is this when the app is meant to start making adjustments? 

My TLOD min is set to 50 but even on the ground and getting smooth frames it often drops to 25.

Finally I know we had discussions on the VRAM+ when it is enabled does it override everything? Even if I manually select Custom on the Reduction Selection Suite and manually choose certain items it drops them all

Everything you ask is covered in the readme. It should not be hard to find what you want as it is written in increasing level of detail and in dot point form to be succinct but still describe features fully.  eg.

Quote

Areas I'd like to understand is the different Auto Methods and why each may work better than others?

Simple outline:

• Auto Method - FPS Sensitivity generally gives the best results for most users and hence is the default. Use FPS Tolerance if you experience stuttering issues. Use Auto TLOD if you want a DynamicLOD-like experience. Use FPS Cap if you use an FPS cap on your system.

Detailed outline of the first option:

• FPS Sensitivity - smaller changes more often.
  • Determines how sensitive the app will be to the variance between your current and target FPS.
  • Also determines the largest TLOD step size you will see, being double the FPS sensitivity number.
  • The lower the setting the smaller the changes will be, which is useful if you are experiencing stuttering with the default value of 5. Vice versa for higher settings. (1 - 20 allowable)

etc.

I am sorry to say that if you are struggling to comprehend it, I suggest that expert mode is not for you and that you stick with the simple how-to guidance for non-expert mode provided in the FAQ.

As you mentioned, we have discussed VRAM+ before. Yes it is intentionally aggressive and affects the full suite of settings. If you are regularly having VRAM+ triggered settings reduction then quite simply your MSFS settings are too high for the amount of VRAM your GPU has. Either turn them down or uncheck VRAM+ and deal with the consequences of VRAM overflow.  If neither of these yield an acceptable result, then this app is not for you.

Edited April 22, 20251 yr by Reset XPDR

This is normal when I use VRAM+ and request automatic parameter reduction in custom mode. I just want it to lower the trees and therefore the TLOD and OLOD.

Except it reduces several parameters, especially the clouds...

I'd like it not to affect the clouds, because sometimes it goes from high to low, and it's cool to see it in the sim; it ruins the immersion. I really want it to lower the trees and the TLOD and OLOD.

Thanks again for your involvement; your app really changes the way you fly with MSFS 2024.

40 minutes ago, Reset XPDR said:

Everything you ask is covered in the readme. It should not be hard to find what you want as it is written in increasing level of detail and in dot point form to be succinct but still describe features fully.  I am sorry to say that if you are struggling to comprehend it, I suggest that expert mode is not for you and that you stick with the simple how-to guidance for non-expert mode provided in the FAQ.

As you mentioned, we have discussed VRAM+ before. Yes it is intentionally aggressive and affects the full suite of settings. If you are regularly having VRAM+ triggered settings reduction then quite simply your MSFS settings are too high for the amount of VRAM your GPU has. Either turn them down or uncheck VRAM+ and deal with the consequences of VRAM overflow.  If neither of these yield an acceptable result, then this app is not for you.

I'll have another look at the readme but recently when using the find option it wouldn't find key words. I do have a 7800x3d, 64 gb of ddr5 memory and a 3080ti with 12 Gb vram. Tests have only been at LEBB in the Fenix and performance was often dropping through the floor. I briefly tested a non third part livery and have gone back quite a few drivers to one recommended. There's a lot of bad press on the last few Inc videos by JayzTwoCents and GamersNexus. Quick test showed better results. Settings in Fenix all medium so nothing heavy

Edited April 22, 20251 yr by cj-ibbotson

13 minutes ago, cj-ibbotson said:

I'll have another look at the readme but recently when using the find option it wouldn't find key words.

It is all there, I assure you. Please see my edited post above where I have provided one example of simple and then detailed info on a feature you seek. The find option in any major browser if using the web version, or notepad if you are using the supplied text readme, should easily find other keywords.

Re drivers and SU1 and SU2 effect on VRAM use, yes it is a pretty poor state that a GPU with 12GB VRAM can be so easily pushed into VRAM overflow territory by MSFS, but that's just the way it currently is. VRAM+ does not start reducing settings until you hit 98% VRAM use with default settings, so the app keeps its reduction settings desires at bay as long as it can before it has to act.

Edited April 22, 20251 yr by Reset XPDR

12 minutes ago, Axis3600 said:

This is normal when I use VRAM+ and request automatic parameter reduction in custom mode. I just want it to lower the trees and therefore the TLOD and OLOD.

Except it reduces several parameters, especially the clouds...

I'd like it not to affect the clouds, because sometimes it goes from high to low, and it's cool to see it in the sim; it ruins the immersion. I really want it to lower the trees and the TLOD and OLOD.

Thanks again for your involvement; your app really changes the way you fly with MSFS 2024.

As recently mentioned, VRAM+ is intentionally aggressive and affects the full suite of settings that can be reduced, because it usually takes that to bring an impending VRAM overflow under control. If you only want the custom mode setting of trees and TLOD and OLOD and nothing else ever, then use your existing settings but uncheck VRAM+ but with the obvious consequence that you will no longer be protected from VRAM overflows.

Edited April 22, 20251 yr by Reset XPDR

Okay, and can a VRAM overflow cause a CTD? Because I've never had one on SU1, but on SU2 I have the impression that a VRAM overflow causes a CTD, which was not the case on SU1.

12 minutes ago, Axis3600 said:

Okay, and can a VRAM overflow cause a CTD? Because I've never had one on SU1, but on SU2 I have the impression that a VRAM overflow causes a CTD, which was not the case on SU1.

Yes a VRAM overflow can cause a CTD if performance gets so bogged down that something critical times out internal to the sim for which there isn't an error handler to deal with it. Whether SU1 or SU2 is more prone to CTDs I do not know but in my experience it is best to avoid situations that invite them, such as VRAM overflow and associated performance drops.

Edited April 22, 20251 yr by Reset XPDR

3 hours ago, Reset XPDR said:

It is all there, I assure you. Please see my edited post above where I have provided one example of simple and then detailed info on a feature you seek. The find option in any major browser if using the web version, or notepad if you are using the supplied text readme, should easily find other keywords.

Re drivers and SU1 and SU2 effect on VRAM use, yes it is a pretty poor state that a GPU with 12GB VRAM can be so easily pushed into VRAM overflow territory by MSFS, but that's just the way it currently is. VRAM+ does not start reducing settings until you hit 98% VRAM use with default settings, so the app keeps its reduction settings desires at bay as long as it can before it has to act.

Ok thanks, weirdly when I skimmed through the Readme the other day I did not see any mention of 'tolerance' or 'sensitivity' even when using the Find option in Notepad.  I have started to read it all more concisely.  I have the latest test version at the moment.

I assume as I use the newly discovered frame rate limiter in the UserOpt.cfg file that I should use FPS Cap method?  I have that set to 30 then use the FSR3 FG option to double to 60

4 hours ago, cj-ibbotson said:

Ok thanks, weirdly when I skimmed through the Readme the other day I did not see any mention of 'tolerance' or 'sensitivity' even when using the Find option in Notepad.  I have started to read it all more concisely.  I have the latest test version at the moment.

I assume as I use the newly discovered frame rate limiter in the UserOpt.cfg file that I should use FPS Cap method?  I have that set to 30 then use the FSR3 FG option to double to 60

Yes, FPS Cap mode is best if you use an FPS limiter and your FPS sits at the set limit most of the time.

Your continued work on this is so much appreciated Reset XPDR! I have been trying to use the different auto methods but since I use an FPS limiter within the Varjo Aero software, I think FPS Cap mode works best with the least stutters. Question - even I have inserted the TLOD at max 250, the app often allows TLOD to go as high as 500 which causes the CPU to work really hard. I understand that the app let it go that high since it able to maintain the FPS cap. Is there a way to still limit the TLOD to the 250?

1 hour ago, kiwipilot1977 said:

Your continued work on this is so much appreciated Reset XPDR! I have been trying to use the different auto methods but since I use an FPS limiter within the Varjo Aero software, I think FPS Cap mode works best with the least stutters. Question - even I have inserted the TLOD at max 250, the app often allows TLOD to go as high as 500 which causes the CPU to work really hard. I understand that the app let it go that high since it able to maintain the FPS cap. Is there a way to still limit the TLOD to the 250?

Yes, you can either:

• Stay in FPS Cap mode but reduce your TLOD Top to half of the maximum you ever wish to see, so in your case I'd set it to 125 to see a max of 250. I know it is a little bit unintuitive, but that's one of the reasons TLOD Max is renamed to TLOD Top in AutoTLOD and FPS Cap modes because it is not actually the max that can be achieved.
• Switch to AutoTLOD mode and uncheck TLOD Base+, which will restrict your TLOD to the base / top range as it ignores FPS. The side effect of this is you can't use auto reduction and VRAM+ features because it needs an FPS target to function. 

I suggest trying the first option first.

Edited April 23, 20251 yr by Reset XPDR

49 minutes ago, Reset XPDR said:

Yes, you can either:

• Stay in FPS Cap mode but reduce your TLOD Top to half of the maximum you ever wish to see, so in your case I'd set it to 125 to see a max of 250. I know it is a little bit unintuitive, but that's one of the reasons TLOD Max is remained to TLOD Top in AutoTLOD and FPS Cap modes because it is not actually the max that can be achieved.
• Switch to AutoTLOD mode and uncheck TLOD Base+, which will restrict your TLOD to the base / top range as it ignores FPS. The side effect of this is you can't use auto reduction and VRAM+ features because it needs an FPS target to function. 

I suggest trying the first option first.

Brilliant, thank you very much. First option provides a smoother experience. I have set max TLOD to 125 and now getting a solid 250 in cruise. Cheers from NZ

 

I'm having a problem with version 0.4.4.9 test 1. Every time I restart MSFS, my settings are reset to default because the app regenerates the user.cfg file. It's clearly AutoFPS, because if I don't start the app, my settings remain.

33 minutes ago, mobiel said:

 

I'm having a problem with version 0.4.4.9 test 1. Every time I restart MSFS, my settings are reset to default because the app regenerates the user.cfg file. It's clearly AutoFPS, because if I don't start the app, my settings remain.

That shouldn't be happening. Could you please message me the contents of your log file, located in %appdata%\MSFS_AutoFPS\log, associated with when this occurs so I can see what is going on. 

Also, if possible can you also send me the contents of your UserCfg.opt file, located in the MSFS root directory for your user, after you close MSFS when AutoFPS has been running and before it gets rebuilt by MSFS.

Thanks

Edited April 23, 20251 yr by Reset XPDR