Aller au contenu

Photo

Error initializing PhysX


260 réponses à ce sujet

#201
SteveGarbage

SteveGarbage
  • Members
  • 813 messages
Well, I forgot to post but my brother was indeed sick this weekend, so I won't be reclaiming my old junky computer until this coming weekend. Suspense!

#202
SteveGarbage

SteveGarbage
  • Members
  • 813 messages
Well, perhaps this will shine some light on the situation from the PC Support thread:

xMotorx wrote...

If you look at the physx dll files in the dragon age 2 folder you will see that the game is using physx version 2.8.4.4. Quick google search shows that PhysX SDK 2.8.4.4 is compiled with SSE2 and the Athlon XP does not support sse2.


So, judging by that, it would appear the problem is in the PhysX version itself and perhaps nothing that BioWare has control over, which would be EXCEPTIONALLY unfortunate. I suppose that would mean we'd have to try to get Nvidia to release a PhysX patch or fix for non-SSE2 systems.

#203
kazeva

kazeva
  • Members
  • 53 messages
Some kind of patch is coming "soon" http://social.biowar...6826179#6833781

#204
SteveGarbage

SteveGarbage
  • Members
  • 813 messages

kazeva wrote...

Some kind of patch is coming "soon" http://social.biowar...6826179#6833781


We can certainly hope it will fix it. Although in my experience, "soon" can mean anywhere from a week to three months, heh.

#205
VelvetV

VelvetV
  • Members
  • 263 messages

SteveGarbage wrote...

So, judging by that, it would appear the problem is in the PhysX version itself and perhaps nothing that BioWare has control over, which would be EXCEPTIONALLY unfortunate. I suppose that would mean we'd have to try to get Nvidia to release a PhysX patch or fix for non-SSE2 systems.

If that's the case, then the solution to the problem is to ask Bioware to recompile their files with the slightly older version of PhysX.

Somebody posted a link to Dogfighter with the same problem that got fixed by developers, I'll find it now. Yes, here it is from wiki http://en.wikipedia....010_video_game):

Version 1.0.2.6 added:
Legacy nVidia PhysX support (2.8.3 SDK) for non-SSE2 systems.

Somehow they could add support for older PhysX version for non-SSE2 systems, although the game was originally compiled with a higher versin of PhysX, as the previous update version says:

Version 1.0.2.5 added:
Updated to Steam SDK 1.11 and nVidia PhysX SDK 2.8.4.4

So it should be possible to do the same in DA2 case, if the problem is indeed only the compiler version.

P.S. Then again, getting nVidia to stop using sse2 instructions for compiling their tools would be perfect for any future games (I take it that all games that use PhysX from now on will stop running for us), but I don't really know how to start asking them about it, I admit. :?

Modifié par VelvetV, 30 mars 2011 - 02:14 .


#206
Elricelf

Elricelf
  • Members
  • 2 messages
I had the same problem - error initializing PhysX.. copying "physxloader.dll" and "physxcore.dll" to sysWOW64 folder solved it. Hope it would help u too ;)

#207
hANGhOHN

hANGhOHN
  • Members
  • 9 messages
in which folder you copied the two .dll? sysWOW64 folder? where it is? i have XP32bit system?

#208
kazeva

kazeva
  • Members
  • 53 messages
Abou full game.Just remembered that MOH:Airborne didnt install if win firewall wasnt enabled.You had to enable it,install game and then disable it.Also you had to install physx version what came with it and after that install newer version.Demo same.

Activision and Quantum of Solace got ie problem.(tried demo,needs sse2)
"Several users have reported that the PC version of the game will not run on Windows XP if Internet Explorer 8 or an updated version of Internet Explorer 7 is installed on the system.[40][41][42]
This essentially makes the game unplayable for users who keep their
Windows systems up to date. The issue seems to be fixed if the user
reverts the system to Internet Explorer 7 prior to the June 2009
Security Update,[43]
by uninstalling all IE7 Security Updates issued since then, but this
has the obvious repercussion of leaving the system insecure. As of May
2010, Activision has not released a patch addressing this issue, and
there is no page on Activision's customer support database acknowledging
it."
en.wikipedia.org/wiki/Quantum_of_Solace_%28video_game%29

#209
kazeva

kazeva
  • Members
  • 53 messages
More about patch http://social.biowar...-6888490-1.html

#210
SteveGarbage

SteveGarbage
  • Members
  • 813 messages
Well, I've finally got my computer back so I'll be trying a couple new things when I get it home tomorrow. I'll also keep my eyes out for the patch release and then see if that helps too.

#211
Elricelf

Elricelf
  • Members
  • 2 messages
2 hANGhOHN
in 32-bit XP its "windows\\system32" folder.

#212
hANGhOHN

hANGhOHN
  • Members
  • 9 messages
@ Elricelf - Didnt work!, but thanks. greetz hANGhOHN

#213
SteveGarbage

SteveGarbage
  • Members
  • 813 messages
Well, today I used Resource Hacker to peek into the DA2 executable. In there, it has an assembly regarding the processor type, which it correctly has that my PC is a x87 (32-bit processor). To me, it would make sense that if the game can auto-detect that I'm running a 32-bit system why it would have a component that likely utilizes a feature only available on 64-bit machines. You would think that it should have a switch like 32-bit detected and utilize a "legacy" software package, but I guess not.

