For performance reasons we want to be able to use LOD on .json models as some of these models can get very intense because of all the parts (model cubes) and amounts of said model.
(Example) A simple bushy leaf model can have up to 24 pollys or 4 parts (1 cube 6 faces (12 pollys) and 3 flat planes inside (4 pollys each because of the double sided rendering on the planes))
and now imagine a forest of at least a 1000 leaf models. that's around 24000 pollys. So having a way to disable some parts if the player gets far enough would help a lot. (That 24000 pollys can become 6000 (+ a little extra for the near non LOD models) if LOD can disable the plane parts in this case.)
Again this is just an example other models may not be used as much or may have more detail. So it depends on what we are talking about but it's good practice to add this feature for performance =D
MVP
[ ] being able to disable parts (elements) on models based on distance to decrease total polly count
tobyplowy
commented
4 years ago
Story
For performance reasons we want to be able to use LOD on .json models as some of these models can get very intense because of all the parts (model cubes) and amounts of said model.
(Example) A simple bushy leaf model can have up to 24 pollys or 4 parts (1 cube 6 faces (12 pollys) and 3 flat planes inside (4 pollys each because of the double sided rendering on the planes)) and now imagine a forest of at least a 1000 leaf models. that's around 24000 pollys. So having a way to disable some parts if the player gets far enough would help a lot. (That 24000 pollys can become 6000 (+ a little extra for the near non LOD models) if LOD can disable the plane parts in this case.) Again this is just an example other models may not be used as much or may have more detail. So it depends on what we are talking about but it's good practice to add this feature for performance =D
MVP
Stretch