Ok so I’m making a game in blender and when there are to many objects in the scene the framerate drops extremely rapidly. Now I’ve looked up threads on this before, but any info they have had is useless to me. My objects are all seperate enemies, as a result it’s not simply a matter of copying via alt+d. So I was wondering if there were some way I could improve preformance without lowering the number of objects.
In the BGE, ALT+D doesn’t have the performance improvement that Blender rendering does. Don’t use it for those reasons.
You need to give us performance reports (e.g a screenshot of the profiler; menu::game->show framerate and profile), otherwise it could be anything. Also, your computer graphics, ram and CPU specs.
It’s going to be an hour or two before I can get on my computer and take a screenshot, but I have an eightcore processor and an Nvidia gtx 960,I typically have no problem running most games, averaging 60-120.
It’s going to be an hour or two before I can get on my computer and take a screenshot, but I have an eightcore processor and an Nvidia gtx 960,I typically have no problem running most games, averaging 60-120.
Read the profile: physics are at 89%. This means 89% of processing power is being spent by physics. Try use collision bounds were possible and also try make AI dynamic or character, not rigid body. Also any objects that are not colliding change to no collision.
I know there are a lot of objects but I need every single one of them! Any other engine wouldn’t normally have a problem with this, so how do I keep my objects but maintain the framerate! Do I edit blenders code, is there something easier I can do? Just what do I do!?!?
You have the symptoms of a permanent collisions.
Unless you’re doing some sort of hard core physic simulation - like fluids - the time spent on physics should be negligible, always.
Even if you have lots of dynamic objects.
A permanent collision is when a dynamic object is forced (usually by a parent-child relationship) to intersect the boundaries of another static or dynamic object.
The physics engine tries to move it away, the engine puts it back where it started and the cpu wastes time.
It is not a bug, just something that you have to be careful to avoid when you design your models and you bind them together as parents to children.
Check your models to see if there is any static-dynamic or dynamic-dynamic intersection among objects that belong to the same scenegraph branch (for exmaple, A is a child of B, B is dynamic, A is static and in permanent collision with B: if so, make A non collidable).
