Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2021.2
2021.2.7f1
2022.1
2022.2
Issue ID
1395158
Regression
No
GameObject active state is changed when it is moved between Scenes created with LocalPhysicsMode
How to reproduce:
1. Open the user's attached project
2. Open scene Scenes/SampleScene
3. In the Hierarchy window, select the GameObject "LoadSceneManager"
4. In the Inspector window, under the "Load Scene Manager (Script)" component, set Scene Physics Mode to Physics 3D
5. Press the Play button and go to the Game view
6. Press the spacebar
7. Observe the Console
Expected result: Console messages show that the GameObject is disabled and re-enabled after moving between Scenes
Actual result: Console messages don't show changes in the active state of the GameObject
Reproducible with: 2019.4.34f1, 2020.3.26f1, 2021.2.8f1, 2022.1.0b4,
Not reproducible with:
Could not test with:
Notes:
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note:
GameObject deactivation is an integral part of the inner workings of moving objects between physics scenes. It's a costly operation, so it's advisable to minimise the amount of objects being moved.