44 réponses à ce sujet

[Reiz]

@Gorath : My VGA is HD4830 if you want to know ,though.

[Gorath Alpha]

The PCs in the family room here have Geforce cards, but my place was built before central air systems were common around here, and the winters are mild enough that central heating was only featured in the "upscale" homes at the time.  The western end of the house gets uncomfortably warm, and the room air conditioner in that wall seems very inefficint, just gobbling down juice, so I only run it when I have several guests over at the same time, and need the bigger room. 

Add the exhaust from a couple of game PCs in there, and no one would want to be in there after about noon, and from then until the next early morning.  There's an 8800 GT, and a 9800 GT, but I haven't had the second one long enough to do much at all with it.  In my bedroom, I have a PC with an HD 4850, and in here (spare bedroom used since 1995 as the "computer room"), I have an HD 3870.  

I've had some trouble with Dragon Age on the HD 3870, nothing too severe, and none at all with the HD 4850.  The Geforce 8800 was problematic in DA at first, but I have some very elderly video drivers now, and it has settled down.

Gorath
-

[Saerwen]

We fixed the issue with the Holy Smite, by updating video drivers. Hasn't crashed since.



Windows 7 64bit

4gb ram

ATI Radeon 5870

[DeadJediJamie]

Saerwen wrote...

We fixed the issue with the Holy Smite, by updating video drivers. Hasn't crashed since.

Windows 7 64bit
4gb ram
ATI Radeon 5870

I'm pretty sure this is not what fixed your game since updated drivers have done nothing and I'm running the same card you have. Unless it fixed your Holy Smite only, have you tried casting mana clash?

[Herdster]

I have just updated to 1.4, and holy smite almost always results in a blue screen of death



Win 7 64

AMD Phenom 3

2 GB RAM

ATI Radeon HD5870

[Xandax]

1.04 and still problems with Holy Smite for me as well. Crashes my game 80% of the time when using that.

[awpdevil]

Its not just holy smite, cleanse area, and mana clash. Any spell or effect that has an aoe look to it can cause it.

Fighting battles in the dungeon crawler view helps. Well it helps me at least.

I am running a 4850.

[JackM]

What version of Catalyst driver are you using? I have no issue like this with 10.7 and a 4850 under XP SP3.

Also, in CCC, set Anti-Aliasing and Anisotropic Filtering to Application controlled, Catalyst AI to Standard and disable Adaptive Anti-aliasing.

[awpdevil]

the latest. 10.7. I use that radeon pro program you mentioned in another post. The only thing I have set on it is the d3d vsync, triple buffering, aniso optimization, and force high priority. Everything else is either default settings or application controlled. The program helps the game run much better, but it never solved all of the problems.

I run on vista 64 though. Hence why you probably have no issues because XP was way better then I could ever say for vista for games, in my experiences.

Modifié par awpdevil, 15 août 2010 - 01:59 .

[JackM]

Do not use Trilinear and Anisotropic Optimization unless you really need to gain some frames/second. These options really lower the image quality. Concerning VSync, you not have to use RadeonPro to activate it; use in-game setting. The two reasons for which I use this program is to enable Anisotropic Filtering (no option in-game for this; with the low quality textures used in DA:O, I really think this is required) and, most important, to activate Direct3D Triple Buffering. Concerning the priority, I'm really not sure that this is a good idea.



Have you checked the CCC settings I mention in my previous post? Some, like Adaptive Anti-Aliasing, can only be correctly set in CCC, not in RadeonPro.

[Lyphen]

Nice to see that my AMD processor crashes the game when I use multi core.



And that my AMD graphics card crashes the game when I use Alistair.

[awpdevil]

Everything in CCC is either set to application controlled, or off. For the case of vsync, CCC has it set to off unless an application specifies.

Everything in radeon pro is the same aside from the ones I mentioned, but this problem existed before you even mentioned the program and even tried it, so playing around with it hasn't hampered anything that wasn't already lol. It just adds time before I have to restart.

Spells sometimes crash the game, it eventually slows down in loading, and graphic performance, and then I have to restart the game. I have had the issue since the game came out, none of the patches have done a thing to resolve it; and no, its not heat throttling the cpu/gpu/nb chip, unless something is stupidly causing them to anyway.. My video card never goes above 45c (stock hs was 60-70c), my processor never above 40c, and the nb, I have never seen above 40 either.

[lizzbee]

Pie-in-the-sky suggestion that actually worked for me: update your .NET framework to the current version, 4.0. I never CTD with anything spell-related anymore. Now my crashes are utterly random, or at least they were until the current patch destroyed things once fixed.

[awpdevil]

I've done everything I could possibly think of. I just recently reformatted even though I knew it was probably not gonna make a difference, and it didn't lol. I only have the OS, steam, dragon age, and all the drivers, and updates I need, including .net 4.

[Quels]

I'm quite sure this is a multicore problem - at least on my system - running on all three cores I can reproduce this fatal bug within seconds by just spamming the most sensitive spells, like Holy smite, mana clash, clense area etc.

All spells can cause CtD in this unstable mode but AoE spells seem to trigger the CtD almost every time. Actually I think all actions can cause the crash, like opening doors, chest etc. it's just not as frequent.

So when reproducing the bug just use aoe spells and spam them until CtD- makes it quite easy to track.

On my system Dragon Age Config only identifies core 1 out of core 0,1,2 (eventhough it registers my triplecore processer) and running on anything else than core 1 makes the game unstable.

It never crashes on core 1 - it's pretty stable on 2 cores but it's a matter of time before CtD, could be several hours in this mode though - running all 3 cores is more or less impossible.

[Alastriona]

Don't know if anyone is still having these problems. But I have them still. Running on 1 core seems to make things more stable for me though. This isn't really a good solution unfortunatly.

[DeadJediJamie]

Yeah, I am, though I've pretty much given up on DA: O for now. I'd recommend going back to the 1.02 patch if you don't care about DLC released after Return to Ostagar or the Awakening expansion.

[Phoenix_UK]

Happening about 80% of the time i use smite. Winding me up a bit now.

[Diablo King]

Upgrade to 1.4, then modify your graphics settings. AA specs shouldn't be over x2 if your system can't handle it. Sacrifice looks for performance when applicable.

And for Quels..

Quels wrote...

I'm quite sure this is a multicore problem -
at least on my system - running on all three cores I can reproduce this
fatal bug within seconds by just spamming the most sensitive spells,
like Holy smite, mana clash, clense area etc.

Try typing -singlecore on your game target line. It's in the properties of the game shortcut.

Modifié par Diablo King, 31 janvier 2011 - 05:20 .

[BounceDK]

1 year later .. Bug still exists and game is still crashing. Wonderful.