9 réponses à ce sujet

[MagicNakor42]

I only ever beat ME1 once because of the random black screens that would occur. It's a widely known issue (though perhaps specific to nVidia cards) and at the time the only "solution" was to use old drivers (174.74 or 175.19 if I recall). This wouldn't fix the problem but would allow for a reduced amount of these black screens.  I'd like to play through it once more before ME2 comes out, but am not sure if willing to endure that much frustration if the issue persists.

[Vairda]

I got the game on PC about a month, but haven't been able to play ti because of this issue and now with ME2 so close, I need to beat it a few times so I can have saved files to bring into ME2, unfortunately this same problem has plagued me for the lats two days. I have tried every odd balled fix I could find on forums, such as running it as admin, running in window mode, updated graphic and sound card drivers, re-installed it, I've done just about everything I can think of, but to no avail. I play for a random amount of time, then the screen goes black, my monitor sais its not receiving any signal, music and sounds continue in background, until I either do something or a minute passes by, then the sound starts to freak out, and I'm forced to do a power reboot( Pressing the power button for 10 sec) Please help!!!

[KBGeller]

Well, you cant expect help without specs and what you've tried already to fix the problem :-P

[MagicNakor42]

Since it's been a known issue for quite some time, I was curious as to whether or not it's been fixed. As for the steps I took to fix it myself (other than using outdated drivers)? I don't recall them other in the vaguest "following the forum stickies/submitting a tech support report via website" sense as this was two years ago. Using the older drivers was a user-supplied solution from the nVidia board; IIRC Bioware claimed it was a problem on nVidia's end and nVidia claimed it was the other way around. Speculation pointed to the newly-added PhysX as the issue, but last I heard there were still many problems with the 180 series and ME. There were also problems with audio and onboard sound cards (perhaps just RealTek) causing stuttering/crashing or simply blanking out. For me, that issue wasn't nearly as frequent so seemed minor in comparison.



OS: Windows XP

Processor: 3.4GHz Intel Pentium 4

Memory: 2 GB

Hard Drive: 31 GB free (gaming drive)

Sound Card: SoundMAX Integrated

Direct X: DirectX 9.0c August 2008

Video Card:nVidia GeForce 9400 GT (512 version)

[crapmonster13]

PhysX shouldn't be the problem, even if that was a possibility its easily disabled via nvidia's control panel and is so by default. Have you tried eliminating your sound as a possible reason?



http://www.gamespot....3947&pid=944902



Its worth trying, at the very least to eliminate it as a possible point of failure.

[MagicNakor42]

Yeah, I remember doing it. I'm sure it was even that exact same link...unfortunately it didn't work to solve the black screens.

[MagicNakor42]

Just a very shameless bump in case there is additional information out there.

[DeltaBravo1]

I posted something a few days ago for some extra info on black screen issue because i couldnt even start the game up without it crashing only way i could get it to start was to set the affinity to 1 core, I then read deeper into other EA games like NFS shift etc and they have all been plagued by black screen issues I'll copy my other post in here hang on

[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.

[DeltaBravo1]

sorry the copy messed up and left huge gaps between lines, forgive a british war cripple.... pretty pretty please only got 1 arm