Search Issue Tracker
By Design
Votes
1
Found in
2019.4
2020.2
2020.2.1f1
2021.1
2021.2
Issue ID
1311336
Regression
No
[HDRP] Editor freezes when Graphics.SetRandomWriteTarget is called in Play Mode
How to reproduce:
1. Open the user's attached "Dynamic Damage Test.zip" project
2. Open the "New Scene" Scene
3. Enter Play Mode
Expected result: Editor doesn't freeze
Actual result: Editor freezes
Reproducible with: 2019.4.21f1 (7.5.3), 2020.2.6f1 (10.3.1), 2021.1.0b8 (11.0.0), 2021.2.0a6 (12.0.0)
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
- Opening Terrain Prefab in Prefab Editing Mode throws "NullReferenceException" error
- [Search] Dragging query pills put them behind the search text field
- A CustomPropertyDrawer that returns a PropertyField for a property named the same as a child field will not render all child fields
- Graphics Settings shows default values instead of the real values in the Rendering Debugger when Volume.profile is assigned via script
- Deleting multiple Tags throws “NullReferenceException”, and "Retrieving array element that was out of bounds" errors when holding the Enter key
Resolution Note:
Documentation states that "The targets stay set until you manually clear them with ClearRandomWriteTargets". If you fail to call clear, the subsequent Unity rendering passes will user your overloaded write targets. This might cause a GPU crash on some platforms as the data is not what the shader expects. We will improve the documentation by making it more clear that ClearRandomWriteTargets is very important to call.