Hi, everyone! I haven't had the need to post much here in a while because, frankly, Dolphin has been so stable I haven't had much in the way of issues. Especially since I did a recent upgrade to me PC. Unfortunately, there is always a time for major bugs and I was hoping to get someone else to help be confirm this before I go cluttering up the Dolphin issue tracker.
SO! I am playing Wario World NTSC-U at this point and have had some major issues here. This crash is reproducible, at least for me. What happens is when you hit start, AFTER the first memory card save has been created, just as Wario starts to jump into the frame the game, video driver, all of it has a hard meltdown. My TV goes completely black, no video output at all and I have to reset my PC the hard way by getting up and hitting the reset button and it boots fine. Now, I am using my steam controller, my new best friend, and the DX12 backend. My first thought was that the Steam overlay was doing some shenanigans again and after testing, still happened. I am using the 16/9 gecko code but disabling cheats didn't help either.
I changed the backend last because to my knowledge the settings I was using were working less than five minutes before, but change it I did. DX11 works a treat without the crash. I know I should just use the DX11 backend, and I am, no worries there but I have some thoughts on how this is behaving that might help in some way. If not then whatever but I am going to say it anyways.
These are the reasons I think I am experiencing perhaps a driver bug? Maybe something specific to an AMD card that hasn't been uncovered until Dolphin is using certain DX12 features or CEMU using OpenGL in a strange way. Sorry about even mentioning CEMU but since the crash is precisely identical in every way I figured it may be relevant for troubleshooting at least.
Here are my specs as I am sure this will be needed for anyone who might want to attempt to recreate this specific issue for me.
CPU: Intel Core i5-6600K @4.5Ghz GPU: Sapphire R9-380 OC @ ~1010Mhz OS: WIndows10 Pro x64
BTW, I also use my IGPU regularly for Quick Sync so it is on and as I stated before I usually use my steam controller and it's overlay hooks into the render pipeline in some strange ways but I DID test without it and it still happened.
Thank you to anyone who can help me confirm!
EDIT: Sorry, I forgot to mention I am using 16GB DDR4 @3000 and my Dolphin build is 4.0-9211
SO! I am playing Wario World NTSC-U at this point and have had some major issues here. This crash is reproducible, at least for me. What happens is when you hit start, AFTER the first memory card save has been created, just as Wario starts to jump into the frame the game, video driver, all of it has a hard meltdown. My TV goes completely black, no video output at all and I have to reset my PC the hard way by getting up and hitting the reset button and it boots fine. Now, I am using my steam controller, my new best friend, and the DX12 backend. My first thought was that the Steam overlay was doing some shenanigans again and after testing, still happened. I am using the 16/9 gecko code but disabling cheats didn't help either.
I changed the backend last because to my knowledge the settings I was using were working less than five minutes before, but change it I did. DX11 works a treat without the crash. I know I should just use the DX11 backend, and I am, no worries there but I have some thoughts on how this is behaving that might help in some way. If not then whatever but I am going to say it anyways.
- UNLIKE DX11, DX12 seems to have the last rendered frame of whatever I was playing before pop up for a split second before it will start rendering anything from a new game I load.
- If this phantom frame happens, and it does not always but often after the second game load from a clean boot, Dolphin will become unstable and is almost assured to just crash out very soon. As in withing about 10 minutes nearly always.
- I have dabbled a bit in the CEMU emulator just for kicks in the last week or so and, funny enough, their latest 1.4.1 crashes in EXACTLY the same way at the MK8 loading screen. no video output and everything but they use OpenGL exclusively.
- I am using the latest AMD 16.3 drivers and they are seemingly having issues with others randomly describing some similar crashing with unrelated games/emulators and such.
These are the reasons I think I am experiencing perhaps a driver bug? Maybe something specific to an AMD card that hasn't been uncovered until Dolphin is using certain DX12 features or CEMU using OpenGL in a strange way. Sorry about even mentioning CEMU but since the crash is precisely identical in every way I figured it may be relevant for troubleshooting at least.
Here are my specs as I am sure this will be needed for anyone who might want to attempt to recreate this specific issue for me.
CPU: Intel Core i5-6600K @4.5Ghz GPU: Sapphire R9-380 OC @ ~1010Mhz OS: WIndows10 Pro x64
BTW, I also use my IGPU regularly for Quick Sync so it is on and as I stated before I usually use my steam controller and it's overlay hooks into the render pipeline in some strange ways but I DID test without it and it still happened.
Thank you to anyone who can help me confirm!
EDIT: Sorry, I forgot to mention I am using 16GB DDR4 @3000 and my Dolphin build is 4.0-9211
![[Image: RPvlSEt.png]](https://i.imgur.com/RPvlSEt.png)