3 hours ago, Reset XPDR said:

The app doesn't permanently change any MSFS setting. It saves your current setting when starting, may change it while the app is running but, regardless of whether it changed it or not, it restores the originally saved setting on exit.

I started up MSFS tonight to change an icing setting, and while I was there, I checked my cloud setting and it was back on low. So this is three times in two days and it has never happened before. I am going to turn off the AutoFPS app, and see if it happens again. 

 

PS, checked my settings again, and found out that my TOD was lowered from around 120 to 50 in MSFS settings. 

Edited February 29, 20242 yr by Bobsk8

 

5 minutes ago, mmcmah said:

I for one appreciate what you're trying to achieve here with the flexibility - thank you! However, I'll have to play with it to see what number combinations work.

To that end, a new test version with the new TLOD Min on ground/landing logic can be downloaded here. I welcome all feedback on it, but I'd particularly like to hear from yourself, those who wanted to have a user adjustable Alt TLOD base and @Cpt_Piettwho stress tested my previous effort and found a big hole it. 🤪😁

New test version 29Feb240320Z:

• Complete rewrite of TLOD Min priority logic and calculations for TLOD Min on Ground/Landing:
  • Two additional parameters will utilise existing parameters used previously for TLOD Min on ground/landing, namely TLOD Min, TLOD Max and FPS Tolerance (aka LOD Step).
  • The first is Alt TLOD Base which, like Alt OLOD Base, is the altitude at, or below, which TLOD Min will be locked in for initial climb, final descent and landing. It will default to 1000 ft, like previously, but is settable between 100 and 10000 ft.
  • The second is Avg Descent Rate. This is used in combination with FPS Tolerance to determine the altitude band in which TLOD will be interpolated between TLOD min at the Alt TLOD base starting point and the lower of TLOD Max and the maximum TLOD your system can achieve while achieving at least your desired FPS target at a calculated top altitude. This band ensures that, if you descend at your set Avg Descent Rate or less, that the app can decrement TLOD from TLOD Max to TLOD Min by the Alt TLOD Base without exceeding the LOD Step rate. This doesn't mean you can't descend at a greater rate than this, its just the LOD steps will be greater than their nominal maximum for smoothness, hence you could introduce stutters from that greater LOD step rate. You can set a higher Avg Descent Rate to counter such behaviour, but that will mean a proportionally increased altitude band before TLOD Max is allowed when climbing. As with most settings, this one is a compromise and it is best to set it to a descent rate slightly higher than you would normally average on approach.
  • Once the calculated top altitude has been achieved, the app will switch to FPS priority and function as normal above that.

 

4 minutes ago, Bobsk8 said:

I started up MSFS tonight to change an icing setting, and while I was there, I checked my cloud setting and it was back on low. So this is three times in two days and it has never happened before. I am going to turn off the AutoFPS app, and see if it happens again. 

Did you set your cloud quality without the app running, not just minimised to the system tray, like I suggested?  Also is the cloud setting on low with the app running and, if so, does the app show it as red? If so, it will restore to medium when the app exits.

Also, message me the contents of your log file so I can tell you precisely what's going on.

Edited February 29, 20242 yr by Reset XPDR

14 minutes ago, Reset XPDR said:

Did you set your cloud quality without the app running, not just minimised to the system tray, like I suggested?  Also is the cloud setting on low with the app running and, if so, does the app show it as red? If so, it will restore to medium when the app exits.

Also, message me the contents of your log file so I can tell you precisely what's going on.

I had it turned off, when I set the clouds to medium. I now just tried to uninstall it, per your instructions, of running the installer and selecting remove, and it comes up with an error , and won't let me uninstall it. It must have done something, because now the app  won't even start. Can I just delete the entire folder that it is in?

 

 

Edited February 29, 20242 yr by Bobsk8

1 minute ago, Bobsk8 said:

I had it turned off, when I set the clouds to medium. I now just tried to uninstall it, per your instructions, of running the installer and selecting remove, and it comes up with an error , and won't let me uninstall it. It must have done something, because now the app  won't even start. Can I just delete the entire folder that it is in?

Yes that will get rid of it, plus you should also delete any icon it put on your desktop. Sorry it didn't work out for you.

1 hour ago, Reset XPDR said:

 

To that end, a new test version with the new TLOD Min on ground/landing logic can be downloaded here. I welcome all feedback on it, but I'd particularly like to hear from yourself, those who wanted to have a user adjustable Alt TLOD base and @Cpt_Piettwho stress tested my previous effort and found a big hole it. 🤪😁

New test version 29Feb240320Z:

• Complete rewrite of TLOD Min priority logic and calculations for TLOD Min on Ground/Landing:
  • Two additional parameters will utilise existing parameters used previously for TLOD Min on ground/landing, namely TLOD Min, TLOD Max and FPS Tolerance (aka LOD Step).
  • The first is Alt TLOD Base which, like Alt OLOD Base, is the altitude at, or below, which TLOD Min will be locked in for initial climb, final descent and landing. It will default to 1000 ft, like previously, but is settable between 100 and 10000 ft.
  • The second is Avg Descent Rate. This is used in combination with FPS Tolerance to determine the altitude band in which TLOD will be interpolated between TLOD min at the Alt TLOD base starting point and the lower of TLOD Max and the maximum TLOD your system can achieve while achieving at least your desired FPS target at a calculated top altitude. This band ensures that, if you descend at your set Avg Descent Rate or less, that the app can decrement TLOD from TLOD Max to TLOD Min by the Alt TLOD Base without exceeding the LOD Step rate. This doesn't mean you can't descend at a greater rate than this, its just the LOD steps will be greater than their nominal maximum for smoothness, hence you could introduce stutters from that greater LOD step rate. You can set a higher Avg Descent Rate to counter such behaviour, but that will mean a proportionally increased altitude band before TLOD Max is allowed when climbing. As with most settings, this one is a compromise and it is best to set it to a descent rate slightly higher than you would normally average on approach.
  • Once the calculated top altitude has been achieved, the app will switch to FPS priority and function as normal above that.

 

