2D optimization help, im going crazy...

Hi Luniac,

I'd suggest three things:

1. If you haven't already been using it, the Object Pool (with setActive instead of Instantiate)

2. This article from Gamasutra

3. Data Locality (more efficient caching and linking between calls)

It certainly sounds as though what is causing it is tags, and high level to native calls and pointers. I'd recommend the 3rd article will probably be your answer with regards to asset arrays instead of pointer arrays. But the other two items will help too.

Good luck.

I ran into a similar problem in a mobile game stacking stones. each stone had a 2d polygon collider. once too many stones were stacked i lost frame rate immediately. My solution was to add a decay counter, once a stone was long enough on screen i changed it to isKinematic.

I don't understand your game mechanic enough but perhaps it will help.

good luck.

I also noticed setting multithreaded in the build options lowered fps by 5+

I'm gonna recode a part of my game so that the 3d collider is deactivated as soon as a particle interacts with it, this way there will way less active 3d colliders at any moment in the game, a lot less actually, so that should help. In fact i'm completely removing any interactivity between zombie 3d colliders, and will make it only particle to collider collisions. It'll make a little extra overhead because ill have more particle with collision enabled, but ill minimize it so that it's less than 100 totalor so collidable particles added.

The way i have it now is that a particle collides with a 3d collider, that collider becomes a trigger and zombie goes on fire, at which point another zombie 3d collider can collide with the trigger and also become a trigger and go on fire, and so on and so on. eventually when the fire disipates from any particular zombie, that 3d collider will deactivate so it cant set any other 3d colliders into a trigger and on fire. It was actually kind of elegant lol, i thought i was being proactive in utilizing one 3d collider for all that functionality by playing with the triggers.

But now the 3d colider can be deactivated the entire time the zombie is on fire instead of being a trigger, and ill just have the fire be a collidable particle like my flamethrower weapon actually. I was originally trying to lower my collidable particle count because i know its inefficient but i NEVER thought that it would turn out that the 3d colliders themselves were this inefficient, even as kinematic!

I'm still not sure how i'm gonna limit the 2d collisions between zombies, but technically speaking, since the turret won't be able to take too many hits, by the time enough zombies start colliding with each other, the turret will already be destroyed.

I'm really not sure any other way to not have the zombies not collide with each other, i definitely don't want them to overlap and ignore any collisions because that would just look silly.

I was thinking of implementing a non physics way of motion using transforms and pure scripting, but it just would just be over complicating things in my opinion at the moment.

I was thinking i'll just limit the amount of zombies on screen at any moment to maybe 50 or less, and if it's too easy i can make them faster.

I'm gonna play around a little more with the timestep after i'm done recoding the 3d collider part and see if maybe i missed a little fps boost somewhere.

Thanks for the help guys, ill definitely write back with my final solution and fps in case anyones interested.

Are you caching your transforms. If you are not it is doing the equivelent of gameObject.find every time you move a Zombie. Have a look at this, it certainly won't hurt your frame rate.

 private var tMy_Transform : Transform;
 
 function Start() {
 
     //Initialise vars.
     tMy_Transform = transform;
 }
 
 function Update() {
 
     //Whatever you want to do, just used this as an example.
     tMy_Transform.Rotate(Vector3.up * fRotation_Speed * Time.deltaTime);
 }