4 hours ago, Reset XPDR said:

Intended functionality is now mostly complete, pending any major issues found by other users that I need to fix, so I should be able to release 0.3.6 in the next day or so.

 

Thanks a lot for your continuing efforts.

I always struggled with the "TLOD PC/VR ..." line in the UI. But now I think it is just misleading.

Instead of

TLOD PC/VR 180/3  - OLOD PC/VR 70/3

it should look like this:

TLOD 180 - OLOD 70 - Cloud Quality 3.

 

Apart from that I'd like to share a thought I hope you might get some ideas from.

Your new "Cloud Recovery FPS" setting to me seems to be only useful without an FPS limit in the sim. So I assume you do not limit FPS. But I guess many people do use an FPS limit in the sim - at least most of those without a GSync monitor.

I always wondered if there are other parameters available to assess the current CPU and GPU headroom but the FPS. If you use an FPS limit you don't see from the the FPS if there is a lot of headroom left or if the FPS is just about to drop. If we could somehow measure the CPU and GPU load resp. headroom we would be able to lower the LOD setting BEFORE an FPS drop occurs (below the FPS limit in the sim). That would also enable us to introduce different settings for CPU- and GPU-limited scenarios (reducing cloud quality foremost gives more headroom for the GPU whereas reducing TLOD foremost gives more headroom for the CPU). And we wouldn't need the AGL-dependent settings anymore but could just use the current CPU resp. GPU load to adjust the settings.

Can you follow what I mean? Any ideas?

 

Edited January 31, 20242 yr by RALF9636

1 hour ago, RALF9636 said:

I always struggled with the "TLOD PC/VR ..." line in the UI. But now I think it is just misleading.

Instead of

TLOD PC/VR 180/3  - OLOD PC/VR 70/3

it should look like this:

TLOD 180 - OLOD 70 - Cloud Quality 3.

As mentioned in my original 0.3.6 post, this is a test version and I was using that line temporarily to show the cloud quality setting while testing, so it is not meant to be a permanent feature. The PC/VR nomenclature predates this test version and is there to show that PC and VR LODs are being changed to the same values. If I remove VR then people are going to keep asking me if it is VR compatible, so I am planning to leave it there or relocate it to the Sim Values title for that reason. If I do indicate the cloud quality, it will show as the setting name (eg. low, medium, high, ultra) rather than a number. Point noted and I will continue polishing this for clarity for all.

 

1 hour ago, RALF9636 said:

Your new "Cloud Recovery FPS" setting to me seems to be only useful without an FPS limit in the sim. So I assume you do not limit FPS. But I guess many people do use an FPS limit in the sim - at least most of those without a GSync monitor.

No I don't use an FPS limit, nor do most people I know who use MSFS for that fact. In any case, you can still use the cloud quality feature with the cloud recovery FPS set to 0 if you want, but as previously mentioned it can cause cycling in and out of FPS Adaption if you set it too low. If you can't find a setting that works, just turn off cloud reduction and the app will work just like before.

1 hour ago, RALF9636 said:

I always wondered if there are other parameters available to assess the current CPU and GPU headroom but the FPS. If you use an FPS limit you don't see from the the FPS if there is a lot of headroom left or if the FPS is just about to drop. If we could somehow measure the CPU and GPU load resp. headroom we would be able to lower the LOD setting BEFORE an FPS drop occurs (below the FPS limit in the sim). That would also enable us to introduce different settings for CPU- and GPU-limited scenarios (reducing cloud quality foremost gives more headroom for the GPU whereas reducing TLOD foremost gives more headroom for the CPU).

This is where it gets way too complicated just getting a reliable CPU and GPU load from MSFS, especially if you are using an FPS cap as it can look like one component is limiting FPS when it actually is not, let alone trying to anticipate an impending FPS drop and what to tweak to avert it. As such, I am not planning on heading too far down this path.

Edited January 31, 20242 yr by Reset XPDR

I was probably a bit too hard in shutting down that last idea, sorry @RALF9636. I did actually look at trying to obtain MSFS GPU load in the app, and even trialed some code to read it in, but the number I was getting was not consistent with CPU-Z so I gave up fairly readily. If anyone can point me to some good code to read reliable and accurate CPU and GPU load for a specific app like MSFS, I could take a look again.

On 1/29/2024 at 6:56 PM, Bond said:

Remember after you change it from 100 to 200 you need to Save it(click the S)

It worked thank you very much!

30 minutes ago, Reset XPDR said:

I was probably a bit too hard in shutting down that last idea, sorry @RALF9636. I did actually look at trying to obtain MSFS GPU load in the app, and even trialed some code to read it in, but the number I was getting was not consistent with CPU-Z so I gave up fairly readily. If anyone can point me to some good code to read reliable and accurate CPU and GPU load for a specific app like MSFS, I could take a look again.

I was confident you would give it a second thought. 😉

Hopefully some ideas will come up.

 

I've updated the UI in the 0.3.6 test version, same download link here, to revise the display of Sim Values to be hopefully a bit clearer.

