Just got a hand-me-down Lenovo Y570 from my brother. Kinda old, not the best laptop in the world, but good enough for what I need it for, i.e. running Dolphin. One problem though; I get a "Failed to initialize Direct3D" error when I try to use Direct3D 11 (on Faster Melee 5.8.7) and Direct3D 12 (on 5.0-321. And yes, I already know the backend isn't being maintained etc but it's still the best option for me.) I don't get the error on 5.8.7, it just crashes immediately upon selecting the D3D12 backend, and if I try to change it manually with dolphin.ini I get a black screen. I've installed all the drivers I can think of, my graphics drivers are as up to date as possible, my DirectX runtime is the newest version, and at this point it's beyond my scope of knowledge. I've attached my dxdiag below and I would attach a log as well, but nothing shows up in the log file after the crashes.
[
attachment=16764]
EDIT: Noticed "ucrtbase.dll" mentioned as having some sort of error with regards to Dolphin in the dxdiag, checked event viewer and sure enough, it was there as well. I copied the information and put it into a txt file, which I have attached below.
[
attachment=16765]
We don't support faster melee. You'll have to get support from them
(01-18-2018, 06:24 AM)Helios Wrote: [ -> ]We don't support faster melee. You'll have to get support from them
And I'm assuming you won't help with 5.0-321 because my problem is with DX12...?
Does Direct3D 11 work in any official release? (For instance 5.0-321 or the latest development build)
(01-18-2018, 06:44 AM)JosJuice Wrote: [ -> ]Does Direct3D 11 work in any official release? (For instance 5.0-321 or the latest development build)
In 5.0-321, yes. I am now getting a loop of "Entered Exclusive Fullscreen/Lost Exclusive Fullscreen," however. The screen tearing issues are also much less than ideal, but I suppose if worst comes to worst...
I'll give the latest development build a shot and see if anything changes.
UPDATE: Direct3D 11 does NOT work in the latest development build. Just in 5.0-321.
Did a repair installation of Windows, because I thought the DLL might be causing the issue. Now I can't use Direct3D backends on ANYTHING. I'm seriously confused as to what's going on now. Attaching the Event Viewer details and my most recent dxdiag results.
[
attachment=16772]
[
attachment=16773]
Did some quick research: DirectX 12 is not supported by the Intel HD Graphics 3000
https://software.intel.com/en-us/forums/...pic/647102
Quote:Coppock, Michael J (Intel) Fri, 07/01/2016 - 07:00
In order for HD 3000 to work with DX12 a new graphics driver enabling support is required. There are no plans for any further drivers for HD 3000 graphics.
And it officially doesn't even support DirectX 11 as stated here, the latest version its drivers support is 10.1:
https://www.intel.com/content/www/us/en/...ivers.html
Quote:DirectX*: 10.1
OpenGL*: 3.1
OpenCL*: No
Shader Model Support: 4.1
Intel® Quick Sync Video: Yes
Intel® Wireless Display: Yes
Intel® Insider™ technology: Yes
Intel® InTru™ 3D Technology: Yes
Intel® Clear Video HD Technology: Yes