Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
3
Found in
6000.0.47f1
6000.1.1f1
Issue ID
UUM-104889
Regression
No
[Intel] Crash on BufferD3D12::BeginWrite when opening a newly created URP project with DirectX12 set as the default graphics API
Reproduction steps:
1. Create and open a new Universal 2D/3D project
2. Observe the crash
Reproducible with: 6000.0.47f1, 6000.1.0f1, 6000.1.1f1, 6000.1.0b3
Reproducible on: Windows 10 (1809) (user's), Windows 11 (24H2) (user's)
Not reproducible on: No other environments tested
Notes:
- Not reproduced by CQA
- Not reproducible with newly created BiRP project
- Not reproducible when launching Editor with -force-vulkan or -force-d3d11 command-line argument
First few lines of stack trace:
0x00007FFBDEE9EFD8 (Unity) BufferD3D12::BeginWrite
0x00007FFBDEBEC0E9 (Unity) GfxDevice::UpdateBufferRanges
0x00007FFBE063A75F (Unity) GfxDeviceWorker::RunCommand
0x00007FFBE063E6BC (Unity) GfxDeviceWorker::RunExt
0x00007FFBE063E7EF (Unity) GfxDeviceWorker::RunGfxDeviceWorker
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
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment