Search Issue Tracker

Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.




Found in


Issue ID




Awake of NetworkBehaviour is not called at launch in standalone build, but is in the Editor



In Editor, Awake and Start functions are called as follows: Awake in Networked object, Awake in local object, Start in local object, Start in Networked object
In Player, Awake and Start functions are called as follows: Awake in local object, Start in local object, Awake in networked object, start in Networked object

To reproduce:

1. Open the project, attached by tester
2. Open "test" scene if not open
3. Press Play
4. Create Host
4. Observe the console
5. Stop the game
6. Build and run a standalone
8. After it has launched, create Host and close the game
9. Go to {standaloneName}_Data folder and open output_log.txt file
10. Observe the order of outputs from Awake and Start methods

Expected: Awake and Start methods are called in the same order on MonoBehaviour and NetworkBehaviour objects no matter if it is in Editor or in standalone build
Actual: the execution order of Awake and Start methods in Editor are diferrent than in standalone build when using NetworkBehaviour

Reproduced on 5.4.5p1, 5.5.3p1, 5.6.0p2, 2017.1.0b1

Comments (11)

  1. zdo

    May 07, 2017 21:47

    Very annoying bug. Having completely working project in editor doesn't mean having working project in standalone build.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.