To edit the LOD distance, open the asset in the StaticMesh editor. Under the LOD Settings, disable AutoComputeLODDistance. You can then adjust the LOD ScreenSize to change the distance.
As for LOD’s and foliage, this is a known issue that our developers are currently looking into. It should however still work but at different distances than the StaticMesh version. Play around with the ScreenSize setting to see if you experience this the same way. As a workaround, you could create a copy of the StaticMesh asset with different setting to use for foliage.
I tested this and it seems to be working on my end. However my LODs may not be setup exactly the same. Would you be willing to post a small test project and repro steps?
you beat me to the post. I reimported the exports from speedtree and the LOD’s appear to be working properly again. I think I done goofed and didn’t have the asset files checked out in source control as the files were locked. Once i checked the files out and reimported the changes took and my LOD are properly working once again. Thanks for your help.
This isnt distance based. nor is it a practical solution for large amounts of assets. Think of the devs that have to spend huge amounts of time changing each assets lod settings to optimize them since LOD settings cant be copied between assets or defined fully in config StaticMeshLODSettings section.
Now its the end of 2023 with no real change to this process…
Think of actually learning the engine and using the proper presets for foliage/geometry etc. so you do not have to manipulate individual assets?
Though you are 100% correct in that distance has nothing to do with it.
Back in .18 they decided to ■■■■ the engine up and change everything from distances to screen size;
damaging performance for pretty-much everyone in the process.
Biggest issue there being landscapes got the change as well, and size on screen doesn’t work at all for them when components can easily change size based on the overall map size.
There where a distance setting would have retained a more or less similar LOD distribution across changes, you now have to waste your life fully benching performance out and tweaking the value to fractional numbers that make little to no sense / spark floating point precision issues as well.
Don’t worry though, no one at epic cares.
BTW, before someone bit ches.
OFC, the proper way to do LODs is Size on Screen - Distance wouldn’t account for scaling.
The problem is that SOME items should be allowed to be LODd based on Distance - or locked into a Distance Only mode instead. Like Landscape.