Awake() and Start()

I see that we can initialize Variable in Awake() or Start() and Awake() will be called before Start().

When should we initialize in Awake and Start to have the best performance?

Usually Awake() is used to initialize if certain values or script are dependent on each other and would cause errors if one of them is initialized too late (awake runs before the game starts). Awake is also called only once for every script instance.

Let me quote the Documentation:

> [...] Awake is called after all objects are initialized so you can safely speak to other objects or query them using eg. GameObject.FindWithTag. Each GameObject's Awake is called in a random order between objects. Because of this, you should use Awake to set up references between scripts, and use Start() to pass any information back and forth. Awake is always called before any Start functions. This allows you to order initialization of scripts. Awake can not act as a coroutine.

and about Start():

> Start is called on the frame when a script is enabled just before any > of the Update methods is called the first time. > > Like the Awake function, Start is called exactly once in the lifetime > of the script. However, Awake is called when the script object is > initialised, regardless of whether or not the script is enabled. Start > may not be called on the same frame as Awake if the script is not > enabled at initialisation time.

Where the last part makes one big difference

To get to your question:

If the script is NOT enabled at the beginning of your game, and you don't need the variables to be initialized, start would be saving performance as awake() would be called regardless...
every variable would be initialized at the very beginning. At least that's the logical assumption I make.

This topic is well described in the official docmentation ([Awake][1] and [Start][2]).

This section describes why you might need two functions:

> The Awake function is called on all objects in the scene before any > object's Start function is called. This fact is useful in cases where > object A's initialisation code needs to rely on object B's already > being initialised; B's initialisation should be done in Awake while > A's should be done in Start.

The difference between Awake and Start is that Start is called only when a script is enabled.

These two functions are called before the first Update method and there is no performance difference between them. I would say that Awake is used to initialize all objects (like a constructor), and Start is used to link the objects or do something before a game starts. [1]: http://docs.unity3d.com/ScriptReference/MonoBehaviour.Awake.html [2]: http://docs.unity3d.com/ScriptReference/MonoBehaviour.Start.html

Awake is the equivalent of the ctor. It is called when a MonoBehaviour is created, before any other method if the object is active.

Start is run the first time the MonoBehaviour is activated. This can be right after Awake or long after. This allows to perform actions that are related to the current state of the app or objects.

For instance, you create an enemy, in Awake, you place everything that is basic initialisation. Then, the enemy is deactivated at the end of Awake. Later on, the enemy is about to be activated but you want to make it red if player is having some specific weapon, then you do it in Start.

IMPORTANT: If a prefab is created and the game object is off by default in the prefab, the Awake is not called until set on. In the case of a pool creation where prefab may be off, the awake is happening first time the pooled object is activated.

OnEnable is similar to Start but happens on every SetActive(true) and on start if enabled. This can be a candidate for your enemy willing to change color over the level based on the player magna for instance.

There's not much difference in the performance. But I can tell you a difference between them.

Take a simple example. Say if you want to print "HELLO" in console even if you have not activated the script in inspector, using Awake() function, you can print it in the console. But if you had written the same thing in Start() function and the script wasn't activated, you don't get any output in the console. That's the difference.

Codes in Start() function get executed only if the script is activated while, codes in Awake() function get executed even if the script is not activated. Try it !

I'd claim there is no real performance difference at all.

What Minzkraut stated

> If the script is NOT enabled at the beginning of your game, and you don't need the variables to be initialized, start would be saving performance as awake() would be called regardless... every variable would be initialized at the very beginning. At least that's the logical assumption I make.

is only semi true. If you do everything only in Start the UX might be even worse since instead of one bigger lag when starting the app - which in my eyes is totally acceptable - it might lead to smaller but more lags during game play which I personally would avoid as much as possible.

---

In general it was already often explained in the other answers how and when Awake and Start are called and that basically it is "just" a timing difference.

For details refer to Execution Order of Events

---

Leaving disabled components and inactive GameObjects aside my personal thumb rule is

• Use Awake for everything where you don't rely on any other component and references.

  E.g. set default field values, populate things using GetComponent etc

• Use Start for everything where you do rely on other components such as accessing the results of GetComponent

  This way these other components supposedly did already receive their Awake call so they themselves are already linked up and ready to be used by others.

This solves timing and dependency issues in the most cases.

Where this is not enough you would start to tweak the Script execution order or use events.

---

And then there is another quite important difference in the use case of using Instantiate or AddComponent

• Awake (and OnEnable except using Instantiate and the component is disabled) will be called right away during the instantiation and any code line after Instantiate will be executed after it is finished.

• Start however will be delayed until the end of that frame (or until enabling if the component was disabled in Awake).

  This allows you to have enough time to use Instantiate and modify some field values before Start is called and can now base its behavior on the modified field values.

For example this

public class Example : MonoBehaviour
{
    private class X : MonoBehaviour
    {
        public int x = -1; 

        private void Awake()
        {
            Debug.Log($"Awake {x}");

            x = 12;
        }

        private void OnEnable()
        {
            Debug.Log($"OnEnable {x}");
        }

        private void Start()
        {
            Debug.Log($"Start {x}");
        }
    }
    
    private void Update()
    {
        if (Input.GetKeyDown(KeyCode.Space))
        {
            Debug.Log("Instantiate");
            var x = gameObject.AddComponent<X>();
            Debug.Log("After instantiate");
            x.x = 42;
        }
    }
}

will produce the output

Instantiate
Awake -1
OnEnable 12
After Instantiate
Start 42