Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.2.X
Votes
0
Found in
2019.4
2020.1
2021.1
Issue ID
1358451
Regression
Yes
CanvasScaler does not scale UI in relation to Camera Viewport Rect size
CanvasScaler does not scale UI in relation to Camera Viewport Rect property size when Canvas Render Mode is set to Screen Space - Camera
Reproduction steps:
1. Open the attached project
2. Open SampleScene in the Assets/Scenes folder
3. Open Game View
4. Select Main Camera in the Hierarchy menu
5. In the Main Camera Inspector window modify the Viewport Rect component H Value in 0 - 1 decimal range
6. Observe how Canvas UI elements scale
Expected results: UI scales in relation to Camera Viewport Rect size
Actual results: UI does not scale in relation to Camera Viewport Rect size
Reproducible with: 2019.4.21f1, 2020.1.0a1, 2020.2.6f1, 2021.1.0a1, 2021.1.0a7
Not reproducible with: 2019.4.22f1, 2019.4.29f1, 2020.2.7f1, 2020.3.17f1, 2021.1.0b9, 2021.1.17f1, 2021.2.0b9, 2022.1.0a6
Could not test with: 2021.1.0a8, 2021.1.0b8 (another issue - https://issuetracker.unity3d.com/issues/viewport-rect-affects-ui-canvas-gameobjects-positions-when-canvas-render-mode-is-set-to-screen-space-camera - makes this issue untestable)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2021.1):
Fixed in: 2021.1.0b9
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.7f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.22f1