Emulator Issues #11127
closed[Qt] Crash when starting emulation in exclusive fullscreen with D3D
0%
Description
Game Name?
Sure
Game ID? (right click the game in the game list, properties, info tab)
7
MD5 Hash? (right click the game in the game list, properties, info tab, MD5 Hash: Compute)
rf6756drtgui9o78fg6873d657asdfasdafds
What's the problem? Describe what went wrong.
Starting any game in Exclusive Fullscreen will cause a crash on D3D.
What steps will reproduce the problem?
- Set backend to D3D11
- Enable fullscreen
- Disable borderless fullscreen
- Start a game
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
Is the issue present in the latest stable version?
[Yes/No and version number here]
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.)
5.0-7437 breaks this.
https://dolphin-emu.org/download/dev/66c1b909c2697e3f3b3f306904e40204a443c7b2/
What are your PC specifications? (CPU, GPU, Operating System, more)
4790k
980ti on 397.64 drivers
Windows 10
Is there anything else that can help developers narrow down the issue? (e.g. logs, screenshots,
configuration files, savefiles, savestates)
Crash dump attached of it crashing with cached interp. See drive link
https://drive.google.com/open?id=1220YvVKqB63Egxt9q-f_P-oTEXy_tsc3
Updated by Helios almost 6 years ago
- Subject changed from [Qt] Crash when starting emulation in Fullscreen with D3D to [Qt] Crash when starting emulation in exclusive fullscreen with D3D
Updated by Helios almost 6 years ago
forgot the PDB file https://drive.google.com/open?id=1YjVrv-9_1NCJCOeLIpS9I_-HLImWgLY4
Updated by spycrab0 almost 6 years ago
- Status changed from New to Fix pending
- Assignee set to spycrab0
Updated by spycrab0 almost 6 years ago
- Status changed from Fix pending to Fixed
- Fixed in set to 5.0-7509