Im using DynamicLOD_ResetEdition. My manual TLOD levels just works. I fly GA and like to fly max of 3000ft. No stutters, when LOD´s are changing.

8 minutes ago, Corsten said:

Im using DynamicLOD_ResetEdition. My manual TLOD levels just works. I fly GA and like to fly max of 3000ft. No stutters, when LOD´s are changing.

If I am correct the developer advised to use just a few AGL levels as otherwise there is a continuous loading/unloading of terrain tiles.

And using Step Max for more smoother tiles loading.

Btw : this is the Auto FPS thread

Edited March 10, 20242 yr by GSalden

6 hours ago, Reset XPDR said:

Fair enough. I will stop putting out test releases until I get some feedback on what is currently out there.

Just wanted to test the Auto FPS feature of 0.4.2 and cannot find this test version for DL. 🧐

I want to see if this can squeeze performance a little more compared to Adaptive LOD which I am still using ( 4090 / 13.900k ) but without the framerate feature..

Edited March 10, 20242 yr by GSalden

9 minutes ago, GSalden said:

Just wanted to test the Auto FPS feature of 0.4.2 and cannot find this test version for DL. 🧐

I want to see if this can squeeze performance a little more compared to Adaptive LOD which I am still using ( 4090 / 13.900k ) but without the framerate feature..

The link to the latest 0.4.2 test version is on the previous page of this discussion. The direct link to the installer is here.

6 hours ago, Reset XPDR said:

Fair enough. I will stop putting out test releases until I get some feedback on what is currently out there.

I have just joined as a new forum member here on Avsim to specifically thank you and express my gratitude and appreciation for this wonderful tool that you've created. I prefer to use the stable version but if I do venture to experiment with any test version I will definitely provide feedback. Don't let your enthusiasm be dampened and keep up the good work. And once again, thank you.

32 minutes ago, Reset XPDR said:

The link to the latest 0.4.2 test version is on the previous page of this discussion. The direct link to the installer is here.

Thank you. Will try it today and report back here.

Question :

Up to now with Adaptive LOD I set oLOD for minimum to 50 and maximum 200. So increasing  with increasing altitude.

i did this because custom objects, like Dubai’s skyscrapers are visible at 20 mls away above 5000 ft.

Am I correct on this as you advise it the other way round : maximum on the ground and minimum at high altitude ?

 

 

1 hour ago, Armen said:

I have just joined as a new forum member here on Avsim to specifically thank you and express my gratitude and appreciation for this wonderful tool that you've created. I prefer to use the stable version but if I do venture to experiment with any test version I will definitely provide feedback. Don't let your enthusiasm be dampened and keep up the good work. And once again, thank you.

You are most welcome. My recent shove into the MSFS social media scene with these apps was quite unexpected and has resulted in a whole lot of unanticipated support effort that has been quite draining on me. I'd always wondered what it would be like to do such a thing and, now that I know, I am quite happy to chalk it up as experience and move on to something else.

In trying to finish it up as quickly as possible, I got a bit carried away with my test releases and may have alienated some of my most avid supporters, and to them I am truly sorry.

If you do get a chance to try the auto target FPS test version, I would appreciate your feedback, but I also appreciate your position of preferring stable versions and understanding if you don't want to do this. Please don't feel obliged to just because I responded to you.

48 minutes ago, GSalden said:

Thank you. Will try it today and report back here.

Question :

Up to now with Adaptive LOD I set oLOD for minimum to 50 and maximum 200. So increasing  with increasing altitude.

i did this because custom objects, like Dubai’s skyscrapers are visible at 20 mls away above 5000 ft.

Am I correct on this as you advise it the other way round : maximum on the ground and minimum at high altitude ?

 

 

There is ongoing controversy between which way to go with OLOD as altitude increases. I am in the camp that the higher I get the less detail I can see in any object anyway, especially in VR as the graphics are not as defined as they are in 4K+ desktop, so I decrease as I go up. Others, like you swear they can see such detail in far off distances the higher they get, so increasing OLOD makes sense to them. There is no right or wrong way, just do what you feel works best for you.

@Reset XPDR

Currentky in a flight from Amsterdam to Nice.

My Left view pc has just 1 4K display connected and the AutoFPS feature seems to work well. 

My Server pc had 2 4K displays connected and the AutoFPS feature seems unstable. The LOD value is continuesly adjusted bevause the target framerate gets adjusted continuously.

And FG is Enabled on both pc’s but the App seems not to see it. It says Off.

Here the LOD The continuesly LOD adjusting on the server ( 5 sec between these screenshots)

Also see the difference in FPM … The Left view client is doing the same as the server ..

To finish the rest of the flight I switched to Adaptive LOD. Also saying that FG is off …

 

 

 

Edited March 10, 20242 yr by GSalden

Finally on latest test version, I do tend to sleep a bit from time to time 😉 

Quote

New Test Version 10Mar240100Z:

• Enhanced auto target FPS functionality to allow auto target FPS to adjust if extremity conditions are such that the target FPS is no longer appropriate eg. if at TLOD Min, cloud recovery reduction on and still 20% lower FPS than target and vice versa at TLOD Max and still 20% higher. This works well if you depart from a non-complex area and arrive at a complex area, and vice versa, allowing the app to appropriately adapt to the significantly changed performance conditions without overreacting to otherwise medium to small performance changes.

