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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment