Project Reality Forums

Hi all,

Within thirty seconds of deploying to a game (i.e. clicking the join button), PR CTD's. This occurs regardless of the ingame activity I'm performing at the time - be it looking at the spawn screen, walking around or doing nothing at all.

I've tried all the troubleshooting steps mentioned in the Vista troubleshooting sticky EXCEPT for reinstalling PR, because the game worked fine yesterday and in my experience, blind re-installs rarely cure anything. I've tried clearing my BF2 caches, deleting my Battlefield 2 folder in My Documents, and running the game in windowed mode to catch any debugging output - there's never been any. It just CTD's; no dialog boxes, no logfiles, nothing. The crash itself is all I see.

vBF2 seems to play fine for extended periods of time.

Now, this all started just today; yesterday I was playing PR just fine. After I started my laptop this morning, Vista installed two of the updates it had downloaded the previous night - the one I'm looking at closely was "Microsoft .NET Framework 3.5 SP1, Windows Vista SP2, and Windows Server 2008 Update x86 (KB982536)". My question is this: could an update to the .NET Framework be causing some problems with PR for Vista users? Is anyone else on Vista 32bit having difficulties playing the game?

I'd just like to get some reassurance from someone who knows the internals of the game before I start reverting Vista updates; or, if you reckon I've misdiagnosed, any suggestions you may have would be great.

(Hardware specs: Core2Duo P8400 2.26Ghz, 2GB of RAM, ATI Radeon HD3470. Running Vista Home Premium SP2, 32 bit, with UAC disabled).

Thanks in advance for any help.

I can't reach my PC at the moment but i've suddenly started getting random CTDs aswell although not as quickly or regularly as u seem to.
I noticed that my framework has also been updated, when I can get to my desktop I'll have a look if the update date was around the same time.

Also finding this an issue. Twice in the last five minuites.

My .net update was after my CTD

Heh. As silly as this will make me sound, a reboot fixed everything. Word to the wise - don't make an idiot of yourself like I did; if you're experiencing problems after Windows Updates, REBOOT first.

This particular update can't actually be removed either, so it's just as well the reboot fixed it. Hope this works for you guys, and if it doesn't, good luck - I know how frustrating random errors are.