Search Issue Tracker
Duplicate
Votes
0
Found in
2018.3.0a5
2018.3.2f1
Issue ID
1120090
Regression
Yes
[UI] Child of Canvas is corrupted when Main Camera size is set to 0 in the editor
To reproduce:
1. Create a new project
2. Create Canvas and add a cube to it
3. Set "Render Mode" in Canvas to "Screen Space - Camera"
4. In the Canvas set "Render Camera" to "Main Camera"
5. In Main Camera set "Projection" to "Orthographic"
6. Set size of "Main Camera" to 0
7. Notice that it corrupts all children of Canvas
8. Try to CTRL-Z, it doesn't bring corrupted children back
Actual result: The Cube is no more visible even if you bring main camera size to 5
Expected result: It should become visible after Main camera set to more than 0 or by using CTRL-Z
Reproduced in: 2018.3.0a5; 2018.3.5f1; 2019.1.0b2; 2019.2.0a4
Not reproducible: 2017.4.20f1; 2018.2.20f1
Can't test on 2018.3.0a4 or lower because there is no UI choice in the Editor
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
- Non-multisampled texture binding errors are logged when running the DepthBlit URP scene with MSAA enabled on Vulkan
- The Editor does not recognize code errors in generic classes when using C# Source Generator to generate serialization code
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
This is a duplicate of issue #1121834