Search Issue Tracker
Fixed
Fixed in 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a2
Votes
0
Found in
6000.0.49f1
6000.1.2f1
6000.2.0b1
6000.3.0a1
Issue ID
UUM-105820
Regression
No
Crash on D3DKMTOpenResource when capturing with RenderDoc while GPU Skinning is set to GPU(Batched)
Reproduction steps:
1. Open the attached project "CrashRepro"
2. Load RenderDoc (Alt + C or the first option in the game view window burger menu)
Expected result: Editor crashes
Actual result: renderDoc image gets loaded
Reproducible with: 6000.0.49f1, 6000.1.2f1, 6000.2.0b1
Couldn’t test with: 2022.3.62f1 - no option to set gpu skinning to “GPU(Batched)“
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
RenderDoc needs to be installed to reproduce
Does not crash with “GPU skinning*“ set to anything other than “Gpu(Batched)“
First few lines of stack trace:
{noformat}0x00007FFEFC0C2E17 (d3d11) D3DKMTOpenResource
0x00007FFEFC0ECE2C (d3d11) D3DKMTOpenResource
0x00007FFE17DE4971 (renderdoc) RENDERDOC_EndProfileRegion
0x00007FFE28205E28 (Unity) UnityMain
0x00007FFE2820C2EC (Unity) UnityMain
0x00007FFE2820C41D (Unity) UnityMain{noformat}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- 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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment