1 hour ago, GSalden said:

Imho it would be better to have one version than two .

Myself I do not use the FPS or Cloud part of the app. 

If you are able to come up with an automated version that would be welcome. Just a minimum LOD and maximum LOD where the app the LOD values changes on how fast the tiles are being loaded/unloaded. The max LOD value will only be reached if achievable ..

Surely with the FPS/Cloud part so others who use this can benefit from this too.

Btw : if FPS LOD is used icw FPS Clouds which one drops the value first wheh FPS is going down ?

Thavks for your great work.

I'll try and rephrase my earlier response. The two versions are to cater for two different audiences: one who regularly like to change settings to achieve optimal performance and the other who likes it to be more click and go and deliver an improved, but not necessarily as optimal as making the settings themselves, experience. You can use either one, or even both, just not at the same time!

Edited February 14, 20242 yr by Reset XPDR

3 minutes ago, Reset XPDR said:

FPS adaption reduces your LODs, and clouds if enabled, by a specified amount if MSFS falls below an FPS you consider acceptable with the aim to restore acceptable performance, even if it costs you some graphical detail.

Thanks. So without FPS adaption - will the LODs change at all?

Just now, Cpt_Piett said:

Thanks. So without FPS adaption - will the LODs change at all?

Yes, they will change in accordance with the tables you have set. It's all in the readme on github.

2 hours ago, Reset XPDR said:

How's this for a simple UI concept?

First: thank you very much for your work for us here!!! Great!

 

I would also like the slick UI. But with a standard value for TLOD and OLOD. This, what you mention is set in the sim ... but I wouldn't want to switch into the sims settings to see what is set.
this should be in the current "sim settings" window, where you have then a setable target TLOD and target OLOD. just as a suggestion.

 

 

Another point with my setup are about the target FPS: I have several monitors, but MSFS is just running on one screen. Meaning, when I click into another window, FPS differ in your app (normally half).
Don't know if it could be solved somehow - maybe if MSFS is not active window, just double the FPS number or whatever.
It is not a big issue ...

11 minutes ago, guenseli said:

I would also like the slick UI. But with a standard value for TLOD and OLOD. This, what you mention is set in the sim ... but I wouldn't want to switch into the sims settings to see what is set.
this should be in the current "sim settings" window, where you have then a setable target TLOD and target OLOD. just as a suggestion.

 

I did originally consider doing it that way, but I wanted to make the UI really simple. It's not too hard to put it in, but I am concerned that some of the intended users won't even know what LOD is, never mind T and O variants thereof. I'll keep it in mind though.

Edit: I could include it in preset speak, ie. I could have a drop down list that has low, medium, high, ultra and maybe custom. The presets could show the LODs in brackets eg. High (100). Custom could make text boxes appear below where the LODs could manually be entered. What do you think of that?

Edited February 14, 20242 yr by Reset XPDR

1 hour ago, GSalden said:

Btw : if FPS LOD is used icw FPS Clouds which one drops the value first wheh FPS is going down ?

If you mean the new simpler app, that depends on whether GPU or CPU loaded. If the former, clouds will drop first, if the latter it will be LODs first. I just need to detect GPU load first, which currently eludes me (well I can do it but the app takes up to 20% CPU resources doing so, which is a no go).

2 hours ago, Reset XPDR said:

How's this for a simple UI concept?

Please don't forget those without a GSync monitor. If you use a monitor with a constant refresh rate you need to keep your sim FPS constantly matching that monitor's refresh rate or a divider thereof. So you either use VSync or an extrernal limiter to keep your FPS constant, for example at a fixed limit of 30 FPS with a 60hz monitor. Whenever your sim FPS would be below or above 30 FPS you would see stutters and/or tearing because the sim FPS don't match the monitor's refresh rate.

When your new mod would keep FPS within a range of say 27 - 33 FPS by adjusting LODs that would lead to fluctuating FPS not matching the monitor's refresh rate all the time, so a very stuttery experience for those with a constant refresh rate monitor.

