Search Issue Tracker
Fixed in 2021.3.26f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.2.X, 2023.2.0a15
Votes
0
Found in
2020.3.47f1
2021.3.24f1
2022.2.18f1
2023.1.0b15
2023.2.0a13
Issue ID
UUM-34557
Regression
Yes
The GameObject is not added to the active Scene when adding it from other Scene
Reproduction steps:
1. Open the attached project “InstantiatingBug“
2. Open the Test Runner (Window>General>Test Runner)
3. Press the button “Play Mode”
4. Press the button “Run All”
Expected result: All tests pass
Actual result: GameObject is not instantiated to the active Scene
Reproducible with: 2020.3.27f1, 2020.3.47f1, 2021.3.24f1, 2022.2.18f1, 2023.1.0b15, 2023.2.0a13
Not reproducible with: 2020.3.26f1
Reproducible on: Windows 11
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 (fix version 2023.2):
Hi, the behavior you report is currently the correct behavior. We have updated the documentation of GetActiveScene() to match the behavior. I will suggest to manually call SceneManager.MoveGameObjectToScene() to move the created GameObjects to the desired scene.
Resolution Note (fix version 2022.2):
Updated documentation to match behavior.