1 réponse à ce sujet

[DeltaBravo1]

After reading an old ME1 post regarding the openAL drivers (which have caused me a few problems in the past) i decided to search for the openAL package on the old internet (http://connect.creat...s/AllItems.aspx) where it says oalinst it gives 2 versions
* OpenAL32.dll version 6.14.357.24
    * wrap_oal.dll version 2.2.0.5

i checked the openal32.dll version in my ME2/Binaries folder and noticed the openal32.dll was an old dll file 6.14.357.22 or something loike that, so i downloaded and installed oalinst, went to my windows/system32 folder and copied the 2 files above into my me2/binaries folder I also copied Physxextentions.dll from the system32 folder as well.

    I am running vista ultimate x86
Nvidia 9800GT
am2 4600+ dual core

before i did this i could not starrt the game without task manager and setting affinity to cpu 0 only and even then it would crash after so long. Now I can start the game without having to do this at all. I hope it helps some of you.  also download the Coalesced.ini editor from one of the posts and work on tweaks like FALSE for Force vsync etc. 
  to me this problem seems like its changing the refresh rate part way through and stopping me from doing something and I couldnt get an error from windows event log and I dont have the tools to debug my ME2 .dmp file.

sorry if this is useless to some of you i guess it is worth a try

[DeltaBravo1]

I found this in a different forum, and im going to try to use the physx files from a different EA game that ran for me, at least I have ME2 starting up for me now but we'll see, I'd rather use both of my cores and dont really want a refund







[PhysX-slowdowns] Found CAUSE, found TRIGGER, found SOLUTION! >PROBLEM STILL EXISTS<



--------------------------------------------------------------------------------



Yesterday and today I tested for hours to find out what was causing the PhysX-slowdowns on my system, which consists of the following components:



Core2Quad Q9550

Geforce GTX 260 with 216 shader cores

2x2GB DDR2-666 memory

Windows Vista Business 64bit SP1



First: I keep my drivers up to date, I keep my system clean and my harddiscs defraged, or in short, my system never crashes and is 100% stable.





PART 1: THE CAUSE



Fact: IF you experience PhysX-slowdowns than this is not a bug of the game, but your PhysX-software/driver not functioning properly which results in the CPU processing the PhysX-effects which in effect results in bad frames per second (fps) in the game.



So the cause of the slowdowns is that your PhysX-systemsoftware doesn't work.



But how can this happen? Off to...





PART 2: THE TRIGGER



I tried multiple things trying to trigger the PhysX-software to malfunction, first here are a few things that DON'T trigger it:



- multiple PC restarts

- multiple PC shutdowns and restarts

- multiple restarts of Mirrors Edge



...do NOT trigger the software to malfunction



THE TRIGGER IS: Another Unreal Engine 3 based game. Yes you read correctly!



In my case it is Mass Effect, another EA game (although it has been developed by Bioware "A division of EA"). When I started this game, played for a few minutes, then exited again and started Mirrors Edge the PhysX-slowdowns where back again.



Both games use the files "PhysXCore.dll", "PhysXLoader.dll" and "NxCooking.dll" to provide the game with PhysX-support, but I noticed that both games use different versions of these files. So that's the problem, maybe loading an older version (in Mass Effect) somehow messes with the PhysX-software.



Disabling the PhysX-hardware support in the Mass Effect config files proved uneffective, the problem still exists.



How to solve this problem? Off to...





PART 3: THE SOLUTION (or let's say a workaround)



I tried different things to solve the problem. First a list of things that DO NOT solve the problem:



- a restart of the PC

- a shutdown and restart of the PC

- disabling and enabling PhysX in Mirrors Edge

- disabling and enabling PhysX in the driver



...DO NOT solve the problem.



THE SOLUTION IS: A reinstallation of the PhysX-system software!



You don't even have to restart the PC. Simply uninstall the PhysX-software and reinstall it.



After I do that and start Mirrors Edge again the PhysX-slowdowns are gone...until I start Mass Effect again, which wrecks the PhysX-software again.



I confirmed all this in multiple tests, it's true.





PART 4: CONCLUSION



What should I say? An EA game wrecks another EA game. Has anybody ever heard of such a stupid thing?



We need a fix, either from EA, or from Nvidia. I want to play both games and I don't want to reinstall the PhysX-software over and over again (I even placed the installer on my desktop, omg ).





I hope this helps the people who suffer from PhysX-slowdowns.



[Latest tests, as of May the 4th 2009]



Recent tests revealed that this problem still exists. Now, with a fresh installation of Windows Vista 64bit and the latest graphic driver, Mirrors Edge still shows bad performance with PhysX enabled when another PhysX supported game had been started before. In my case it is Mass Effect.



I really wonder if EA is going to fix it, but I bet they wont. They had their share of money from the sales, case closed.