I understand the general concepts of TLOD and OLOD, but  am curious if there are distance units associated (or implied) with a particular TLOD or OLOD value? 
For example, if TLOD = 100, does that mean the terrain will be clear and detailed for approximately 100 ft, or 100 meters, or 100NMs ( it would be nice! 😉) in front of the aircraft?

Same kind of question for OLOD = 100.  What if anything does the 100 mean?

Thanks,
Al

Decided to ask my TLOD and OLOD questions above to AI. FWIW below is the response.

TLOD (Terrain LOD)

• Governs terrain mesh resolution (DEM detail, ground textures, and vector data).
• A value of 100 means “baseline,” i.e. the distance/quality Asobo chose as default for performance vs. visuals.
• Increasing TLOD to 200 doubles the draw radius (terrain remains detailed further out), while 50 halves it.
• The actual distance in meters/NM is not published, but community tests show something like:
  • TLOD 100 = ~9–10 NM radius of full-resolution terrain around you
  • TLOD 200 = ~18–20 NM
  • TLOD 400 (very heavy) = ~35–40 NM
• Beyond that radius, the sim progressively lowers terrain detail and swaps to lower-res textures/mesh.

---

OLOD (Objects LOD)

• Controls 3D objects (autogen buildings, vegetation, airport objects).
• Same principle: 100 = baseline. Higher values extend the distance at which full-detail objects are drawn.
• At OLOD 100, autogen buildings/trees are full detail roughly out to ~6–8 NM. Beyond that, they thin out or switch to lower complexity models.
• At OLOD 200, that radius nearly doubles.
• So again, the number is a multiplier for the engine’s internal distance thresholds.

Edited September 12, 2025Sep 12 by ark

FYI, I found a bug with the new hybrid dynamic setting feature where settings reduction recovery does not occur at night, so I am working on a fix now.

2 hours ago, ark said:

Decided to ask my TLOD and OLOD questions above to AI. FWIW below is the response.

TLOD (Terrain LOD)

• Governs terrain mesh resolution (DEM detail, ground textures, and vector data).
• A value of 100 means “baseline,” i.e. the distance/quality Asobo chose as default for performance vs. visuals.
• Increasing TLOD to 200 doubles the draw radius (terrain remains detailed further out), while 50 halves it.
• The actual distance in meters/NM is not published, but community tests show something like:
  • TLOD 100 = ~9–10 NM radius of full-resolution terrain around you
  • TLOD 200 = ~18–20 NM
  • TLOD 400 (very heavy) = ~35–40 NM
• Beyond that radius, the sim progressively lowers terrain detail and swaps to lower-res textures/mesh.

---

OLOD (Objects LOD)

• Controls 3D objects (autogen buildings, vegetation, airport objects).
• Same principle: 100 = baseline. Higher values extend the distance at which full-detail objects are drawn.
• At OLOD 100, autogen buildings/trees are full detail roughly out to ~6–8 NM. Beyond that, they thin out or switch to lower complexity models.
• At OLOD 200, that radius nearly doubles.
• So again, the number is a multiplier for the engine’s internal distance thresholds.

Doesn’t TLOD in 2024 also impact the resolution of the mesh? I’ve noticed on the ground that going from 200 to 400 makes the runway textures look sharper.

Had a go with Test18 last night and the results were pretty good, getting good FPS in areas where normally it would tank (NYC, over PG areas for example), but I was noticing the ground textures were incredibly pixelated/low Res which I think maybe the in game dynamic settings as I've never seen them that bad before. Using non-expert, will give the latest update a go tonight hopefully but my idea is to wait until it's a full release of your app then tweak as this beta is already showing signs of differing performance with the two updates of that so far.

Edited September 12, 2025Sep 12 by MarcG

20 minutes ago, MarcG said:

Had a go with Test18 last night and the results were pretty good, getting good FPS in areas where normally it would tank (NYC, over PG areas for example), but I was noticing the ground textures were incredibly pixelated/low Res which I think maybe the in game dynamic settings as I've never seen them that bad before. Using non-expert, will give the latest update a go tonight hopefully but my idea is to wait until it's a full release of your app then tweak as this beta is already showing signs of differing performance with the two updates of that so far.

Test18 set the dynamic settings target frame rate to your frame gen target FPS but I have since learned that it should be set to native FPS, so it has been updated in Test19 and Test20 to rectify, so should be better now.

Yes, you could wait until the full release, but if I didn't notice the FPS issue myself and no one else told me, like you did, it could have been formally released that way. One of the reasons I silently enabled auto-enable of dynamic settings is to flush out feedback like this that would otherwise have been latent in the release version.  I need this kind of feedback to get it to release condition and if no one provides feedback I will assume it is acceptable and that's what you'll get, so please keep using the test version and tell me what you think. 

BTW, to anyone else testing this, I found that you can enable developer mode and show the FPS view then close developer mode before a flight session and you will get the FPS view in your flight session and your log book still gets updated with the flight details.

