Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
0
Found in
6000.0.73f1
6000.3.13f1
6000.4.2f1
6000.5.0b3
6000.6.0a4
Issue ID
UUM-139779
Regression
No
SubScene can be assigned recursively
Steps to reproduce:
- Create a new project
- Install the Entities package
- Create and add a SubScene to an Empty GameObject
- Attach the "SampleScene" to the "Scene Asset" property of the SubScene Component
- Press "Convert"
- Observe the Editor
Actual results: Multiple errors are thrown, and the Hierarchy is corrupted
Expected results: The action is prevented with an error "Circular reference detected: Attempted to convert Scene into a Sub Scene. A scene cannot reference itself as a SubScene." (as it is in fixed in versions)
Reproducible with versions: 1.2.4 (6000.0.0f1), 1.4.5 (6000.0.73f1, 6000.3.13f1)
Not reproducible with versions: 6.5.0 (6000.5.0b4, 6000.6.0a3)
Fixed in: 6.4.0 (6000.4.3f1)
Tested on (OS): Windows 11 Pro (25H2)
Notes:
- Thrown errors are 2 or 3 versions of:
"Recursive SubScene setup detected. Report a bug.
UnityEngine.Debug:LogError (object)"
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
- AI Assistant upgrade banner's `Open package Manager` link doesn't work
- Sub-asset UI does not refresh when undoing Renderer Feature add or remove actions in a URP Renderer asset
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Color Curve Key values remain visible after changing Curve type
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.
Resolution Note (6000.6.X):
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.