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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
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.