Search Issue Tracker
Not Reproducible
Not Reproducible in 6000.0.X
Votes
0
Found in
2021.3.42f1
2022.3.42f1
6000.0.15f1
Issue ID
UUM-78386
Regression
Yes
"Canvas (Environment)" GameObject is added as root to a Canvas Prefab when the Prefab is saved with "PrefabUtility.SaveAsPrefabAsset" in a Script
How to reproduce:
1. Open the “PrefabTest.zip“ project
2. Open the “SampleScene“
3. Open the “Assets/Canvas.prefab” Prefab in the Project tab
4. Observe the “Canvas“ GameObject in the Hierarchy
5. Exit the Prefab Edit Mode
6. Select the “EditorButton” GameObject in the Hierarchy
7. Click on the “Prefab Load/Save“ Button in the Inspector
8. Select and open the “Assets/Canvas.prefab” Prefab in the Project tab
9. Observe the Hierarchy
Expected result: The Canvas has not changed
Actual result: The Canvas has a grayed-out “Canvas (Environment)“ root GameObject
Reproducible in: 2021.3.42f1, 2022.3.30f1, 2022.3.42f1, 6000.0.15f1
Not reproducible in: 2022.3.29f1
Reproduced on: Windows 11 Pro (23H2), macOS 14.5 (by the reporter)
Not reproduced on: No other environment tested
Notes:
- Reproducible only with the Canvas GameObject
- The reporter states that this bug could be caused by the fix of this issue: https://issuetracker.unity3d.com/issues/the-prefab-scale-values-are-set-to-zero-when-the-prefab-with-a-nested-canvas-is-modified-through-a-script
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
This appears to already be fixed in 6.1. No further work required at this time.
Resolution Note (6000.0.X):
This appears to already be fixed in 6.1. No further work required at this time.