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

#26
Pract1t10ner

Pract1t10ner
  • Members
  • 37 messages

JironGhrad wrote...

if you'd be willing Pract1t0ner, could you update the PhysX and re-enable and see what happens?


Jiron, i actually had the latest PhysX driver and for me it didnt help, but turning it off completely did... sorry man :(

Im atleast glad that this helps some people play the game.  What we really need is for Bioware to patch this game up, it has nothing to do with our graphics card (or overheating) or the drivers, its the game itself and Bioware needs to optimize DA...

But lets not stop here, obviously this dosnt and wont work for everyone so lets keep this bug fixing ball rolling eh.

#27
gurthang orcus

gurthang orcus
  • Members
  • 2 messages
Hmm, that's interesting. Trying uninstalling PhysicX (I run a 3870) and now Dragon Age won't load. Why should a game that's ATI compatible be reliant on "PhysicXLoader.dll"

#28
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
well be aware you didn't "turn it off" exactly... it's just been transferred to the CPU for proccessing. The game will not run without PhysX at all (there's a guy who tried it and tanked the game)

#29
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
The reason for the PhysX engine is that NVidia bought the technology a couple years ago... but this game has been in development a lot longer than that. You used to (not sure about now) be able to buy stand alone PhysX processors

#30
gurthang orcus

gurthang orcus
  • Members
  • 2 messages
Updating PhysX does not help with issues with the 3870 crash's, at least for me. Uninstalled, game wouldn't load, updated PhysX, game still crashed. I'm currently caught in try to clear the Tower of Ishal.

#31
seek333

seek333
  • Members
  • 1 messages
I just reloaded PhysX and DA is no longer crashing. My graphic card is a 4670. Thank you for the fix.

#32
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
what are your precise specs gurthang?

#33
kalgorath

kalgorath
  • Members
  • 10 messages
Does anyone have random BSODs with a Quad Core processor? My specs are:

Processor: Quad Core Q9450 @2.66 Ghz
RAM: 4 GB Corsair DDR2
Graphics: GTX 280
Sound: Creative Xfi

I'm running it on Windows XP SP3. Drivers are all latest. I've tried running on just 2 processors, re-installing Physx, setting the sound acceleration to Basic( as recommended by EA tech support) and I'm still getting BSODs, most of the time in the midst of a conversation.

#34
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
does the blue screen give an error message?

#35
Graunt

Graunt
  • Members
  • 1 444 messages
I'm not having crash issues, but I'm getting that really annoying "white dot speckle" effect on any textures that have grass or lots of green on them. It looks almost like what you would see when a card overheats I guess, but mine doesn't get above 65c (5850).

#36
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
@ Graunt you have a driver issue (unsurprising given the relative newness of both the GPU and the game) ATI will probably have that one cleared up in the next updated driver set

#37
kalgorath

kalgorath
  • Members
  • 10 messages
JironGhrad, the BSODs are random. Sometimes it's the IRQ_not less or equal error, sometimes it's the graphics card driver error (nv4_dll something) and sometimes it's a page file error.

#38
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
have you tried updating to the Beta Drivers, kalgorath?

#39
kalgorath

kalgorath
  • Members
  • 10 messages
Beta drivers for? The graphics card?

#40
JironGhrad

JironGhrad
  • Members
  • 1 657 messages

kalgorath wrote...

Beta drivers for? The graphics card?


correct

#41
kalgorath

kalgorath
  • Members
  • 10 messages
Ok, tried that. No dice. Still gives me a BSOD for the graphics card driver. Sigh....

#42
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
hmmm.... there's a link to microsoft update here



try opening the link and install whatever it might ask for and then when the window loads pick "custom" rather than "express"... install all the optional and hardware updates along with any high priority ones

#43
harrier25699

harrier25699
  • Members
  • 401 messages
I have disabled physx within nvidia control panel but unfortunately this has not helped.

I can barely play the game for 5 minutes before I get major gfx/texture corruption.  You might see something similar if your gfx card was overheating, however mine is running nice and cool.  This is extremely frustrating. 

I have updated to 191.07 (8800 GT) nvidia drivers and no improvement.  Here is a ss of my problem ingame as it occured at the looting screen:

 Image IPB

I am running the game at recommended gfx settings + x2 AA, which I have also disabled/re-enabled while problem solving.  

resolution: 1920 x 1200 (16:10)
gfx detail: High
AA: x2 or off
texture detail: high
framebuffer effects: on
v-sync: off

*edit*  I should also mention that i have patched the game to 1.01a and that in doing so I could no longer launch the game :pinched:.  I found the vcredist fix and I can now launch the game again but of course the gfx problem remains.

Modifié par harrier25699, 13 novembre 2009 - 07:41 .


#44
JironGhrad

JironGhrad
  • Members
  • 1 657 messages
you might want to try the BETA drivers harrier... and you may want to try updating to the latest physX version



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

#45
kalgorath

kalgorath
  • Members
  • 10 messages
Installing the MS VC++ 2005 in the link seemed to have worked. Fingers crossed. Thanks very much JironGhrad!

#46
JironGhrad

JironGhrad
  • Members
  • 1 657 messages

kalgorath wrote...

Installing the MS VC++ 2005 in the link seemed to have worked. Fingers crossed. Thanks very much JironGhrad!


yay! another one on Jiron's bedpost...errr... bug post...

#47
harrier25699

harrier25699
  • Members
  • 401 messages

JironGhrad wrote...

you might want to try the BETA drivers harrier... and you may want to try updating to the latest physX version

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


I have done as you suggested and it seems to have worked.  I do get the occasional stutter where the game locks up and the sound chugs but DA does resume and without gfx corruption so thanks for you help.  Hopefully Bioware are busy trying to nail this problem properly.

#48
JironGhrad

JironGhrad
  • Members
  • 1 657 messages

harrier25699 wrote...

JironGhrad wrote...

you might want to try the BETA drivers harrier... and you may want to try updating to the latest physX version

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


I have done as you suggested and it seems to have worked.  I do get the occasional stutter where the game locks up and the sound chugs but DA does resume and without gfx corruption so thanks for you help.  Hopefully Bioware are busy trying to nail this problem properly.


that could be a side-effect of Beta drivers too... you might try updating your sound drivers though and see if that helps

#49
Brygard2009

Brygard2009
  • Members
  • 132 messages

Mythos Engineer wrote...

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)


You need to enble the triple buffering to ("On") in your nvidia panel when you use vsync on,this a must this will prevent fps drop to half of your refresh rate which you just experienced.

See pic for example:
Image IPB

#50
JironGhrad

JironGhrad
  • Members
  • 1 657 messages

xiper wrote...

Mythos Engineer wrote...

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)


You need to enble the triple buffering to ("On") in your nvidia panel when you use vsync on,this a must this will prevent fps drop to half of your refresh rate which you just experienced.

See pic for example:
Image IPB


excellent point... you can force it in game too through editting the .ini file and the same for forcing AF