Emulator

I have tested all the beta builds listed on the downloads page back to 5.0-11333 and am experiencing the same problem with all the builds. Other back ends don't appear to exhibit this problem, further testing is needed to confirm.

I would just switch to another back end, but I use Parsec to stream my gaming setup and DX12 offers the smoothest performance. All other backends occasionally stutter, but this doesn't appear to be related to shader compilation.

That is really odd, I don't know how a texture create would fail in this very specific case. Does it happen in any other games?

I have not personally experienced this issue with any other title, all my other games chug along quite nicely.

I noticed issue 12227 posted has Skyward Sword crashing with the same error, but the circumstances appear to be a little more duplicatable.

https://bugs.dolphin-emu.org/issues/12227

Yeah, this is weird though because the Skyward Sword issue only occurs on AMD. I'm not sure it's the same bug. My question is why don't you just use any other video backend in the meantime? All backends should perform equally well for this game, as it doesn't use a lot of draw calls. I personally use Vulkan is my primary backend.

Can you please test this again on the latest Beta?

If that doesn't work then can you test this version below. This is when D3D12 was re-implemented into Dolphin.

5.0-9878 -> https://dolphin-emu.org/download/dev/a2a4694497e71dbe4e033b6bd5f6224bf0af637e/

ZephyrSurfer wrote:

Can you please test this again on the latest Beta?

If that doesn't work then can you test this version below. This is when D3D12 was re-implemented into Dolphin.

5.0-9878 -> https://dolphin-emu.org/download/dev/a2a4694497e71dbe4e033b6bd5f6224bf0af637e/

I get the same bug in the latest beta, and in 5.0-9878. I actually opened a bug report for it.

I was able to reproduce this once, but only on dual core. I used the yoshi stampede attack, and then savestated near the start of the animation (after completing all inputs). Loading that savestate produces nondeterministic results, including unknown opcodes and other things that indicate bad fifo behavior, hangs, and once this message.

Dual core in general interacts poorly with TTYD, and I'm not sure how fixable it would be. My basic, flawed understanding of it is that TTYD has some kind of system to detect hangs and reset the graphics system if that happens, and dual core triggers it repeatedly whenever something takes slightly too long; and when it does get reset, that often breaks what's happening in Dolphin (for some reason). But I don't fully understand how that system works or why dual core breaks it.

If you've run into this DX12 crash in single core, please let me know.

here is information about TDR https://learn.microsoft.com/en-us/windows-hardware/drivers/display/tdr-registry-keys
if it's triggered, it's very likely the gpu actually is crashed/hung (and not that it just needs a bit more time)

pokechu22 wrote in #note-9:

I was able to reproduce this once, but only on dual core. I used the yoshi stampede attack, and then savestated near the start of the animation (after completing all inputs). Loading that savestate produces nondeterministic results, including unknown opcodes and other things that indicate bad fifo behavior, hangs, and once this message.

Dual core in general interacts poorly with TTYD, and I'm not sure how fixable it would be. My basic, flawed understanding of it is that TTYD has some kind of system to detect hangs and reset the graphics system if that happens, and dual core triggers it repeatedly whenever something takes slightly too long; and when it does get reset, that often breaks what's happening in Dolphin (for some reason). But I don't fully understand how that system works or why dual core breaks it.

If you've run into this DX12 crash in single core, please let me know.

If the dual core setting you're talking about is "Settings > General > Enable Dual Core (speedup)" then I already had it off.