i tried setting the lod terrain to 8.0 (800) and object to 6.0 (600)
and made the userconfig read only however this didint improve my visuals

Make sure the preset line is set to Custom, otherwise it won't work.

No need to make the file read only BTW.

}
{Graphics
    Version 1.1.0
    Preset Custom

6 hours ago, Epicmc said:

i tried setting the lod terrain to 8.0 (800) and object to 6.0 (600)
and made the userconfig read only however this didint improve my visuals

Not sure why anyone would want to do this? LOD 200 is fine and taxing enough even on the best of systems. 

21 minutes ago, Ianrivaldosmith said:

Not sure why anyone would want to do this? LOD 200 is fine and taxing enough even on the best of systems. 

Yes.  It doesn't improve things like the taxiway signs anyway - they still pop up far too close.

43 minutes ago, bobcat999 said:

Yes.  It doesn't improve things like the taxiway signs anyway - they still pop up far too close.

As you say, driving along the runway/taxiway, I see only the next two, sometimes three signs. Not sure since when this behavior came in. Very early this year, I could have T-LOD up 400-600 working effectively with no big penalties (with my machine). Meanwhile, as stated by others, even 200 is very heavy for every CPU. I'm trying to ignore these annoyances in favor to all the other eye-candy appearances of the sim, but cannot say that I always succeed.

Edited September 1, 20223 yr by Nemo

I've been testing with a TLOD of 600 recently. My system can handle it in remote areas, and the draw radius is larger, which is great at higher altitudes. 

2 hours ago, Ianrivaldosmith said:

Not sure why anyone would want to do this? LOD 200 is fine and taxing enough even on the best of systems. 

Just out of curiosity, did you set your Objects LOD to 200 as well?

A dynamic Lod system would be the best possible solution, we don't need a high Lod when we are on the ground at airports, that would solve most people's performance problems.

1 hour ago, Nemo said:

As you say, driving along the runway/taxiway, I see only the next two, sometimes three signs. Not sure since when this behavior came in. Very early this year, I could have T-LOD up 400-600 working effectively with no big penalties (with my machine). Meanwhile, as stated by others, even 200 is very heavy for every CPU. I'm trying to ignore these annoyances in favor to all the other eye-candy appearances of the sim, but cannot say that I always succeed.

Glad you called this out Harry.  I have this as well and similarly it was "introduced" but I don't remember when.  I see you have a 3090, I have a 3080 and thought it was GPU memory but if it's happening to you too that isn't the case.  The frustrating thing is it's happening in P3D too now...  I've got the taxiway signs "appearing" as I move and models that appear without texture then a second or two before textures paint...   

So on my end I chalked it up to system specific but it sounds like in MSFS at least others have the same issue.  Ironic we both have 3xxx series cards and 12k CPU's and have issues.  Also both running M.2 drives.  

8 hours ago, MrFuzzy said:

Make sure the preset line is set to Custom, otherwise it won't work.

No need to make the file read only BTW.

}
{Graphics
    Version 1.1.0
    Preset Custom

It is set to custom, and btw it somewhat does affect the far loading however doesn’t affect what’s close to me aka still buildings pop in 

5 hours ago, hvw said:

Just out of curiosity, did you set your Objects LOD to 200 as well?

Yes I went above 200 

7 hours ago, Ianrivaldosmith said:

Not sure why anyone would want to do this? LOD 200 is fine and taxing enough even on the best of systems. 

I did this in hopes that it may help with buildings fading in/ popping  in as I land or fix the stupid taxi signs that suddenly show up 

My little old i7 4790k CPU is crying in the corner......

Edited September 1, 20223 yr by sidfadc

I have read a few posts in the MSFS forum that suggest this is related to internet bandwidth.  Anecdotally, I am fortunate to have 1 gig internet.  I was always on WiFi and the draw distance looked rough at times especially with Photogrammetry.  Speedtest was fine showing 350 mbps which is expected on Wifi with my distance from the router, but the needle bounces around and it doesn't look perfectly smooth.  I swear MSFS terrain requests and unpacks hundreds of 2mb files.  Combine that with anyone else in the house using wifi and I think the terrain can't catch up and wifi sucks and the constant small requests.

I switched to hardwire and my Speedtest went to ridiculously rock solid 800 Mbps.  I flew a test flight and the photogrammetry looked much better in the distance.  It looked like TLOD of 200 should.  Things were much more consistent and distance was definitely greater than wifi.  I am sure there needs to be more conclusive tests but I think wifi is bad the small file requests.  Even if you have a 250 mbs connection, it might be okay for a 1 gig file where it can ramp up to a download of 21/mbps, but the relentless small file requests get hung up with a wifi connection.

10 hours ago, Cpt_Piett said:

I've been testing with a TLOD of 600 recently. My system can handle it in remote areas, and the draw radius is larger, which is great at higher altitudes. 

Our hardware is very close, do you have this pop-in taxi signs too? For me it seems that it is not related to any LOD settings.

Edited September 1, 20223 yr by Nemo