So I guess the auto target FPS is a completely new feature. Since I only updated to 240100Z 30 min ago I need time to digest a bit. If any other early adopters are testing the latest test version, it'll be good to have a discussion about the benefits of the new auto target FPS feature. 

EDIT: Later I realised that @GSalden beat me to it - I was still not up to date on this thread when I wrote the above sentence 😉 

For me my immediate reaction is that it'll take some time to get used to not even having to set a target FPS value. 

AGL 20,374ft en route in the Fenix from KBOS to CYYZ (image looks a bit funky as I turned HDR off to be able to include AutoFPS in screenshot):

Edited March 10, 20242 yr by Cpt_Piett

Fellow simmers and AutoFPS enthusiasts: It'll be good if we could collaborate and gather some info while Reset is catching up on some (probably much-needed) sleep 🙂 Hopefully when the man wakes up in 7-8 hrs he'll be greeted with some activity in this thread 🙂

Update: I'm already 98nm from TOD, and I still haven't been able to fully absorb what the new auto-auto mode actually does. Need to get some coffee to wake up that brain!

Seems that Reset has introduced some new terminology: 

• auto target FPS
• TLOD Min Extra behaviour
• cloud recovery plus

Quote

Changed the GPU load to always show in status line

Not seeing this with GPU_Z open. EDIT: It did work a bit later 🙂

I'd prefer a higher TLOD up at FL370 (even though at the moment I can't see the ground due to heavy clouds). But I guess my settings are still too high.

Edited March 10, 20242 yr by Cpt_Piett

Descending, changed resolution from 5461x2880 to a more reasonable 3840x2160. Also I shut down FSLTL (AI traffic). I was previously FPS-locked at 80 using RTSS. I'm now unlocked (to be able to test new auto target FPS feature fully). Now FG-FPS is higher than my monitor max refresh rate at 120Hz. I'd still prefer a higher TLOD up at altitude and lower FPS. 

Quote

Added config file option to log sim values, as currently happens automatically in test versions. Apart from not wanting clutter up the expert settings UI area any further, this is not shown in the UI on the expectation that only the type of users who have the skill to find and edit config files will be able to interpret this extra logging information properly anyway.

Appreciate this as I tend to examine the log file for any inconsistencies. Usually too busy on departure and approach to have time to check the AutoFPS window. 

10 hours ago, pete_auau said:

your putting  updates  far too quickly  can you slow  it  down abit  so  we  can  catch up from the last update 🙂 

I have to agree with this. I haven't even had time to catch up on this thread as it takes some time to get the Fenix ready for departure 🙂 After testing latest test version I'll probably get some time to read Reset's mega-post 😉

11 hours ago, Reset XPDR said:

I've just drafted up the testers notes for AutoFPS version 0.4.2, with additional feature explanations that will end up in the readme instead.

Sorry for the post spam guys - guess I'm a bit energized after a good nights sleep 😉 Put aircraft in a hold on STAR into CYYZ to get some time to check out @GSalden's post above mine. 

Edited March 10, 20242 yr by Cpt_Piett

2 hours ago, Reset XPDR said:

In trying to finish it up as quickly as possible, I got a bit carried away with my test releases and may have alienated some of my most avid supporters, and to them I am truly sorry.

You can rest assured there won't be any alienation happening with yours truly, my friend 🙂 And can understand the publicity AutoFPS is getting can be a bit overwhelming. 

If you do as you've alluded to (retreat back into the obscurity from whence you came), I'll surely miss collaborating with you on your excellent app(s)!

2 hours ago, Reset XPDR said:

There is ongoing controversy between which way to go with OLOD as altitude increases. I am in the camp that the higher I get the less detail I can see in any object anyway, especially in VR as the graphics are not as defined as they are in 4K+ desktop, so I decrease as I go up. Others, like you swear they can see such detail in far off distances the higher they get, so increasing OLOD makes sense to them. There is no right or wrong way, just do what you feel works best for you.

Higher OLOD at lower altitudes makes sense to me. Just as lower TLOD at lower altitudes. Although if TLOD is too low on approach, we'll get too much of a "FS98-effect", especially in mountaineous (yeah I know I misspelled that word) regions. 

Hence if I interpret correctly what I've seen so far with auto target FPS, I might turn it off in the future and tweak my settings so that TLOD will be higher (rather than having ridiculously high FPS. 

Edited March 10, 20242 yr by Cpt_Piett

Arrived at a CYYZ gate and the approach was certainly... interesting. I'll probably infringe on the screenshot limit here, but as a picture is worth a thousand words...

Final approach (Fenix V2, FlyTampa's Toronto Pearson Intl, no AI traffic):

Here the TLOD is too low - notice how the RWY is blurry. 

Vacated the runway: 

FSLTL back on:

Edited March 10, 20242 yr by Cpt_Piett

I’d like to add my thanks to @Reset XPDRfor an outstanding little app, it’s removed the annoying stuttering I used to get moving camera views at heavy airports whilst bringing out amazing ground detail from high altitude which I didn’t have before. 

One question, is it possible to set a standard minimum TLOD on ground but allow it to go further down if necessary (my system maintains TLOD 100 and 60 FPS easily except EGLL/KLAX etc with AI traffic, so I’d like it to be 100 standard but reduce below 100 only when necessary, not every time). My understanding is that the minimum TLOD is mandated at all airports regardless of performance.

Maybe there’s something I’m not setting correctly?