Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X
Votes
0
Found in
2021.3.43f1
2022.3.43f1
6000.0.16f1
Issue ID
UUM-78487
Regression
No
D3D11 Compute shader dispatch isn't synchronous when running in the Editor
Steps to reproduce:
1. Open the attached user's project "Compute Woes.zip"
2. Make sure that the Graphics API is set to D3D11
3. Open the "SampleScene.unity" and watch for red messages in the console
4. If you don't see any red messages, make sure the scene view is open and visible, and restart the Editor
Expected results: D3D11 Compute shader dispatch is synchronous when running in the Editor
Actual results: D3D11 Compute shader dispatch isn't synchronous when running in the Editor
Reproducible with: 2021.3.43f1, 2022.3.43f1, 6000.0.16f1
Testing Environment: Windows 11 23H2
Not reproducible on: Windows 10
Notes:
-Issue does not reproduce with D3D12 or OpenGL
-According to the user, steps that make the bug disappear:
*Dispatching an empty compute shader kernel after the real dispatch
*Attaching nvidia nsight
*Storing _BoxAction in a compute buffer instead of an int property
*Instantiating the compute shader, using different instances for the apply case, and another for the preview case
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Spot Light with 'Box' Shape stops working when it collides with Mesh
- Accepting Asset Store EULA endless loop in Package Manager window
- “InvalidOperationException: Sequence contains no matching element“ error when reenabling a custom Debug Draw Mode
- Prefab that contains a layout group is marked as changed by the Editor when opened
- Emission animation does not appear when the "Emission Map" parameter is set to black in a Lit material
Add comment