Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.1.X
Votes
0
Found in
2021.3.47f1
2022.3.55f1
6000.0.32f1
6000.1.0a9
7000.0.0a1
Issue ID
UUM-91185
Regression
No
Shadow maps are not evicted from Shadow Atlas when Light component with "preserveCachedShadow" property set to false is disabled
Reproduction steps:
1. Open the attached project “IN-90971“
2. Open the scene “ExampleScene“
3. Open the Rendering Debugger. Go to Window → Analysis → Rendering Debugger
4. Open the Lighting tab and for the Shadow Debug Mode option, select “Visualize Cached Punctual Light Atlas“
5. Enter Play Mode
6. Try toggling the light components using UI provided
7. Observe the result
Expected result: Disabling the light components with preserveCachedShadow disabled should evict their light texture from the shadow atlas
Actual result: Disabling the light components with preserveCachedShadow disabled did not evict their light texture from the shadow atlas. Thus, other light components with preserveCachedShadow disabled are unable to be added to the shadow atlas.
Reproducible in: 2021.3.47f1 2022.3.55f1, 6000.0.32f1, 6000.1.0a9
Reproducible on: macOS 14.6.1 (M1 Pro), Windows 10
Not reproducible on: No other environments tested
Note:
* Also reproducible in Player
* To enable “Visualize Cached Punctual Lights Atlas” option in Player. Enable “Development Build“ before building a Player, then press LeftCtrl+Backspace (LeftCtrl+Delete on macOS) to open the Rendering Debugger Menu. Open the Lighting tab and for the Shadow Debug Mode option, select “Visualize Cached Punctual Light Atlas“. Close the Debugger menu by pressing the same combination of buttons. Make sure that “Runtime Debug Shaders“ option is enabled in HDRP Global Settings asset
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Dragon Crashers] Build fails in U6
- [Dragon Crashers] 4 Shader error messages on import
- [Dragon Crashers] Readme text is white on light grey
- Cursor stays in front of the first character when entering text in the TextMeshPro field
- Searching in Hierarchy causes unwanted component calls
Add comment