Fantastic modifications to the code! Thank you again. I have my sim set to 64fps max through NCP, most settings on Ultra and running 4k on a 4090, along with DLSR 1.78x, Ultra Quality DLSS. I did circuits around KJFK in an F-14 so that I could gain/lose altitude quickly or slowly as per the particular test. I was using PSXT/ReatTraffic with a 30nm radius around the airport for in air traffic and 30% of the parking spots filled with static aircraft. All told, there were 70 live aircraft in the air and 80 parked (static and live) aircraft at the airport. It was a heavy test and my FPS generally varied between 45-64.

I have my target FPS at 40,,,, FPS tolerance at 5%, the new Alt TLOD base at 500 (tried 1000, but preferred 500), Descent rate at 1500fpm (tried the default 2000, but 1500 seemed to work better), TLOD 100/400 and OLOD 600@1000 and 100@5000.

This combination worked very well and I tweaked here and there to get to it, but not too much. I will continue to play with it, but I think that the new parameters work well. I did get some heavy stutters from time to time, but that was when I also had Decrease Cloud Quality selected. I generally run the clouds on High, but I had been testing Ultra lately. I therefore set the clouds on Ultra and checked the box. I noticed that it kept trying to vary the clouds level (I had set the recovery TLOD to 200, but I'm not sure if that was right). Anyway, once I unchecked the Decrease Cloud Quality box, I experienced no more stutters and then I changed to High for good measure.

I think the results were really really good in what is a challenging scenery (iniBuilds KJFK), a challenging area, and lots of injected traffic.

24 minutes ago, mmcmah said:

I think the results were really really good in what is a challenging scenery (iniBuilds KJFK), a challenging area, and lots of injected traffic.

That is great to hear. I was a bit worried that its simplicity might come back to bite me but I have tried many different numbers in those two new parameters and it just does what it is supposed to do. I've settled on Alt TLOD base 100 ft and the default Avg Descent Rate of 2000 fpm and it worked great in a short Concorde flight I just did. Thanks for the feedback!

Edited February 29, 20242 yr by Reset XPDR

Hi @Reset XPDR ! and big thanks for your precious contribution to the Community !!!

ASOBO should hire ya ! 😉

Well, I am still trying to decide if I should go for it, get your App, try to configure it properly and try the results, mostly because since I have hat in today's standards can be called a low profile machine (described in my Sig) and have been using it with the DLSS-FS3 trick (version 0.90) in DX12, with VSync OFF in sim but frames set in Nvidia Inspector (or through the NCP to Adaptive Half Refresh Rate, giving me 30 FPS in my 60 Hz non G-Sync monitor, I believe it will probably not do a big difference, because I don't experience lag or stutters, have Graphic options mostly  between LOW and at most HIGH settings, and the only scenery installed is WU12 Iberian Peninsula... 

One of the things I would like to know is if setting "Target PC FPS" to 30 your App will take care of the half refresh rate and I can then only set VSync to ON in NCP or Nvidia Inspector, or if I still need to use Adaptive Half Refresh Rate ?

Thank you !

Edited February 29, 20242 yr by jcomm

Why does the TLOD stay at 200, if the setting in the main menu is set too max 400, doesn't matter what altitude you flying fl200 and above?

Still have a basic question:

If not using the expert option: Are some of the settings of this option also valid if expert is not ticked?

If not, which settings does the app use in non-expert?

Maybe the answer is hidden in the description, but so much information ...

Thanks!

Small question, how can I adjust the App Window. It is too small for me xD

40 minutes ago, kurtb said:

Why does the TLOD stay at 200, if the setting in the main menu is set too max 400, doesn't matter what altitude you flying fl200 and above?

Probably because your FPS target is too high, so the app is staying down the low end of your TLOD range. You have to set a realistic FPS target for it to work with.

16 minutes ago, mobiel said:

Small question, how can I adjust the App Window. It is too small for me xD

Try adjusting the high DPI settings on the second tab under properties when you right click on the app.

1 hour ago, jcomm said:

Hi @Reset XPDR ! and big thanks for your precious contribution to the Community !!!

ASOBO should hire ya ! 😉

Well, I am still trying to decide if I should go for it, get your App, try to configure it properly and try the results, mostly because since I have hat in today's standards can be called a low profile machine (described in my Sig) and have been using it with the DLSS-FS3 trick (version 0.90) in DX12, with VSync OFF in sim but frames set in Nvidia Inspector (or through the NCP to Adaptive Half Refresh Rate, giving me 30 FPS in my 60 Hz non G-Sync monitor, I believe it will probably not do a big difference, because I don't experience lag or stutters, have Graphic options mostly  between LOW and at most HIGH settings, and the only scenery installed is WU12 Iberian Peninsula... 

One of the things I would like to know is if setting "Target PC FPS" to 30 your App will take care of the half refresh rate and I can then only set VSync to ON in NCP or Nvidia Inspector, or if I still need to use Adaptive Half Refresh Rate ?

Thank you !

The app only really works if it has some headroom above the target FPS, normally 10%, for the automation to do its work.  This can cause tearing on older monitors but the only way to find out is to try it. I suggest you set a target FPS of 27 (ie. 10% lower than 30 Hz half sync).

10 minutes ago, Reset XPDR said:

Try adjusting the high DPI settings on the second tab under properties when you right click on the app.

That does not work