Search Issue Tracker
Fixed in 2021.3.28f1
Fixed in 2021.3.X, 2022.2.X, 2023.1.X, 2023.1.0b1
Votes
0
Found in
2021.3.13f1
2022.1.22f1
2022.2.0b14
2023.1.0a17
Issue ID
UUM-18616
Regression
Yes
[Linux][Windows][MacOS][Quest] Shader Prefiltering/Stripping does not take disabled Renderer Features in to account.
Reproduction steps:
1. Open the user’s attached project
2. Open the “Assets/Scenes/SampleScene.unity” scene
3. Click “Assets/Pipeline/Repro-renderer.asset”
4. In the Inspector window, under “Renderer Features”, make sure the “Screen Space Ambient Occlusion” Renderer Feature is disabled
5. Click File > Build And Run
6. In Player, observe the scene
Expected result: Player “SampleScene” scene looks the same as in Editor Game View
Actual result: Player “SampleScene” scene is darker than in Editor Game View
Reproducible with: 2021.3.4f1, 2021.3.13f1, 2022.1.2f1, 2022.1.22f1, 2022.2.0a14, 2022.2.0b14, 2023.1.0a17
Not reproducible with: 2020.3.41f1, 2021.3.3f1, 2022.1.0a1, 2022.1.1f1, 2022.2.0a1, 2022.2.0a13
Reproducible on: Ubuntu 20.04.5, Windows 10
Note: if you remove the SSAO RenderFeature from the Renderer and build again, the scene will be as it is in the GameView
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- GameObjects change Hierarchy order when undoing adding Component to multiple GameObjects
- [macOS] Editor crashes after entering Play mode with overlapping GameObjects with Cloth Component and Cloth Inter-Collision enabled
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
Add comment