DirectX11 Problems

[Tami]

So a few months back whenever I started up a game in DirectX11 or 10 it looked seriously messed up and you couldn't even tell what was going on, whereas DirectX9 works perfectly fine and plays perfectly fine. It's never bothered me too much since I could just swap most games down to DirectX9 and play just fine. I noticed this when I tried to play Metro 2033 in DirectX11 after giving up on Watch_Dogs, it's been like it ever since. I'm interested in Middle Earth: Shadow of Mordor but it's DirectX11 only and whenever I try to start a game in DirectX11 it just looks really off. I'm too lazy to boot fraps up and don't know if it'll catch it with fraps but here, poorly recorded example with Metro Last Light.

[youtube]mPkgyMAQHGY[/youtube]

 

[Tami]

Started it up with fraps and it wasn't nearly as bad as it was and usually is, but it's still got issues. Main menu and gameplay below. Recorded in 1366x768 and reduced to 720p for youtube so it might not be the best quality, but it shows what's wrong.

[youtube]crr00e1YdSw[/youtube]

 

[Helios]

did you try updating video drivers for ati/nvidia card you have
usually those cause problems with directx

 

[Tami]

I've got the latest driver atm

 

[posepsi]

tried uninstalling the drivers and reinstalling them?

how are the temperatures?

what card is it?

 

[Tami]

Fixed! Helios suggested over Steam that it could be a problem that could be resolved by getting the beta for my driver. Apparently somewhere along the line AMD cards got issues with tessellation if you had a 60hz monitor, which I have. AMD's latest beta driver resolved the issue.

Thanks+locked

 

[Tami]

Maybe not+unlocked

Metro: Last Light works just fine in DirectX11 now, for what little I played of it to test it out. Tomb Raider on the other hand, definitely does not. Same issue, though worse. This is about how it used to be with Metro as well, except most of the time I couldn't make out any distinguishable shapes through the mess.

[youtube]o8wfU1LT4DY[/youtube]

@Pepsi

N/A for the first one now, I suppose.
My laptop's overheated a lot in the past though lately (since I started playing Dark Souls II) I've been keeping it propped up on two books so there's more space between the desk and the laptop, since the fans are on the bottom. It hasn't overheated since.
Don't know the exact card off the top of my head and cba to check unless it's vital to a solution. I've had my laptop for about two years though, I think.

e;

Metro's gone back to it's old ways as well. Super quick before of Metro working just fine this morning in DX11, then now in DX11. For some reason the Fraps footage is actually more clear than what I saw on my screen, which makes no sense at all.

[youtube]E28zcoqYO18[/youtube]

 

[posepsi]

knowing what card you have is pretty vital to trying to diagnose the issue, i'd say

 

[Tami]

AMD Radeon HD 7400M Series (0x6760) and AMD Radeon HD 6620G (0x9641), AMD Crossfire enabled.

 

[K33f3!]

FUCKING CROSSFIRE.

 

[JC Heavy]

5:23 PM - JC Heavy: Tami, you have a normal card and an APU, right
5:24 PM - JC Heavy: That's what you crossfire with right
5:25 PM - fire of your loins: yes
5:24 PM - JC Heavy: You might want to add that into the forum post

-snip after convo with Keefe on Crossfire-

 

[Tami]

I can't play Shadow of Mordor/Alien Isolation/The Evil Within/Daylight until I get my DX11 fixed and the internet has no answers for once.

 

[JC Heavy]

I figure I'd drop this as well, both of Tami's cards support DX11. I checked.

 

[Tami]

But for some reason AMD Radeon Dual Graphics seems to be the reason DirectX screws up? I gave it a bit of thought and disabled it in CCC. Opened up Metro: Last Light, worked perfectly fine. Played around with that fine. Metro: Last Light works with and without it on or off, though I suppose sometimes with it off it screws up. Tomb Raider, on the other hand... I started up Tomb Raider without AMD Radeon Dual Graphics and running the lowest settings, worked just fine. Bumped the settings up to the highest (spare anti-aliasing and tressfx, which kills my system) and it worked perfectly fine. I started it up with AMD Radeon Dual Graphics enabled however, and it had the same issue as before. On disabling it again, the game worked. So I'm going to go ahead and assume I can actually play DirectX11 games now as long as I'm not using that feature, but that nicks precious framerate when I don't use it, so that's conflicting and the problem isn't really solved.

Does anyone happen to know why DirectX11 would work without it enabled only, and not work most of the time with it enabled? Both cards are DX11 compatible, why would it do this?

e; As a side note, I did actually play Watch_Dogs with it disabled because Watch_Dogs was supposedly not in favor of things like Crossfire and SLI at launch.