Research: LODs
-
So, I was thinking about how important LODs are for asteroid fields and how awesome it would be to have them for asteroids.
Now the question: Has anybody figured out how to do LODs for .3db files?
How do LODs work anyways for .cmp files?I know it should be possible, since tradelanes have their very own lod, that is actually exclusively controlled by the .3db file (overriding any .ini change).
So yeah, any experts?
-
I’ll ask the dumber question: can we use CMPs for asteroids? Because then we could just put LODs and try seeing if the LODranges parameter can be used.
-
Cant see why we cant…
As long as the codes all sorted u could use Osiris’s for asteroids… lol not that i’d
recommend it… hehe…I came to this conclusion after making an asteroid torpedo launcher for my brother… If it goes
one way… (using asteroids for torpedos…) i dare say it will go the other as well
-
Should be as easy as adding a MultiLevel node under the . Add the Level0, Level1, etc nodes under the new MultiLevel. Move your initial VmeshPart under which ever LOD it’s meant to be. Then as you construct your LOD’s in Milkshape (changing the mesh names to reflect the LOD level), choose update 3db. Repeat the VMeshPart move for each LOD.
You could probably make it a bit more standardized by changing the VMeshLibrary node names to be like vanilla, but then you’d also have to hex edit the VMeshLibID section within its VMeshRef to match.
O yea, dun fergit ta add in a Switch2 leaf at theee end of yer MultiLevel section, editing its data as a float array and pasting in:
0.000000
100.000000
1000.000000
1000000.000000I think I had this working at one time, but you know… I’m senile I guess, or high school caught up with me.
Sidenote, yeah using a CMP might be much easier lol, 'specially with the LOD selection right there at export.
Ah just looked at the TLR model, yeah this should work just fine going by that. The Lod VMeshRefs just have to know where to look for their data, the actual name just has to match the hash already in it (or hex edit that to match the VMeshData name).
By the way, you should still need to add LOD entries in the INI too, the Switch2 values doesn’t seem to actually do jack by itself.
