Over on github I have a sample Unity project that demonstrates both the non-type-safe and type-safe methods. In the above example we also keep track of the active explosions so we can return them to the pool when they are finished: The pool is empty, so we can't spawn any more at the moment. Public void SpawnExplosion(Vector3 position) Now to spawn an explosion, you can do this: The ObjectPool‘s m_prefab field will appear in the inspector, and it will only allow you to drop an Explosion component on it. To do this, we must define a new class which derives from ObjectPool with the Explosion as our type parameter:Īnd that’s it! You can now add ExplosionPool to a GameObject, and assign a prefab to it.
We want to create a pool of Explosion objects. We use the generic collections so we can give them our type T.
#BINARYFORMATTER IN UNITY FOR MAC FREE#
The list of free and used objects for tracking. The prefab must have a component of type T on it. Public class ObjectPool : MonoBehaviour where T : MonoBehaviour Now that we have the class defined like this, we can use the generic type placeholder T anywhere that we want to refer to the type that the pool was created with: In our case we want the constraint that says “the type MUST derive from MonoBehaviour”. There are several different types of constraints we can specify. The where keyword defines the constraint. We want to pool Unity components, so we’ll also add a constraint on the type which says that it must be a MonoBehaviour: public class ObjectPool : MonoBehaviour where T : MonoBehaviour First we need to define a generic version of the class that accepts a type name. Let’s implement our object pool class using generics. When you call the method and put your type in the angled brackets, you tell the compiler to automatically generate a version of GetComponent that knows specifically about your type.įor more detailed information about generics, check out this introduction from Microsoft. This syntax with the angled brackets indicates that the GetComponent method is a generic method which can work with any type (actually, specifically any MonoBehaviour type). How can this work? The Unity developers don’t know anything about your FooComponent. Gets the MonoBehaviour of type FooComponent which is on fooGameObject. Instantiate the pooled objects and disable them.įor (var i = 0 i () methods you, are already using them yourself. Public class BasicObjectPool : MonoBehaviour A First AttemptĪ first pass on a system like this might look as follows: This way you re-use firework effects instead of continually creating new objects and destroying them later.
Then when you need to spawn a new firework, go through the list, find one that isn’t enabled, enable it, configure its position, and play it. Instead of instantiating the prefab whenever you need it, you could pre-instantiate a list of them and disable them.
Let’s say you want to spawn a firework particle effect: One technique we can use to avoid these issues is called “object pooling”. Also in Unity the Instantiate function call can take quite a bit of CPU time. If you allocate objects regularly every frame that quickly become unused and unreferenced, you’ll probably cause regular hitches in your framerate. You don’t know when the garbage collector is going to clean up objects that are no longer referenced in order to reclaim unused memory. In a garbage collected, managed language like C# you still have to worry about this. Constructing objects can also be time consuming depending on the complexity of your classes.
It’s usually best to allocate what you need up-front at startup or on level load rather than mid-game during a frame, because the default memory allocators can be slow at finding free memory blocks. Managing memory usage can be crucial for decent performance in game development, especially on memory-constrained devices like mobile phones or consoles.
0 kommentar(er)
