Dolphin, the GameCube and Wii emulator - Forums

Full Version: Texture issues with Direct3D 11
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
First off, apologies if this is in the wrong place, missing info, etc. I'm new to forums! I read up on the rules but I'm sorry if I still mess up.

Anyways, my problem I'v been having with Dolphin lately is that my games have been experiencing an odd glitch with the textures. Not just in one game but all of them, and they all look fairly the same in each game. Here's an example:

[Image: tumblr_oding8NHYX1ur4mpqo6_1280.png]

I haven't changed anything in my settings in Dolphin prior to this happening. I was using Dolphin version 4.0-8973 x64 and tried a later version, 5.0-632 x64, but the issue persisted. I then tried changing the graphics backend to OpenGL and it went away. Swapping back to Direct3D 11 made the issue return.

I have another version of Dolphin, Dolphin Dc netplay 4.0-652 x64? Something like that. And It looks fine on the direct3d backend. But noting, it just says Direct3D. not Direct3D 11.

I checked which version of DirectX I have and I have 11.
I'v tried updating my graphics drivers after this, and I also did some windows updates but it hasen't changed anything.


I'm wondering if anyone else is having this issue? Or what I can do to fix it. Because Direct3D 11 backend runs much better than OpenGL so I'd much rather be using that.

My specs should be on my profile, but I feel the relevant ones would be to mention I have Windows 7 x64 and my graphics are AMD Radeon R7 200 series.

Edit: Apologies my image is so huge. Also I should mention this isn't happening in any games through steam. Just Dolphin.
Does this happen in 5.0 stable?
Is there any chance this started when you updated your amd gpu driver? I was having an issue in new super mario bros after updating to 16.7.3. Updating to 16.9.1 did not fix it, but downgrading to 16.6.2 fixed it.

Could you test 4.0-5012 and 4.0-5016 please?
(09-19-2016, 04:52 AM)Helios Wrote: [ -> ]Does this happen in 5.0 stable?

Yes, Just tried 5.0 stable now and it's still there.
(09-19-2016, 05:00 AM)mimimi Wrote: [ -> ]Is there any chance this started when you updated your amd gpu driver? I was having an issue in new super mario bros after updating to 16.7.3. Updating to 16.9.1 did not fix it, but downgrading to 16.6.2 fixed it.

Could you test 4.0-5012 and 4.0-5016 please?

I can't entirely recall if I had played dolphin after updating to 16.7.3 or so. I have 16.9.1 now.
Just tested both of those versions and 4.0-5012 looks just fine but the glitch still happens in 4.0-5016.

I can try downgrading my driver to 16.6.2 and see if it goes away for me
(09-19-2016, 05:57 AM)ToxicCaves Wrote: [ -> ]I can't entirely recall if I had played dolphin after updating to 16.7.3 or so. I have 16.9.1 now.
Just tested both of those versions and 4.0-5012 looks just fine but the glitch still happens in 4.0-5016.

I can try downgrading my driver to 16.6.2 and see if it goes away for me

Thank you for confirming that this build "breaks" it. Can you report back here, if you decide to downgrade?
(09-19-2016, 06:30 AM)mimimi Wrote: [ -> ]Thank you for confirming that this build "breaks" it. Can you report back here, if you decide to downgrade?

I downgraded the graphics driver to 16.6.2 and there are no issues on any dolphin version! So its clear this comes from the later versions of AMD's driver updates. I would prefer to be able to keep my AMD drivers up to date though. Unsure what it could be in these later updates that cause the issues with directx in dolphin.
I posed this issue on the amd forums, but i doubt it will get any attention. What gpu do you have? Please don't say R7 260, because that should be about the same as my HD 7790, which might mean that only 3 out of 20 gpus might be affected by this bug.
(09-19-2016, 07:45 AM)mimimi Wrote: [ -> ]I posed this issue on the amd forums, but i doubt it will get any attention. What gpu do you have? Please don't say R7 260, because that should be about the same as my HD 7790, which might mean that only 3 out of 20 gpus might be affected by this bug.

I got R7 250.
I have an HD 7950, getting the same issue.
Pages: 1 2