Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.2.5f1
Issue ID
1082634
Regression
No
New GameObject is not created in the active scene in builds
To reproduce:
1. Open the attached project (SceneTestProject.zip)
2. Open the TestSceneA
3. Enter Play mode and observe the output in the console
4. Build and Run the project for PC Standalone
5. Observe the output in the output.log file
Expected: the new game object is created in the active scene
Actual: the new game object is created in a currently loaded, but not active scene
Reproduced in 2017.4.11f1, 2018.1.9f2, 2018.2.5f1, 2018.2.9f1, 2018.3.0b2, 2019.1.0a1
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2018.3.X):
I would actually expect this to be the case during Awake during load, because of the way scene loading is implemented.
Changing this would break existing projects.
A work around would be to delay creating other object until Start or manually move new objects to the right scene.