Search Issue Tracker
Fixed in 2018.3.X
Votes
1
Found in
2018.2.1f1
2018.3.0a6
Issue ID
1066277
Regression
Yes
Child Canvas Prefabs get correct 1,1,1 scale on disk but incorrect 0,0,0 scale in library
The bug can be reproduced without old projects at all. In any project in 2018.3:
1. Create a new Canvas
2. Create a new Canvas as a child of the previous Canvas
3. Notice the child Canvas scale is 1,1,1
4. Drag the child Canvas to the Project Browser to make it a Prefab
5. Notice the child Canvas Prefab instance scale is now 0,0,0
6. Open the child Canvas Prefab Asset in a text editor
7. Notice the localScale of the RectTransform is 1,1,1
See comment in case for how to check that the library representation scale is 0,0,0 even though it's is 1,1,1 on disk.
Original repro steps:
When upgrading a project from Unity 2018.2 to 2018.3, some of the UI prefab scale was changed to 0.
1. Download attached project
2. open it with Unity 2018.2.0f2
3. Open the MainMenu scene from SceneAssets/Scenes
4. Notice the Canvas Hierarchy -> Main Menu panel scale is 1 and UI is visible
5. Open it with Unity 2018.3.0a6 or a7
6. Open the MainMenu scene from SceneAssets/Scenes
7. Notice the Canvas Hierarchy -> Main Menu panel scale is 0 and all UI is invisible
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
Add comment