- Home /
Low fps with many objects even when not looking at them
I have a 12k poly cube that I duplicated 50 times. Before I added them, I have 350 fps. Now I only have 40 fps when looking at them, but the problem is, when I look in the opposite direction and there is nothing in view, I still only have 80-90 fps. Why is this?
When I look away, the draw call number goes down to only 30. When I am looking at them thought its over a thousand. I'm designing for pc. Also, the cube does not seem to be batching, even though I have static batching turned on and they are all set to static and have 1 plain diffuse texture all of them are just duplicated with the same material.
I'm not sure if the draw calls are even effecting the fact that just having all these objects is making my fps low, I mean why am I dropping 200 fps if they are not even in view and the draw call goes down if they are not in view?
What is the problem? It's like just having all the objects in the scene is dropping the fps in game even if I'm far away not looking at them.
batching is applied only to meshes containing less than approx 900 vertex attributes in total. This includes everything (uv1 uv2).
What you've posted doesn't make sense, so I wonder if there are other things going on. You say that when you look at 50 cubes you have 1000+ draw calls - at most, you should have 50 additional draw calls. What else do you have in that scene? Can you try creating a blank scene with just the cubes and debugging that?