Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
12
Found in
6000.0.66f1
6000.3.4f1
6000.4.0b5
6000.5.0a5
Issue ID
UUM-132599
Regression
No
High MeshSkinning duration when using Vulkan
How to reproduce:
1. Extract and open the attached “IN-130133.zip“ project
2. Navigate to “File” → “Build Profiles”
3. Select “Windows” and “Build” the project
4. Download, install, and open “RenderDoc”
5. Select the “Launch Application” tab
6. In the “Executable Path” field, enter the built project’s executable path
7. In the “Command-line Arguments” field, enter “--force-vulkan“
8. Press the “Launch“ button
9. Once the project is running, click the “Capture Frame(s) Immediately“
10. Double-click the capture in the “Captures collected:“
11. Navigate to the “Event Browser”
12. In the “Filter“ field, enter “MeshSkinning.SkinOnGPU“ and press Enter
13. If needed, expand the “FrameTime.GPU” entry and select “MeshSkinning.SkinOnGPU”
14. Navigate to the top of the “Event Browser“ and click the clock icon
15. Observe the value in the “Duration” column in the “MeshSkinning.SkinOnGPU“ row
Actual result: Duration is significantly higher with Vulkan than with DirectX11 or DirectX12
Expected result: Duration should be comparable across all graphics APIs
Reproducible with: 2023.1.0a1, 6000.0.66f1, 6000.3.4f1, 6000.4.0b5, 6000.5.0a5
Reproducible on: Windows 11 (Nvidia RTX 3500)
Not reproducible on: Windows 11 (AMD RX 6800 XT)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment