Execution order of Awake, Start AND custom init functions

So I understand that all Awake functions are called before Start functions, but what about custom init functions?

Here is my scenario:

- I Instantiate a gameobject that have two component scripts. Lets just call them Script1 Script2. Script1 has my init function which I'll just call InitFunc.

- Since one cannot pass variables through a constructor, I call InitFunc immediately after Instantiation.

- Then I notice that things done in InitFunc will not be picked up in the Awake function of Script2, but it will be picked up by the Start function of Script2.

So, since I couldn't find anything about this in the docs, I have to ask: Can I be sure of this? ..or was I just lucky that the init function of Script1 was executed before the Start function of Script2?

 

Try these links:

http://www.unifycommunity.com/wiki/index.php?title=Event_Execution_Order

http://unity3d.com/support/documentation/Manual/Execution Order.html

 

Thanks, but I'm not that much wiser. I couldn't find my scenario into any of these docs.

Code (csharp):

1.  
2. GameObject tmp = Instantiate(obj, pos, rot);
3. tmp.GetComponent<Script1>().InitFunc();
4.  

When exactly is InitFunc called compared to any Awake Start functions of tmp's component scripts?

 

add debug log at the start of each and test it.

I'm pretty sure awake is the first, but as start happens a frame later, initfunc should be 2nd, with start 3rd

 

Awake is called during the instantiate, so there is no way for you to pass it any data. Start is called just before a script's first Update, which certainly won't happen between those two lines of code, so it is guaranteed to happen after your init function.

 

Thanks tomvds, that's what I wanted to know. May I ask how you can say this with guarantee? I mean, could I have found this in the docs somewhere, or do you need 5 years of unity experience to know this?

 

This information is actually documented on this manual page.

 

Thanks andeeee, I read that page already as it was suggested in the first reply, but I will argue that it's far from clear where my InitFunc fits into this documentation. It's logical what tomvds says, that calling InitFunc right after the Instantiate should maybe happen before Start, but that situation is not handled in the document above, at least I can't seem to see it. So, I will take his word for it, but it would be reassuring to see it on some documented page. If you see something that I don't, please specify

 

The reference page for Start mentions that it is called right before the first update.

 

Yes I know, in my case however I'm calling a custom function (InitFunc) just after an instantiation. This function call is the one I can't seem to fit into this documentation.

 

As Instantiate and the first update never happen in the same frame, you actually can.

Frame 0: Instantiate
-> Awake
-> Whatever you call on it

Frame 1: Update
-> Start -> Update

 

Order of execution:
Awake
OnEnable
InitFunc
Start
Update

 

In case someone comes to the thread and needs an answer, like me, it's fine. The link you provided doesn't say when custom Init() functions are called, and that's exactly what the question was about.

 

Question:
"So I understand that all Awake functions are called before Start functions, but what about custom init functions?"
Context:
"I Instantiate a gameobject"
"Since one cannot pass variables through a constructor, I call InitFunc immediately after Instantiation"

My answer:
Custom init function called after Instantiatiate() is called after Awake() and OnEnable() but before Start() and Update()

Order of execution:
Awake
OnEnable
InitFunc
Start
Update

 

Context of question:

Code (CSharp):

1. GameObject tmp = Instantiate(obj, pos, rot);
2. tmp.GetComponent<Script1>().InitFunc();

Custom function called just after Instantiate().
Custom function called not in Awake, Start, Update, Reset, OnValidate, not in coroutine and so on.

Post is necro but my answer may be helpfull now.
My answer is more specific and clear than what has been left before.