- Home /
Mass Placed tree Collision
In my scene when I mass place trees (Without Colliders) The game runs fine at 100 FPS. However when I add Colliders to the trees my FPS drops to about 25 FPS. Is there anyway solution to this? or is this just how it is? My computer can run high end games just fine (crisis 3 on high settings) oh, and i'm placing around 8000 trees since it is a forest level.
Thanks in advance
Answer by Entairex1 · Sep 28, 2013 at 10:07 PM
It depends on what kind of collider you're using. If you're using a mesh collider, then that means it has to calculate a very precise collider that covers every branch and bump of the trees (probably eats memory).
An idea would be to use a box collider instead. Try creating one and tweaking it to only cover the stem of the tree, this should lower the requirements a lot.
If you're placing that many trees, it's important to keep it optimized, and depending on how thick the forest is, you wouldn't necessarily need a very high mesh render distance. Maybe increase the fog thickness to make the transitions less noticeable.
I currently am using a "Capsule Collider". I have tried using a box collider, but that does not work when you "mass place trees". I mean it works when I manually place the tree prefab down. When I "$$anonymous$$ass place trees" The box collider does not work anymore =s. $$anonymous$$aybe I should just use less trees maybe?
hmm you could try and lower the density of trees at different areas, also did you try changing the render distance for trees?
By the way, how many polygons is 1 tree?
Each tree has about 2500 polygons. I know this isn't the problem though because I get around 80 FPS when the colliders are off. but still drops to about 20 - 25 FPS when I turn them on
Your answer
Follow this Question
Related Questions
"Mass place trees" vs -place trees with brush- vs -my own script- 0 Answers
Lag with trees that use colliders? 0 Answers
Mass Placed Tree Collider 2 Answers
Null reference that isn't null 2 Answers