Search Issue Tracker
Won't Fix
Votes
5
Found in
2018.2.17f1
2019.2
2019.3
2020.1
Issue ID
1103727
Regression
No
Editor crashes with D3D12SwapChain::CreateHWND when switching to Direct3D12 on AMD card after Windows Update
How to reproduce:
1. Create new project
2. Open Project Settings/Player tab
3. Under Other Settings disable "Auto Graphics API for Windows" checkbox
4. Add Direct3D12 Graphics API and drag it above Direct3D11
--------------
Observe crashing
Reproduced with: 2018.3.1f1, 2019.1.0a13, 2020.1.0a3
Note: Issue only reproduces with AMD cards and Windows 1809 update
Comments (4)
- 
        PaulDyatlov Jul 27, 2020 10:46 Direct3D 12 don't support creating MSAA swap chains--attempts to create a swap chain with SampleDesc.Count > 1 will fail 
- 
        arsys Apr 10, 2020 14:02 happens in EVERY project, new or existent, with every version I have installed, I updated to latest LTS 2018.4.20f1 and 2019.3.9f1 with same results. The crash log states: atidxx64.dll caused an Access Violation (0xc0000005) in module atidxx64.dll at 0033:e4834a0f. I have Windows 10 Home 1909, in a Dell Inspiron 3576 with Radeon 520 integrated chip returning configuration from GAME to STANDARD in the Radeon Adrenalin software solves the issue. 
- 
        SkeletonDoctor Jan 21, 2020 03:09 I haven't had any issue with Vulkan, but that's just me. 
- 
        Theironlefty Feb 24, 2019 14:14 Also happens when switching to Vulkan API. 
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
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- Addressables Profiles and Analyze windows no minimum window size
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note (2019.1.X):
The crash is an AMD driver issue