Search Issue Tracker
Fixed
Votes
1
Found in
6000.0.24f1
6000.1.0a2
Issue ID
UUM-85457
Regression
Yes
Errors are thrown and the view is not rendered properly when using Overlay Camera with Non-Default 2D Renderer
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Observe the Scene view and Console window
Expected result: No errors are thrown and the view is rendered correctly
Actual result: Errors are thrown and the view is flickering
Reproducible with: 6000.0.20f1, 6000.0.24f1, 6000.1.0a2
Not reproducible with: 2021.3.44f1, 2022.3.51f1, 6000.0.19f1
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Note: Setting the Overlay Camera's render type to Base resolves the issue
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
- 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
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-83013