1 hour ago, Ixoye said:

Be sure you don't have it running when you start MSFS, just let it autostart, I have noted that it wont work if I had it running before I start MSFS.

That was it! I thought I'd exited, when in reality, it was still running in the background.

6 hours ago, abennett said:

It’s the middling altitudes when TLOD is obvious like 500ft to 8000ft you can clearly see the edge of the detailed terrain, trees etc, and beyond blur. At very low altitudes you can’t see that far to see the edge, and when high you can’t make out the detail anyway. But for example at 3000ft on approach, one can clearly see where the detail is loaded and where it isn’t.

Well I guess, like many things in the flight sim world, this seems to be an individual system thing because I see no edge to detailed terrain with low TLOD at "middling altitudes" and off course at airliner flight levels any detail is obscured by haze.

Bruce

Anyone had the issue where even though descending its says trend cruise and doesn't lower LODs?

 

Edited January 3, 20242 yr by abennett

1 hour ago, abennett said:

Anyone had the issue where even though descending its says trend cruise and doesn't lower LODs?

 

I've had it once that it was stuck on the 1500 AGL level although I was on cruise at 38000 feet. I suppose it was due to me using time compression or something. Anyway closing DynamicLOD and restarting it solved the problem.

2 minutes ago, Fiorentoni said:

Anyway closing DynamicLOD and restarting it solved the problem.

You're saying you can close it and restart and it works.  Can you edit pairs during flight and have the changes reflected do you know?

22 minutes ago, Noel said:

Can you edit pairs during flight and have the changes reflected do you know?

Yes that is possible.

8 hours ago, abennett said:

Anyone had the issue where even though descending its says trend cruise and doesn't lower LODs?

 

With these settings you get a lot of loading when climbing or unloading when descending.That might cause stutters.

The developers advice is to use just 3 levels. You can add 1-2 extra levels but keep then at least 2000 ft apart.

9 hours ago, Noel said:

You're saying you can close it and restart and it works.  Can you edit pairs during flight and have the changes reflected do you know?

Yes. Immediate effect.

4 hours ago, GSalden said:

With these settings you get a lot of loading when climbing or unloading when descending.That might cause stutters.

The developers advice is to use just 3 levels. You can add 1-2 extra levels but keep then at least 2000 ft apart.

The developer also recommends a reasonable step-size of 25-75. Which is a kind of a dilemma. The more steps you have the more chances for stutters you get. But the larger the step-size is the bigger the chance for a more noticeable stutter is as well. 

So I guess key is to not go to extremes like a step every few hundred feet or step-sizes of 100 or more.

I use these steps for Airliners:

tlodPairs0" value="0:80|500:100|1000:110|2000:120|3000:130|5000:140|8000:160|12000:180|16000:200|20000:250|24000:300

and these for GA::

tlodPairs1" value="0:100|300:120|600:140|1000:150|1500:160|2000:170|3000:180|4000:200|5000:250|6000:300|8000:350

 

These settings don't cause issues with stuttering for me. Of course you can always get a stutter when some demanding scenery is just at the edge of an LOD area, but that will happen without this tool as well.

 

8 hours ago, GSalden said:

With these settings you get a lot of loading when climbing or unloading when descending.That might cause stutters.

The developers advice is to use just 3 levels. You can add 1-2 extra levels but keep then at least 2000 ft apart.

I read that too but I'm not getting stutters with this configuration.  I'm setup close to my machine's capabilities for MSFS settings and I tried to get much more LOD at high elevations but it was much to much for my settings but this config is flawless:

@Noel

What is the reason that you lower your oLOD instead of increasing it ?

The moment you are flying higher you can see more in the distance….

 

14 minutes ago, GSalden said:

@Noel

What is the reason that you lower your oLOD instead of increasing it ?

The moment you are flying higher you can see more in the distance….

 

Last night is the first time I tried this after someone suggested it's a better way to set OLOD, but not sure if it's a good thing or not.  The reason being, presumably, the farther away you are the less detail matters.  Ever since I read your suggestion I've kept fixed OLOD at 100, so again not sure if this is the best the way I have it now or not.  I just know landings at arrival airports are good right now with this, and w/ the prior setting to set OLOD to go up during the climb.

I did notice the big stutters when I had TLOD set too high for my hardware.  I had set TLOD to 300 to 400 at high altitude but was way too much for my hardware.

21 minutes ago, Noel said:

Last night is the first time I tried this after someone suggested it's a better way to set OLOD, but not sure if it's a good thing or not.  The reason being, presumably, the farther away you are the less detail matters.  Ever since I read your suggestion I've kept fixed OLOD at 100, so again not sure if this is the best the way I have it now or not.  I just know landings at arrival airports are good right now with this, and w/ the prior setting to set OLOD to go up during the climb.

I did notice the big stutters when I had TLOD set too high for my hardware.  I had set TLOD to 300 to 400 at high altitude but was way too much for my hardware.

Noel, currently I use :

tLOD : 0-100 / 1500-150 / 5000-175 / 10000-200 / 15000-225 / 20000-250

oLOD : 0-100 / 2500-150 / 7500-175 / 12500-200

I am still testing. As I only use the VC without instruments and never Spotplane view perhaps a tLOD of 200 might be enough already and any higher will show nothing extra.

- - - 

Keep attention to first set a new tLOD and have the oLOD follow 1000-2500 ft later…..

In that way the pc first will load more terrain tiles around the plane and after that the objects follow. Not all together which wil tax your pc more at that moment.

 

I only think that higher OLOD values gives more detail on buildings at ground level, the higher up the less important it is, personally I have no performance loss having it at max settings all the time.

17 minutes ago, Ixoye said:

I only think that higher OLOD values gives more detail on buildings at ground level, the higher up the less important it is

Yes that is why I think it may make sense to have OLOD decrease as you climb, since it's less important as you ascend. OTOH, as Gerard mentioned a while back it's since we're after good performance on arrival having OLOD increase the closer you get to landing adds load.