Search Issue Tracker
Fixed in 2019.2.X
Votes
0
Found in
2019.2.0a6
Issue ID
1127388
Regression
Yes
[DirectX 12] Editor crashes on switching Windows Graphics APIs to Direct3D12
Editor crashes on switching Windows Graphics APIs to Direct3D12
Steps to reproduce:
1. Create a new project
2. File > Build Settings > Player Settings
3. Other Settings > Uncheck "Auto-Graphics API for Window" checkbox.
4. Add Direct3D12 > move to the top of the list > Apply.
Actual Result:
Editor crashes.
Expected Result:
Graphics APIs switches to Direct3D12.
Reproducible on:
2019.2.0a6
Works fine on:
2019.2.0a5, 2019.1.0b3
Environment:
Occurs only on Windows
========== OUTPUTTING STACK TRACE ==================
0x00007FF7572A1EFA (Unity) GfxDeviceD3D12::BeginFrame
0x00007FF757303338 (Unity) GfxDeviceWorker::RunCommand
0x00007FF75730A62B (Unity) GfxDeviceWorker::RunExt
0x00007FF75730A9F5 (Unity) GfxDeviceWorker::RunGfxDeviceWorker
0x00007FF7580FFF87 (Unity) Thread::RunThreadWrapper
0x00007FF9C72D3DC4 (KERNEL32) BaseThreadInitThunk
0x00007FF9C7DE3691 (ntdll) RtlUserThreadStart
========== END OF STACKTRACE ===========
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
- MeshRenderer.sortingLayerID cannot be changed when change is being done in a built Player
- Warnings related to App Icon are being thrown when building project to VisionOS Platform
Bartosz-Bieszka
Oct 04, 2021 19:10
It's still not fixed
create3dgames
Dec 23, 2020 01:31
Why is this marked as fixed? It isn't.