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.
Postponed
Votes
2
Found in
5.3.5f1
Issue ID
805873
Regression
No
[UNET][Standalone] Inconsistent load order of networked objects in Editor and Build
Steps to reproduce:
1. open attached project '805873_54.zip'
2. build and play
3. host and join local host (using editor and standalone, order doesn't matter)
4. select join on both
5. check console and built game output_log
Expected: Awake should be run in the same order on both, editor and standalone
Actual: Editor: Scene > player > player || Standalone: player > player > scene
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Overlay Image gets darker on each Camera when multiple Cameras are used
- Assertion failed on expression: 'scriptedImporterClass == SCRIPTING_NULL error when opening the standalone profiler window
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
moco2k
Nov 18, 2016 15:13
I can confirm this issue. For example, I encounter the problem that networked callbacks like OnStartServer and OnStartLocalPlayer on player objects are called before Awake functions of networked objects which are pre-placed in the scene. However, this is only the case in standalone builds but not in the editor.
Erik-Sombroek
Jul 13, 2016 09:36
This error started to appear for me when i switched from non developer build to developer build, after that that even switching back to a non developer build made this error appear.
Very strange.