Search Issue Tracker
Duplicate
Votes
2
Found in
2022.3.20f1
Issue ID
UUM-64095
Regression
Yes
Canvas keeps changing size when “Physically Based Sky” is enabled and an Image or RawImage GameObject is selected
Reproduction steps:
1. Open the attached "Playground-22" project
2. Open "Assets/OutdoorsScene" scene
3. In the Hierarchy window, expand the "Canvas" GameObject and click on "Image" GameObject to open its' Inspector window
4. Observe the results
Expected results: The Canvas does not flicker or change size
Actual results: The Canvas keeps changing size
Reproducible with: 2022.3.18f1, 2022.3.20f1
Not reproducible with: 2021.3.35f1, 2022.3.17f1, 2023.2.10f1, 2023.3.0b7
Reproducible on: Windows 11 Pro
Not reproducible on: No other environments tested
Notes:
- Reproducible in both the Scene view and Game view
- Reproducible with both Image and RawImage GameObjects
- Not reproducible when the “Physically Based Sky” Component is disabled in the “Sky and Fog Volume” GameObject
- When the “Physically Based Sky” component is disabled and the Image is selected, the Image sometimes is rendered in the corner of the Game view or in the center but zoomed out, switching between the Canvas GameObject and the Image GameObject fixes this
-
Resolution Note:
Duplicate. Already fixed.
Summary:
Branch:2022.3.X
Resolution: Fixed
Fix Versions: 2022.3.21f1
Resolution Notes:
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-63694
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
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
- [Mobile] The Material is not visible when using the Decal Renderer Feature
- Uncaught TypeError: Cannot read properties of undefined is thrown when the tab is inactive for several minutes
- Crash on mono_array_length when building a project
- "StackOverflowException" error when changing spline curve type from "Bezier" to "Auto" in the "Element Inspector"
This is a duplicate of issue #UUM-63694