Jump to content

Recommended Posts

  • 2 weeks later...
Posted (edited)

Update your graphics card driver

In the DirectX log file it says your GPU driver has no WHQL (windows hardware quality) certificate

Install the latest drivers from AMD's official website

And all the other errors in DCS' log file and the dump file also indicate a driver issue to me

Also found this:

Screenshot_1.png

Dont know if thats normal or not, but if you have modified any game files, open steam and verify the files' integrity

last thing, I saw you had SSAA turned on, turn it off, if you want antialiasing use MSAA

Edited by peanuts0441
Posted (edited)

Thanks for replying. It sure would be nice if AMD notified users when there's an update, but I've now updated my drivers, and I'm not using Steam. I switched to MSAA, having found the notice in the MT bugs section about turning off SSAA. I also ran DCS repair. Anyway, long story short, it's not Viggen-induced, after all, because I just had 3 CTDs with the Apache this morning.

Edited by WWSmith
Posted

I seem to have fixed the Viggen CTDs by removing all mods (I hadn't installed anything new recently, but maybe something old doesn't play nice with MT--I'll have to try to narrow that down), and running a full repair. The Apache CTD I mentioned earlier is connected to a specific instant action mission.

Posted

Yea it is possible if you had an old mod that wasnt updated, some incompatibilty arises with newer versions of the game

(For my own knowledge), once you figure out the cause, can u post it here pls

Posted (edited)

I seemingly fixed the Viggen by removing the A-4 mod, successfully flying 2 sorties which had previously ended in CTDs, and then decided to try the Hornet, since I hadn't flown it in quite a while and wanted to see if it had any issues. The result was constant CTDs, all with logs showing DXGI_ERROR_DEVICE_REMOVED. A few hours later, I had seemingly fixed this, which I think I inadvertently caused by reinstalling my graphics driver while troubleshooting the Viggen issue. AMD's software likes to be meddlesome, and some settings which I'd probably turned off ages ago were re-enabled. The Hornet worked for a little while, then CTD'd again. After more digging on the forum, I found a thread about this exact issue:

So, long story short, it's not any specific module, and supposedly it's being fixed in the next update. In any case, DCS currently seems a lot more stable in single-thread, so that's what I'm sticking with for now.

Edited by WWSmith
New Info
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...