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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [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
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.