First Instantiation of Particle System Lags

I posted in scripting, but no one currently has given an answer. I figured I would reach out to another relevant section of the forum and share my pain.

I have an extra simple Android app. The user taps the screen to destroy objects, and when an object is destroyed, it creates a particle system to give some feedback to the user that the object was destroyed (little tiny default particles). My problem is that when the first object is destroyed, and the first particle system is instantiated, there is a lag spike that locks up the game for about a 1/2 second. Every other destroyed object and instantiated particle system works smooth as silk.

So I tried to pre-instantiate the object, as soon as the first object is destroyed, it still lags.

I also tried to instantiate the object with the other game object that gets destroyed (they are both in their own parent object) and make the particle system not auto play. Sure enough, even if I did not play the particle system effect, it still freezes on that first object destruction.

If I remove the instantiation from the object destruction, no lag. It seems to be tied to instantiating the first destroyed object. Again, at the end it all works fine after the first destroy/instantiate.

I do not think an Object Pool is the answer here, only because pre-instantiating the object didn't help in two different scenarios.

Thanks in advance for any help that is offered!

 

Have you had any success? I am facing the same issue.

 

I would pull out the profiler and see exactly what's causing the slowdown.

 

You could try instantiating and fully running the particle system out of camera view when the scene first loads as a brute force approach.