Aller au contenu

Photo

For all those having graphic corruption, crashing and lag look here.


  • Veuillez vous connecter pour répondre
82 réponses à ce sujet

#1
Pract1t10ner

Pract1t10ner
  • Members
  • 37 messages
So from day 1 on dragon age i have had problems, graphic corruption, random and sometime very consistant crashes and game stopping lag (mainly in denerim and orzammar) i have tryed so many work arounds, tweaks and reinstalls but nothing worked, until i turned PhysX GPU acceleration off.

As soon as i turned PhysX off it was magical almost, and dragon age runs great now at full settings (not really saying much seeing as how theres only 3 settings)  and to further prove that this works, i was questing in the dead trenches in the deep roads and i was about half way through the area, i got to the this part with a bunch of skeletons and a genlock emissary attack me and every time DA crashed over and over again, in short i was stuck... i turned PhysX off and not only did i finish the dead trenches but for the rest of the night DA did not crash, lag or have corrupt graphics whatsoever .   :)


Intel Core 2 Duo 3.16 ghz
4 gigs of ram
2x Nvidia 8800 GT 512mb
Vista home premium 32B

Now im not saying that this will work for everyone but im hoping that this will help some, but i still need to further test it as i only played for another 2-3 hours after the fix.

Oh and i am running the latest Nvidia driver.

Modifié par Pract1t10ner, 13 novembre 2009 - 12:16 .


#2
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
can you tell me what happens when you re-enable PhysX and run from the 2nd core please?

#3
moose777

moose777
  • Members
  • 4 messages
how do you turn PhysX off?

#4
moose777

moose777
  • Members
  • 4 messages
wow!!! It worked. Thanks. I kept crashing when the guard talks to you across the bridge at ostagar.

#5
Pract1t10ner

Pract1t10ner
  • Members
  • 37 messages

JironGhrad wrote...

can you tell me what happens when you re-enable PhysX and run from the 2nd core please?



I have the same problem, graphic corruption and all.  Does that work for you?


and im glad it works for you Moose :D

#6
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
hmmm.... do you have an ATI or NVidia card moose? Thanks for the imput Pract1t0ner

#7
Pract1t10ner

Pract1t10ner
  • Members
  • 37 messages
Only Nvidia has PhysX, so i assume he has an Nvidia card, of course i might be wrong about that.

#8
Lifter82

Lifter82
  • Members
  • 65 messages
Works for me. Really good thought you had there. Finaly I can play for more than an hour straight without restarting my comp. Thanks a lot.

#9
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
There's a software mode that's installed with the game... but I suspect that trying to disable it on non-NVidia cards will tank the game... hence asking... did you try updating PhysX?



Go to Nvidia's site and install the latest Physx system software.

http://www.nvidia.co..._9.09.0814.html


#10
maelstrome

maelstrome
  • Members
  • 40 messages
for my 8600m under win7 i had a seperate control widget called nvidia physx[32bit] and had to go in there to disable it.

#11
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
if you'd be willing Pract1t0ner, could you update the PhysX and re-enable and see what happens?

#12
Mythos Engineer

Mythos Engineer
  • Members
  • 28 messages
So I took some advice from here & turned off auto saving & set my affinity to one core instead of two. The game is a wee bit more sluggish, just a tiny, but my load times are no more than 10 seconds at most now. It's an incredible difference. Before I had some 8-10 minute load times. Crazy! Sadly, any time I play fullscreen I start to get graphical tears & glictches which are solved only by a restart, however if I play in windowed mode it's fine. So I have it on windowed mode, the size of my screen. Basiclly fullscreen but not.

#13
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
Mythos what processor do you have? also did you try turning on V-Sync?

#14
Mythos Engineer

Mythos Engineer
  • Members
  • 28 messages
I have an AMD Athlon 64 C2 duel core 6000+, my gfx card is an 8800GT Nvidia & I did try with V-Sync, but that lowered my FPS quite a lot (& there were still graphical bleeds)

#15
Mythos Engineer

Mythos Engineer
  • Members
  • 28 messages
C2=X2 (Sorry for double post, didn't notice Edit button)

Modifié par Mythos Engineer, 13 novembre 2009 - 01:56 .


#16
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
hmmm... good to know about the X2... what drivers are you using on your 8800?

#17
Mythos Engineer

Mythos Engineer
  • Members
  • 28 messages
I am using 191.07 which is their latest (according to the site). I did try going back one, then two, but it made no difference so I returned to their current.

#18
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
you might try the Beta 195.xx's... there have been some success with those

#19
Mythos Engineer

Mythos Engineer
  • Members
  • 28 messages
Hmm where could I find that one? I don't know of anywhere to get drivers except the actual website

#20
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
they're on the NVidia site I believe...

http://www.nvidia.co...aspx?lang=en-us try that link, and if it doesn't work properly use the NVidia search and type "beta drivers"

Modifié par JironGhrad, 13 novembre 2009 - 02:12 .


#21
Groumph099

Groumph099
  • Members
  • 46 messages

Mythos Engineer wrote...

Hmm where could I find that one? I don't know of anywhere to get drivers except the actual website


Change the bottom right combobox to beta.

http://www.nvidia.co...aspx?lang=en-us

#22
Mythos Engineer

Mythos Engineer
  • Members
  • 28 messages
Thanks a lot, I'll give these a go & report back after supper :)

#23
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
good luck

#24
andysdead

andysdead
  • Members
  • 459 messages
trying this now. hopefully at least half of my problems are solved!

#25
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
I'd like someone with the original problem to try updating physX if they could to allow us to better troubleshoot the problem (since all turning it off on an NVidia card does is move the load to the CPU)