Project

General

Profile

Actions

Emulator Issues #13490

open

D3D12 Crashes Dolphin when booting any Wii game on intel iGPU's and ARC GPU's

Added by ZeronXR about 2 months ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

Any game: Tested with Pandora's Tower, Last Story, and Twilight Princess (GCN)

Game ID? (right click the game in the game list, Properties, Info tab)

SX3P01 (0001000053583350)
SLSP01 (00010000534c5350)
GZ2P01
Respectively

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

904107ea0244217827a23013ac9c7581
06ac8678014fc99c9d129ce25de6a6e3
f9c47b0c8a34d345c06061f24e0db277
Respectively

What's the problem? Describe what went wrong.

On Dolphin version 5.0.21088 launching any Wii game using the DirectX 12 API, with an intel iGPU or ARC GPU [Theorised], will crash Dolphin.
The DirectX 11 API still functions as normal.

What steps will reproduce the problem?

Launch Dolphin > Go to graphics settings > change the api to Directx12 > Launch a Wii game > Game screen goes black as the game boots > Dolphin crashes

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

Yes, 5.0.21088

Is the issue present in the latest stable version?

No, 5.0

If the issue isn't present in the latest stable version, which is the first broken version? (You can find the first broken version by bisecting. Windows users can use the tool https://forums.dolphin-emu.org/Thread-green-notice-development-thread-unofficial-dolphin-bisection-tool-for-finding-broken-builds and anyone who is building Dolphin on their own can use git bisect.)

Beta Version: 5.0-20347 (5.0-19870 does not experience the issue)
Development Version: Unknown

If your issue is a graphical issue, please attach screenshots and record a three frame fifolog of the issue if possible. Screenshots showing what it is supposed to look like from either console or older builds of Dolphin will help too. For more information on how to use the fifoplayer, please check here: https://wiki.dolphin-emu.org/index.php?title=FifoPlayer

N/A

What are your PC specifications? (CPU, GPU, Operating System, more)

OS Windows 11 Home
Processor Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz 1.50 GHz
Intel Iris Plus Graphics
Graphics Driver Vers. 31.0.101.2127
Installed RAM 16.0 GB (15.6 GB usable)
System type 64-bit operating system, x64-based processor

Even with these specifications I am able to run games at 3x Native resolution in DirectX 11 at full speed

Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)

It appears that this issue exists on intel ARC GPU's as well due to this post on the intel community:
https://community.intel.com/t5/Intel-ARC-Graphics/Direct-X-12-crash-Dolphin-Emulator/m-p/1576258

Actions #1

Updated by ZeronXR about 2 months ago

Correction:
Issue is present in the latest development build, 5.0-21172

Actions #2

Updated by Dentomologist about 2 months ago

The following three versions made changes to the VideoBackends/D3D12 folder in that window of time which is the obvious place to start looking:

5.0-19872 (previous version 5.0-19870, which you already tested and found unaffected)
5.0-19912 (previous version 5.0-19907)
5.0-20221 (previous version 5.0-20215)

Do any of those three versions have the problem while the corresponding previous version doesn't?

Actions #3

Updated by ZeronXR about 2 months ago

Thank you for directing me further, and yes!

Builds 5.0-19872 & 5.0-19912, are working perfectly with DirectX 12, however
build 5.0-20221 has the issue and in the exact same way the current build does.
For posterity I can confirm the previous version 5.0-20215 does not have the issue.

I believe we can isolate this issue to build 5.0-20221

Actions

Also available in: Atom PDF