Search Issue Tracker
Fixed in 2022.3.8f1
Fixed in 2022.3.X, 2023.2.X, 2023.3.X, 2023.3.0a1
Votes
0
Found in
2022.3.6f1
2023.1.0b7
2023.2.0a5
2023.3.0a1
Issue ID
UUM-29955
Regression
Yes
Shader Dispatch event is not captured when using RenderDoc
Reproduction steps:
1. Open the attached project “IN-32136_RenderDocBug_STRIPPED”
2. Open the Scene “Assets/Scenes/SampleScene”
3. Open the Game View
4. In the Toolbar select the “Load RenderDoc” option
5. Enter the Play Mode
6. In the Toolbar press the Capture button
7. In the RenderDoc select the captured frame
8. In the Event Browser search for the Dispatch event
Expected result: The Dispatch event is captured by RenderDoc
Actual result: RenderDoc can not capture the Dispatch event
Reproducible with: 2022.2.0a16, 2022.2.11f1, 2023.1.0b7, 2023.2.0a5
Not reproducible with: 2020.3.46f1, 2021.3.20f1, 2022.2.0a15
Reproducible on: Windows 11, Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Add comment