Unna Oertdottir on 20/7/2017 at 14:11
Post an object's LOD that doesn't work for you. I can tell you why.
Cardia on 20/7/2017 at 14:21
you mean you want a screenshot of the model?
Unna Oertdottir on 20/7/2017 at 14:28
Post the settings of the LOD. It's not that hard :bored:
Unna Oertdottir on 20/7/2017 at 14:42
:laff:
These settings doesn't make any sense
Try this
LOD 0 Model: adoor1
LOD 1 Model:
LOD 2 Model:
LOD 0-1dist: 300.00
LOD 1-2dist: 500.00
Cardia on 20/7/2017 at 14:46
Ok thanks Unna, damn you´re just here about two years and you know much more about Dromed than most of us. Nice!
Cardia on 20/7/2017 at 14:51
Nope, doesn't work, the object still disappears. I think i´ll have to block the access to this roof.
ZylonBane on 20/7/2017 at 15:10
Uh, guys, the Model LOD property is not a tool for reducing the number of models in a scene. If you don't provided a LOD1 or LOD2 model, Dark ignores it.
Unna Oertdottir on 20/7/2017 at 15:18
That's what LODs are made for: a detailed object disappears, another object appears within a certain distance. That depends on the settings. DromEd can't handle 3000 objects in sight within 1500 DU. Give it up.
ZylonBane on 20/7/2017 at 15:37
Yes Unna, we all get that. What I'm pointing out is the fact that the Model LOD property doesn't do anything unless you provide it with alternate model names.
Model LOD is intended to improve frame rates by swapping in lower-detail models for distant objects. That is not the problem Cardia is having. He's hitting a hard limit on total onscreen objects. That has nothing to do with model complexity.