Also, and of particular note to @Rob G, I noticed a strange thing when I was testing VR in non-expert mode in that the FPS view showed TLOD was reducing to 0.5 (ie. 50%) even though I was achieving my target FPS of 40, which matches the 40 FPS I have set for motion reprojection for my Quest 3 and 40 FPS for dynamic settings, when it should have been showing 1.0. Further investigation revealed that my FPS was rapidly changing between main thread and GPU thread limited and when I turned on the frame rate limiter in MSFS settings and set it to 40, everything turned green and TLOD went back up to 100% as it should. ie. @Rob G, contrary to my advice the other day, yes do enable the frame rate limiter in MSFS and set it to 40. The motion reprojection is a lot smoother too!

 

Edited September 12, 2025Sep 12 by Reset XPDR

Ok mate it's more time to actually test stuff but I'll see what I can do 🙂

5 hours ago, MarcG said:

Ok mate it's more time to actually test stuff but I'll see what I can do 🙂

Just fly as you normally do and advise me of any notable observations, like you did earlier, which shouldn't be too much extra effort.  It really helps me shape the final product.

On 9/10/2025 at 10:22 AM, ark said:

Thanks for the suggestion. I gave it [AutoFPS with the new hybrid dynamic settings mod] a try, but unfortunately I did not see any real difference. I'm still getting the small stutters on takeoff. Since using FSR 3 FG in the FS2024 settings disables V-Sync, then I assume V-Sync should also be set to Off in Nvidia control panel, or at least set to Use the 3D application setting. 
Thanks for your tireless work on Auto FPS!
Al

Just to close this issue, I tried an 'old' Nvidia GPU driver (522.22) which was released well over a year ago, and that seems to have solved my stutters problem (still using AutoFPS, of course). I have a 4070Ti Super GPU card and wonder if some of the older GPU drivers might work better with an older 40XX card then the new GPU drivers which I assume are focused on optimizing the performance of the newer 50XX series cards. Hard to know I guess, but I'm happy with how my system is now working.

Al 

Edited September 12, 2025Sep 12 by ark

So just to confirm, if my dynamic settings target is 20 fps, I should set autofps to 20, not 40 now, correct?

Edited September 12, 2025Sep 12 by agent00729

3 hours ago, ark said:

Just to close this issue, I tried an 'old' Nvidia GPU driver (522.22) which was released well over a year ago, and that seems to have solved my stutters problem (still using AutoFPS, of course). I have a 4070Ti Super GPU card and wonder if some of the older GPU drivers might work better with an older 40XX card then the new GPU drivers which I assume are focused on optimizing the performance of the newer 50XX series cards. Hard to know I guess, but I'm happy with how my system is now working.

Al 

Sorry, I must have missed your original message in all the mayhem trying to get the new SU4 beta working with the app. I still use the last known good driver for the 4000 series that came out just before the 5000 series did, namely 566.36, with great success. If you've found something that works well, stick with it!

2 hours ago, agent00729 said:

So just to confirm, if my dynamic settings target is 20 fps, I should set autofps to 20, not 40 now, correct?

Dynamic settings target is native and AutoFPS is frame generated, so 20 for the former (if that's what your native FPS is) and 40 in AutoFPS for FSR3. Note that 20 FPS is the bare minimum you can set for dynamic settings, so it may not work very well. Let me know how it goes. 

Ok great! I’ve actually been doing that, and everything works so far. I can’t explain it but even when I get down to 30fps, it doesn’t even feel like it. Idk if it’s something with frame gen or what where it even smooths out lower fps scenarios. But 30 feels barely different than 40 on my system 

Edited September 12, 2025Sep 12 by agent00729

15 hours ago, Reset XPDR said:

Test18 set the dynamic settings target frame rate to your frame gen target FPS but I have since learned that it should be set to native FPS, so it has been updated in Test19 and Test20 to rectify, so should be better now.

Yes, you could wait until the full release, but if I didn't notice the FPS issue myself and no one else told me, like you did, it could have been formally released that way. One of the reasons I silently enabled auto-enable of dynamic settings is to flush out feedback like this that would otherwise have been latent in the release version.  I need this kind of feedback to get it to release condition and if no one provides feedback I will assume it is acceptable and that's what you'll get, so please keep using the test version and tell me what you think. 

BTW, to anyone else testing this, I found that you can enable developer mode and show the FPS view then close developer mode before a flight session and you will get the FPS view in your flight session and your log book still gets updated with the flight details.

Also, and of particular note to @Rob G, I noticed a strange thing when I was testing VR in non-expert mode in that the FPS view showed TLOD was reducing to 0.5 (ie. 50%) even though I was achieving my target FPS of 40, which matches the 40 FPS I have set for motion reprojection for my Quest 3 and 40 FPS for dynamic settings, when it should have been showing 1.0. Further investigation revealed that my FPS was rapidly changing between main thread and GPU thread limited and when I turned on the frame rate limiter in MSFS settings and set it to 40, everything turned green and TLOD went back up to 100% as it should. ie. @Rob G, contrary to my advice the other day, yes do enable the frame rate limiter in MSFS and set it to 40. The motion reprojection is a lot smoother too!

 

Thank you for the update!

Don’t know if this has been discussed before, but I have an issue with cockpit shadows / occlusion (frankly, I’m not sure what but the cockpit shadows / lighting lose their depth) switching off and on near or on the ground. Am I the only one seeing this?