Search Issue Tracker
Won't Fix
Votes
0
Found in
2021.3.47f1
2022.3.54f1
6000.0.31f1
6000.1.0a8
Issue ID
UUM-90572
Regression
No
GameObjects are re-enabled when they are transferred to a Scene created with the CreateSceneParameters set
How to reproduce:
1. Open the “IN-90418-AudioSceneBug.zip“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Select the “Manager“ GameObject in the Hierarchy
5. Click the “Instantiate“ checkbox in the Inspector
6. Click the “Move to Physics Scene“ checkbox in the Inspector
7. Listen
Expected result: No sound is produced
Actual result: A sound is produced
Reproducible in: 2021.3.47f1, 2022.3.54f1, 6000.0.31f1, 6000.1.0a8
Reproduced on: Windows 11 Pro (23H2), Windows 10 (by the reporter)
Not reproduced on: No other environment tested
Notes:
- The issue occurs only in Scenes where localPhysicsMode is set to either Physics2D or Physics3D and not when it is set to None
- If CreateSceneParameters does not define the localPhysicsMode, the issue will not reproduce
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
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.