Resolved Question About Object Pooling Components

I'm following this Brakeys tutorial on object pooling:

And here is what my method that initially instantiates the objects looks like:

Code (CSharp):

1. private void Start()
2.     {
3.         poolDictionary = new Dictionary<string, Queue<PooledUIObject>>();
4.  
5.         foreach (UIPool pool in pools)
6.         {
7.             Queue<PooledUIObject> objectPool = new Queue<PooledUIObject>();
8.  
9.             for (int i = 0; i < pool.size; i++)
10.             {
11.                 GameObject obj = Instantiate(pool.pooledObject.gameObject, this.transform);
12.  
13.                 PooledUIObject pooledObject = obj.GetComponent<PooledUIObject>();
14.  
15.                 pooledObject.gameObject.SetActive(false);
16.                 objectPool.Enqueue(pooledObject);
17.             }
18.  
19.             poolDictionary.Add(pool.tag, objectPool);
20.         }
21.     }

It's all working well, but I'm wondering, is there any way to avoid the

GetComponent

call when doing something like this?

I want the

PooledUIObject

component because that holds the text and image that I want to have access to but when I instantiate something it always just returns a

GameObject

, so is there any way, using this object pooling technique, to avoid the (potentially hundreds)

GetComponent

calls?

 

Instead of calling Instantiate like this:

Code (CSharp):

1. GameObject obj = Instantiate(pool.pooledObject.gameObject, this.transform);

Can you call it like this?

Code (CSharp):

1. PooledUIObject pooledObject = Instantiate(pool.pooledObject, this.transform);

 

Thanks perfect, thank you! For some reason I was under the impression that Instantiate always returned GameObjects. Thanks again!

 

Does this actually save the performance cost of GetComponent, or does it just call GetComponent under the hood?

 

Probably just calls it under the hood. But the performance cost of GetComponent is overblown anyway.