🐛 Fixed LODs not being loaded

[AnotherFoxGuy]

The code for loading LODs got removed at some point

[ohlidalp]

I vividly recall measuring performance of actor spawning: The worst thing was flexbody generation as I expected, but the second worst thing shocked me: the LOD lookups. Also by large margin our FPS bottleneck is batch count, not triangle count, so even if we got LODs right, it won't make signifficant difference. I'd rather remove that code entirely and let testers try finding actual difference, or at least add cvars to disable the 'classic lod' and 'custom lod'. At the very least wait until OGRE14 upgrade, after which I plan to implement resource loading on background.

I can't find this info in docs: Can OGRE mesh file format have embedded LODs? It would make sense. The MeshLodUsage object suggests that the primary way of doing LOD is having alternate edge lists for the same vertex buffer, and having a whole alternate mesh is something of an emergency solution. I don't know much about LOD in general but the manual suggests there's more than one way to determine LOD levels and some make more sense than plain distance.

[CuriousMike56]

The code was removed sometime after 0.4.7.0. Was meaning to create an issue ticket on this, glad to see it restored 👍

I'm only noticing a difference in spawn time of ~1.2s when loading actor-heavy maps like Train Valley, negligible difference really.

I'd rather have wonky LODs than none at all ,especially as they're used in some maps (NeoQ, Community Map etc).

[Zentro]

Do we need to refer to it as "OGRE's automatic mesh LOD generator"? Could it just be "Enable automatic mesh LOD generator"?

[ohlidalp]

^

[ohlidalp]

Right, I probably measured before resource groups were fixed, so the lookup had to go over all meshes in modcache instead of just over meshes in that ZIP. Thanks for checking.

[ohlidalp]

Seems to work fine.