Search Issue Tracker
By Design
Votes
0
Found in
6000.0.11f1
Issue ID
UUM-75905
Regression
No
[URP] Surfaces turn black briefly when lights are moved
How to reproduce:
1. Open the user's attached project
2. Enter Play Mode
3. Click the "Create Room" button in the Game view window
4. Click the "Start Game" button
5. Select a light in the scene view, move it slightly
Expected results: No surfaces turn black for a single frame
Actual results: Sections of upward-facing surfaces turn black for a single frame
Reproducible with: 6000.0.11f1
Could not test with: 2021.3.40f1, 2022.3.38f1 (compilation errors in the Console window)
Reproducible on: Windows 10 22H2
Not reproducible on: No other environment tested
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
- SystemInfo.get_graphicsDeviceName() is generating garbage GC Alloc when using Metal graphics API
- Crash on D3D12CommonShader::ApplyGpuProgram when attaching material which samples "_UnityFBInput0" to "Full Screen Pass Renderer Feature" Component
- SpeedTree meshes and objects count differs when comparing the numbers in the Player with the Editor
- Model and Prefab Preview icons are not updated after upgrading associated Materials to URP
- Game view is rendered white when viewing the Editor with HDR display and Post Proccesing is enabled on the Main Camera with 2D URP
Resolution Note:
I think it is a shadowmap behavior and there's a workaround, changing the near-plane value to draw more accurately.
This flickering happens because the position of the point light is changed every frame by a custom script to make the light look more realistic. Therefore, the depth rendering output on the shadowmap changes every frame, so the flicker is 100% reproducible. When I changed the shadowmap resolution from D16 to D32, the flickering happened more.
However, if the near-plane value is set to a higher value, such as 1.0, the flickering hardly happens or even disappears. This is because as the near-plane value gets higher, the shadow map covers a narrower range of area, so the depth rendering output for the close objects becomes more precise.
Due to the shadowmap constraints such as the texture resolution and the light movement, the sampling result changes every frame. This is the reason for the flickering problem here, so it looks like it's better to find the proper shadow settings here.