Search Issue Tracker
Fixed
Fixed in 2021.3.28f1, 2022.2.15f1, 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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Add comment