So unless you find a way to adjust LODs before FPS drop below the fixed limit (by somehow reading the remaining headroom of the CDU/GPU, as I suggested before), please keep supporting the AGL-dependant LOD-tables.

Thanks again for your ongoing work.

 

1 minute ago, RALF9636 said:

When your new mod would keep FPS within a range of say 27 - 33 FPS by adjusting LODs that would lead to fluctuating FPS not matching the monitor's refresh rate all the time, so a very stuttery experience for those with a constant refresh rate monitor.

So unless you find a way to adjust LODs before FPS drop below the fixed limit (by somehow reading the remaining headroom of the CDU/GPU, as I suggested before), please keep supporting the AGL-dependant LOD-tables.

I agree and you have just demonstrated why someone like you needs the swiss knife version, which I will continue to update, to meet your needs. This new version would likely be not suitable for you, and that's fine too.

9 hours ago, Reset XPDR said:

I'm thinking of making an Auto LOD spin off of this app where you set a target FPS band and upper and lower LOD limits and it adjusts your LODs, and possibly even cloud quality

That's great for me, as that's how I use your tool at the moment. I have one LOD set for 0 AGL, and use the FPS adaptation function to reduce it and/or the cloud details.

25 minutes ago, Reset XPDR said:

What do you think of that?

perfect!

 

Does the reduced version will also reduce cloud details leven itself?
(However, this I does not want to have happen, maybe there's an option to tick that. But on the other side I can then use the extended UI version)

4 minutes ago, guenseli said:

perfect!

 

Does the reduced version will also reduce cloud details leven itself?
(However, this I does not want to have happen, maybe there's an option to tick that. But on the other side I can then use the extended UI version)

I don't know yet. I will only do cloud quality if its GPU bound trigger condition is met and GPU load is a work in progress. And, yes you can still use the full strength version to tickle any "no cloud quality change for sure" itch.

6 hours ago, Reset XPDR said:

I did originally consider doing it that way, but I wanted to make the UI really simple. It's not too hard to put it in, but I am concerned that some of the intended users won't even know what LOD is, never mind T and O variants thereof. I'll keep it in mind though.

Edit: I could include it in preset speak, ie. I could have a drop down list that has low, medium, high, ultra and maybe custom. The presets could show the LODs in brackets eg. High (100). Custom could make text boxes appear below where the LODs could manually be entered. What do you think of that?

I think that's a better solution. In my opinion, even the simpler app should allow setting TLOD and OLOD according to the expected total GPU/CPU load (GA x airliner, busy or regional airport, traffic amount etc.). Changing this in the MSFS settings could be cumbersome. 

It is possible that some users may not know what TLOD or OLOD is, but I would take into account that 1) these are the same settings that MSFS already has, and 2) the form of distribution of the application itself, i.e. downloading the application from Github, already assumes a certain degree of user awareness. 

7 hours ago, Reset XPDR said:

I could have a drop down list that has low, medium, high, ultra and maybe custom.

I absolutely would want to retain full control over the TLOD and OLOD settings (as we do now) using a 'custom' or 'advanced' setting in the app.

Otherwise, yes. Preset options in a drop down list is a great idea.

Over simplifying could inadvertently lose the beauty of this mod, namely customization to the users system, aircraft, type of flying (tubes v GA), traffic mods, third party add-ons, etc.

Presets could be ok, as long as there are "advanced" options as mentioned. 

Like lots of things in this MSFS hobby, this one requires a little study and I think that's not a bad thing.      

       

If anyone is on the SU15 beta, can you let me know if DynamicLOD_ResetEdition 0.3.7 is working OK and doesn't show the message Incompatible MSFS version - Sim Values read only

Also, could you paste the section of log file that shows memory manager entries at the start eg.

2024-02-15 07:02:01.012 [DBG] [ MemoryManager:MemoryManager      ] Trying offsetModuleBase: 0x004B2368
2024-02-15 07:02:01.116 [DBG] [ MemoryManager:MemoryManager      ] Boundary tests passed - memory writes enabled

I want to see if the offsetModuleBase changed at all.

Edited February 14, 20242 yr by Reset XPDR