The more I fruitlessly mess with this problem, the more I'm absolutely convinced that it is a conflict in the PhysX 2.8.4 package which utilizes the SSE2 instructions. I was messing with decompilers and stuff but came to the realization that any effort at patching it myself is way above my head. It would require someone with some significant programming experience and an understanding of how the game is built. I can look at the decompiled code all day but I have no idea what I'm staring at. If only it were as simple as like a .ini file where everything is spelled out for you.

I suppose I'll keep my fingers crossed that this next patch will resolve it, because I've about exhausted my options.

#214
VelvetV

VelvetV
  • Members
  • 263 messages
Would you please write about this theory of yours in the launch bugs thread or somewhere else (unless you already have). I'm also keeping my fingers crossed for the next patch!

#215
hANGhOHN

hANGhOHN
  • Members
  • 9 messages
no patch?
no update?
nothing???
...thats realy hard... :-(((

#216
Rifster

Rifster
  • Members
  • 23 messages
I think we are doomed :crying:
Patch release today, hope it will work...

Modifié par Rifster, 12 avril 2011 - 10:11 .


#217
kazeva

kazeva
  • Members
  • 53 messages
Doomed hah hah hah.Hope not.
I believe they fixed this.

There www.kvraudio.com/forum/viewtopic.php is quite simple explained sse2 usage.

"the main reason for using SSE2 instead of SSE is that SSE2 brings 64-bit
floating point capabilities and all our plug-ins do require that as
they internally process the audio content with 64-bit precision."

"but 64-bit precision does not necessarily require SSE-2. It is just faster."

Modifié par kazeva, 12 avril 2011 - 12:41 .


#218
Rifster

Rifster
  • Members
  • 23 messages
If it so easy, why they don't fix it early in first patch or in the demo?
lost hope, just wait ... :)

#219
kazeva

kazeva
  • Members
  • 53 messages
It propably aint so easy after game is coded to use it but for bigger companies its easier depending how much there is sse2 code.And after playing this on low settings,it should run Athlon XP's.

Modifié par kazeva, 12 avril 2011 - 03:45 .


#220
Rifster

Rifster
  • Members
  • 23 messages
Patch live, wait Steve :)

#221
SteveGarbage

SteveGarbage
  • Members
  • 813 messages
I'll check it out when I get home in an hour and a half and report back!

#222
SteveGarbage

SteveGarbage
  • Members
  • 813 messages
And the results are in! Still NO LUCK. Same damnable error.

Also I discovered that the Catalyst 11.3 AGP Hotfix drivers also like to crash my computer for no apparent reason, so I'm still stuck operating on the lowly 10.6 package which seems to be about the only driver package that will not crash during install or crash repeatedly during Windows boot.

The day I can afford to throw this !#%*^!#%^ computer out and finally play DA2 again is going to be something of a celebration

#223
kazeva

kazeva
  • Members
  • 53 messages
****.Game is a product.As any product.And in my mind you have to get answer if you are asking is it working.SO BIOWARE IS IT GONNA WORK ON ATHLON XP'S meaning in english:Does it require sse2?Simple question where answer is YES or NO.
To be more specific i have my rights to know some things BEFORE i buy something.

Steve Garbage-Try install those drivers in built-in account.

Modifié par kazeva, 12 avril 2011 - 11:57 .


#224
SteveGarbage

SteveGarbage
  • Members
  • 813 messages
I'm convinced the video driver issue is a lost cause.

Anyhow, after I got a bit moody in the 1.03 patch thread, the PhysX issue has been added to the official list in the OP of things to look at. I included a bit more information and even offered a suggestion on how to solve the problem (if the game recognizes the processor as 32-bit, to default to using an older 2.8.3 PhysX build).

Hopefully that will take root. For now, it appears its more waiting.

#225
kazeva

kazeva
  • Members
  • 53 messages
Yep.But if you want hassle with those.Finally updated 10.10 to 11.2 and physx 9.10.0513 that way(sapphire drivers).It gives bsod sometimes but seems work better than 10.10 and when installed in normal account.
I'm pretty sure bioware/ea knows that we are talking here non sse2 processors so i've been wondering why they just dont give announcement about it.And thats the main reason why i still think that theres coming possible fix.
Unless they really arent realize that or they just collect information about game problems and dont tell nothing to us.

And yeah "the PhysX issue has been added to the official list in the OP" they have to know it.

Did you try that Dogfighter demo?Theres iePhysXLegacy.dll in iePhysXLegacy folder which propably handle physx to 2.8.3 and game works pretty good.But that ie is added to quite many .dll's so maybe it required more code to those also.Dont know.

Or
9.10.0513
"Supports NVIDIA PhysX acceleration on GeForce via CUDA 3.0 for SDK
versions 2.7.1, 2.7.3, 2.7.4, 2.7.5, 2.7.6, 2.8.0, 2.8.1 and
2.8.3 (requires graphics driver v196.21 or later)."
Is it possible that 2.8.4.4 can use (or game exe) older installed version?That would explain why they told to update physx driver ( for nvidia users also).Just thinking cause debug stopped after cuda and thats why i write earlier that "If it is trying to use GPU PhysX."

Modifié par kazeva, 14 avril 2011 - 12:56 .