Project Reality Forums

Alright, I've read the stickies, searched up and down google and still no solutions.

I've played PR for almost a year now, aside from small bugs and the occasional Lost Connection errors, there were no problems.

After fiddling around with my computer for bit recently (in an ill-fated attempt to get COD WaW working) like downgrading my graphics card driver which I eventually updated again.

When I gave up on that deal I tried to get back to PR, but the game started ctd left and right, while loading, 3 seconds after I press spawn etc..
So I decided to reinstall PR and see if that would solve my problems - It didn't.
Then I tried updating and tweaking Punkbuster as suggested by forums - didn't work.
Eventually I got so desperate that I reinstalled BF2 and PR together - Bad idea.

Now PR wouldn't even start anymore, I get that "PR.exe has encountered a problem and needs to close" error even tried in windowed mode and got the same message.
So I did some more checking up, uninstalled PR and BF2, cleared the registry, deleted all previous entries of BF2 files and folders, the tried reinstalling (again), no luck.

My system stats:
OS: XP Professional SP3
Intel Core2 Duo CPU E8400 @ 3.00 GHz
3.2GB RAM
Nvidia GeForce 9800 GTX/GTX+

Somebody help??? PLEASE!

I've also tried to install the older PR 0909 from the installation files I had retained, but 0909 also crashed.
BF2 vanilla works fine, I had it patched 1.41, then 1.5 and then installed PR

Did you remember to install BF2 and PR from an admin account , and have you given them admin rights to run ? (both BF2 and PR.exe need this).

Also ticking the XP compatibility box on BF2.exe properties should help.

Um, I have Win XP, as stated above

Indeed ... so you do. In that case its probably something to do with your .NET installation. And you probably didn't clean your registry properly when you deinstalled. There is also an entry under BlackSandStudios that you should delete.

Somewhere like this .... ... but in your case it wont have that Wow6432Node bit in there.

Thank you Twisted_Helix, it was my .NET 3.5 SP1 that was somehow corrupted, thanks for the help