Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
0
Found in
2018.3.0a5
2018.4
2019.2
2019.2.11f1
2019.3
2020.1
Issue ID
1203097
Regression
Yes
Canvas with Screen Space - Camera Render ignores its Height value when Camera projection Matrix [0,2] or [1,2] value is not 0
How to reproduce:
1. Open the user-submitted project's Sample Scene
2. Inspect the Canvas GameObject in the Scene view
Expected result: Canvas GameObject's actual Height is 480
Actual result: Canvas GameObject's actual Height is close to 0
Reproducible with: 2018.3.0a5, 2018.3.14f1, 2018.4.14f1, 2019.2.16f1, 2019.3.0f2, 2020.1.0a16
Not reproducible with: 2017.4.35f1, 2018.3.0a4
Comments (2)
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
- A 404 page is opened when selecting "Open Documentation" on the Float Node in Shader Graph
- Shader Graph Importer's Documentation Reference button leads to a 404 page
- Crash on WriteParticleLineVertex when particle systems are rendered in a specific project
- Asset names longer than the allowed system file path are not handled gracefully
- Moving VFX Particles leave a ghosting trial in Ray Traced Screen Space Reflections
zORg_alex
Sep 18, 2021 13:46
It isn't fixed in 2021.1.12f1
jeepee-ef
May 25, 2020 07:16
Height seems fixed, but there is still an offset when rendering with a non-symmetrical projection matrix.