Search Issue Tracker
Fixed
Fixed in 2021.3.18f1, 2022.2.0b13, 2023.1.0a13
Votes
0
Found in
2021.3.7f1
2022.1.11f1
2022.2.0b7
2023.1.0a9
Issue ID
UUM-12397
Regression
No
Shadows get messed up when using Screen Space Shadows
To reproduce:
1. Open the project “ReflectionProbeTest”
2. Select “Reflection Probe” GameObject in the Hierarchy
3. Notice the messed-up shadows in the Reflection Probe map
4. Edit → Project Settings → Graphics → Universal render Pipeline Asset → Renderer → disable Screen Space Shadows
5. Select “Reflection Probe” GameObject in the Hierarchy
6. Click Bake, Inspector → Reflection Probe
7. Notice the correct shadows in the Reflection Probe map
Expected result: There should not be any visual difference if Screen Space Shadows are on or off
Actual result: Screen Space Shadows messes up the shadows
Reproducible with: 2021.3.7f1, 2022.1.11f1
Could not test with: 2020.3.38f1, 2022.2.0b3, 2023.1.0a4 (Console errors)
Reproduced on: macOS Monterey 12.4 (Intel)
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
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
Resolution Note:
Fixed by another internal issue: UUM-2519: [URP] Depth priming doesn't work on GLES when MSAA is enabled