It just seems to me like dx11 has not been as qa tested as it could for whatever reason. ![]() However, civ 5 dx11 works fine, and some of the crysis dx11 stuff hasn't worked so well. I do the core affinity thing but it pisses me off. I personally don't think much of hyper threading (especially for games which have more real time demands than, say, a 3D or non linear video rendering app which is what HT is really made said: Either I have to run Dirt 3 on only 4 of the 8 logical cores or turn off DX11 for it to run without crashing after a few races. Try the latest drivers (including the new betas) and disabling Hyper Threading. Possibly, maybe even likely, it's actually an older driver causing the issue, or it could even be Hyper Threading (I'm guessing this due to your demonstrated logical core count being over 4). Yeah well Nvidia have been making noise about their thread aware driver support for shader performance enhancement (it's been a thing since the release of the beta Civ5 driver) so it could be related. That says to me that while potentially the issue is a core issue, DX11 is related because turning on/off dx11 features causes the crash. When I turn on dx11 I have to manually set core affinity. Also, yes I agree it's a compiler issue- however, in the specific example I have if I run the game in dx9 mode it never crashes. Anyways- my point is more so that it seems like DX11 is complex in such a way that developer QA isn't work as well as it said: Nvidia user- which baffles me more because Nvidia provides such good support. It also baffled me that so many people consistently had nvdia 500 level GPU's and i5-i7 sandybridge processors (or the i7 extremes hexacores), and yet for some reason codemasters couldn't work out the pattern (>4 logical cores and the latest Nvidia boards), and work out a way to test this. Anyways, I don't have highly specialized parts, and it baffles me that a games developer can't reproduce the issues I was having. Almost the exact config that the tested crew built +/- a couple components. This was strange because at least for me, I'm running i7 2600K, gtx570 and 8 gb of ram. ![]() My issue with Dirt3 was that people worked out a 'fix' to get around crashing issues, and codemasters couldn't reproduce the crash on their pcs. Edit: I really should say that it seems individual developers have not been as thorough as they could be. Either I have to run Dirt 3 on only 4 of the 8 logical cores or turn off DX11 for it to run without crashing after a few races.
0 Comments
Leave a Reply. |