Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
1
Found in
6000.0.51f1
6000.1.8f1
6000.2.0b6
6000.4.0a1
Issue ID
UUM-109659
Regression
No
Compute and graphics queues are not run asynchronously when asynchronous compute shaders are enabled in DX12
How to reproduce:
1. Open the attached “IN-101628” project
2. Navigate to Edit → Project Settings → Graphics → Asynchronous Compute Shaders, and ensure that “Asynchronous Execution” is enabled
3. Select File → Build Profiles and ensure “Development Build” is enabled
4. Select “Build”
5. Once the project is done building, open PIX
6. Select “Launch Process” and set the “Executable Path” to the built project
7. Ensure “GPU Capture” is selected, and press “Launch”
8. Once the Player is launched, open the PIX window and select “Take Capture” in the top left corner
9. Close the Player
10. In the “Captures” tab in PIX, double click the capture
11. Start analysis and collect timing data by selecting “Click Here” in the “Timeline” tab
12. Observe the result in the “Timeline” tab
Expected result: The compute and graphics queues run asynchronously
Actual result: The compute and graphics queues do not run asynchronously, introducing unnecessary wait instructions
Reproducible with: 2023.3.0b1, 6000.0.51f1, 6000.1.8f1, 6000.2.0b6
Could not test with: 2022.1.0a1, 2022.3.63f1, 2023.3.0a1 (No asynchronous compute shader execution setting)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: PIX can be downloaded here:https://devblogs.microsoft.com/pix/download/
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
Add comment