Firstly on startup now you will see n/a as values instead of 0, because they are actually not available until simconnect gets connected and the session starts.

Secondly, I have grouped OLOD and TLOD together, with single values for each as they are set the same for VR and PC, and now show cloud quality for PC and VR, which can be set differently, as their actual textual description.

With FPS Adaption activated it looks like this:

If FPS Adaption is activated but you are not using decrease cloud quality, it will look like this:

2 hours ago, Reset XPDR said:

I've updated the UI in the 0.3.6 test version, same download link here, to revise the display of Sim Values to be hopefully a bit clearer.

I cannot keep up with your releases lol

You sir are an awesome individual for taking this on where the dev left off and creating a masterpiece. I have to say with the latest Nvidia drivers I updated too a couple days ago and this app I have never had such a butter smooth experience in the sim. I just left Zurich in the PMDG with a ton of FSLTL traffic and even taxiing to the active runway was sublime. When I arrive in Manchester I will be jumping in the Fenix and coming right back 🙂 

I have been lucky with my experience with the sim after I bit the bullet and purchased my 4090, your work has made it even better. I don't think I will ever need to upgrade my hardware again !!

Seriously, thank you for your hard work and taking time to evolve this awesome addon.

Richard

Edited January 31, 20242 yr by RJC68

Reset XDPR,

Been following this thread from the road.
 
Won’t get back home to fly for a while, but just reading about the updates has been amazing.

Agree with RJC68 that you’ve done incredible work. All of us have spend lots of hard earned $ over the years for mods and add-ons that do far far less.

Thank you for giving your time, effort and passion back to a community that greatly appreciates it.

Thank you!

Yeah, between this (still trying to tweak it) and the Frame Generation mod....my 2080ti has new life and my 8080ki7 is a lot happier as well.

Now I notice there are more potential settings including clouds? Thats even better

I've been recently discussing automatic VR mode detection with Fragtality and we are trying to get the right MSFS memory address that indicates VR mode is active, which is proving somewhat elusive. We have managed to get it working on my setup, which is the Steam version of MSFS with either Steam VR or OpenXR, but we'd like to know if it works on the MS Store MSFS version and any other VR client out there.

To that end, I have added some test VR detection code to the my latest 0.3.6 variant here which shows a label saying which graphics mode is active eg. PC and VR mode respectively:

 

Can I ask some of you using 0.3.6 currently that use VR to update to this latest test version and tell me whether the app correctly identifies whether you are in PC or VR Mode. When replying, please state which MSFS version you have (Steam or MS Store) and what VR client you are running (eg. SteamVR, OpenXR, occulus, etc.). Thanks.

BTW, there is no harm updating to this latest test version even if you don't use VR, as this is the only change since my last test version and it will work in PC mode without VR.

Thanks for all your hard work!  The latest 0.3.6 test version works as intended for me, it correctly identifies PC and VR modes.   MSFS MS Store version, OpenXR, Varjo Base. 

Edited February 2, 20242 yr by JDJ

Thank you very much for this amazing tool Sir @Reset XPDR

I was thinking that if it is possible to set the road traffic as we fly higher (the less road traffic down there).

 

9 hours ago, History said:

Thank you very much for this amazing tool Sir @Reset XPDR

I was thinking that if it is possible to set the road traffic as we fly higher (the less road traffic down there).

 

I am glad you are finding the app useful. In the name of simplicity and notable benefit, I'm not planning on incorporating any individual settings beyond the three we already have that do affect FPS and smoothness significantly, namely TLOD, OLOD and Cloud Quality. 

10 hours ago, JDJ said:

Thanks for all your hard work!  The latest 0.3.6 test version works as intended for me, it correctly identifies PC and VR modes.   MSFS MS Store version, OpenXR, Varjo Base. 

Thanks for the feedback. That is great news as I wasn't sure whether it would work properly with the MS Store version. If anyone else can confirm too that would be great.

I finally got my act together and created a github page with my current 0.3.6-test version of DynamicLOD, now known as DynamicLOD_ResetEdition based on Fragtality's 0.3.2 release, available to download as either the installer or source code.

As I have given the app a new name, so as not to create confusion between Fragtality's and my versions, the app will install in the same area as before but with a directory name DynamicLOD_ResetEdition and therefore won't overwrite any existing installations as it has done in the past. As such, I recommend you uninstall DynamicLOD first if you no longer wish to use previous versions, keeping the contents of the config file from it it you don't want to start with a fresh one and pasting them into the new config file. It's pretty easy to repopulate the LOD tables and make your other settings, so it's not the end of the world if you have to start fresh.

Please note that 0.3.6-test is, well, a test version so the source isn't as polished as it will be on release and does intentionally contain some quick and dirty code changes to trial new functionality. I will fix this up in due course.

Without further ado, my github page for DynamicLOD_ResetEdition is here. Let me know if you encounter any issues getting what you need with the transfer to this new hosting medium.