Search Issue Tracker
Fixed
Votes
0
Found in [Package]
7.1.1
Issue ID
1210093
Regression
Yes
[URP][macOS] Game View is overlayed by background color when Background Type Solid Color property is selected
How to reproduce:
1. Create a new project and install URP via Package Manager
2. Right-click in Project Browser > Create > Rendering > Universal Render Pipeline > Pipeline Asset
3. Edit > Project Settings > Graphics > Select RenderPipelineAsset > UniversalRenderPipelineAsset
4. Select the Main Camera in the Hierarchy
5. Change Background Type to Solid Color in the Inspector
Expected result: Game View is not overlayed by Camera's component Solid Color background
Actual result: Game View is overlayed by Camera's component Solid Color background
Reproducible with: 7.1.1 (2019.3.0b4, 2020.1.0a19), 7.1.7(2019.3.0f4, 2020.1.0a19)
Not reproducible with: 4.10.0(2018.4.15f1) 6.9.0, 6.9.2(2019.2.18f1), 7.0.0(2019.3.0a12), 7.0.1(2019.3.0b12, 2020.1.0a11)
Could not test: 2017.4.36f1 Package Manager is not introduced
Notes:
- More information and screenshot of actual result attached in Edit
- Not reproducible on Windows(DirecX11, OpenGLCore, Vulkan)
- Tested macOS 10.13.6, 10.15.2
- Reproducible on macOS (Metal, OpenGLCore)
- Not reproducible if a new URP project created via Hub
Comments (1)
-
DomeCreator
Jan 20, 2021 14:55
This regression come back on Unity 2020.2.1f1.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
Fixed in 2020.1.0a22, backported to 2019.3.1f1