Project Reality Forums

So I've found where other people have similar problems that have been answered, but nothing works for me. My problem is actually twofold because I have a partitioned hard drive and I have PR installed on both partitions. One partition runs Windows 7 (64bit) Ultimate and the other runs Windows XP SP2. I'll start with the relevant specs:

Processor: Intel Core i5 - 760 @2.8GHz
RAM: 4gb
Video card: NVIDIA GeForce GTX 460

On both OS's, I run the game at mostly medium with a reasonable resolution. For intensive settings like dynamic light and shadow, I run it at low, but that doesn't seem to help at all (I just never changed it back after giving up on the problem). The problems for both OS's is different, so I know it can't be my system or the settings.

First the Win 7 problem. It seems to be RAM-related, but I'm not sure how that can be since I don't get the same problem on the XP partition. What happens is that the game causes my computer (picture, sound, and I guess entire OS) to freeze up. Prior to that, the game runs fine with the exception of the skins for FOB's and hideouts being gone, leaving them totally black. So if I can fix the freezing and texture problems, then I wouldn't have to deal with the very annoying XP problem.

The XP problem actually allows me to play the game, just with one annoying and constant issue: my controls seize up every 10-30 seconds for about 1 to 3 seconds, sometimes a bit longer. It's constant and never causes the game to crash or even freeze. I can see everything happening as it would, and whatever controls I was inputting at the time, except for mouse movements, just continues for the duration of the hiccup. So if I was firing an automatic weapon, it continues until finishing the magazine or until I regain control. It seems to happen a little more often when there's something going on around me, but even if I'm just sitting around looking in the dirt it will still happen. Needless to say, choppers and jets are out of the question.

So the Win7 problem never occurs with the XP game, and the XP problem never occurs with the Win7 game. If I could fix either of these problems, I would be a happy camper. As it is now, I have to make due to the XP problem, even though it gets me killed quite a few times (enemy pops up close to me but I can't aim at him).

to freeze up. Prior to that, the game runs fine with the exception of the skins for FOB's and hideouts being gone, leaving them totally black.

This is an easy fix for your win7 install.
You can try to delete your shaders cache and let the game optimize them again. To do this, navigate to My Documents > Battlefield 2 >mods >bf2 and delete cache folder. Run PR and let it optimize shaders again.

Second problem on win7, the freezing/stuttering problem.
I am helping Dendari who has the win7 and a GTX 460 also, and has same problem as you.
Please read this thread and try the suggestions I added in this link:
https://www.realitymod.com/forum/f27-pr ... eplay.html

Most importnantly, IMHO, "Have you tried turning AntiAlias OFF completely and tested on a online server? Does it help?"

Please tell me the make and model of your GTX 460, and please tell me the version of NVidia drivers you are using.

After you try the suggestions in the above link, post here with a synopsis of what you tried and any results.

Whichever OS is in the back of your HDD could be lagging due to read/write bottlenecks on a mechanical hard drive, btw.

Get back to us when you can.

Not sure what you mean by "make and model" of the video card. All I saw was the info I already posted, unless there's another place to look for such things that I don't know about.

Deleting the cache folder solved the black objects problem and seemed to give me a little more time in game than I had before, but it still ended up freezing my computer after about 30 minutes of playing split between two servers.

I have been playing with Anti-aliasing and dynamic shadows off and dynamic lighting on low, everything else on medium.

I just updated my drivers as well but obviously it had no effect. My drivers are the newest ones: version 301.42 WHQL.

I'm going to try the command prompt idea you told Dendari about. If that fails, then I have no idea. Might as well get a new video card in the near future.

So the command prompt idea didn't work at all. It froze up in less than 10 minutes.

Also, after watching the video that Dendari posted of his problem, it seems to be something totally different from what I'm experiencing. His is constant, small jerking where mine is intermittent freezes of most of my controls. I'll try to make a video of what my problem looks like.

Here's a video of it. You can see it at 9 or 10 seconds and then a couple times later.

Stupid lag problem or some such bullshit - YouTube

Sex_Cactus wrote:First the Win 7 problem. What happens is that the game causes my computer (picture, sound, and I guess entire OS) to freeze up.

Do you use a headset/speakers attached to your motherboard's onboard audio device, by any chance?

If it helps I have a EVGA GTX460 768. I do not have this issue. I have the latest drivers. will check resolution and in game settings if you think it would help this discussion:

cpu: Quad core Q6600 @ 3.0GHz
ram: 8GBs
gpu: EVGA GTX460 768
WIN7 64bit
HDD
onboard sound
headset plugged in via 3.5mm jacks when needed.

Game crashes with looping audio requiring reboot - Windows 7
First of all if you are using a genuine copy of windows (Not a cracked copy) then please try seeing the other fixes offered. If you are using a cracked copy of windows and are using the "RemoveWAT" program then Punkbuster occasionally has an issue with this forcing the game and your pc to lock up.

Using the "RemoveWAT" program restore WAT onto your computer. (Online guides will help with this)
Once your computer is back into its unregistered (Non Genuine) state download a program called "Windows 7 loader by daz" you will want to use version 2.1 or higher.
Follow the steps included and check windows is now Genuine
Now you should be able to play PR without crashes !

The reason this works is because the "RemoveWAT" program only removed the authentication checker included within windows so that microsoft cannot check if you are running a valid copy, punkbuster detects this and shuts down the game, subsequently locking up the game at the same time !
I hope this helps with your problem !

I have been playing perfectly fine for the past maybe 3 months on BF2 PR all High settings , 1680X1050, 100 veiw and 8x AA ,but 3 days ago now I'm getting choppy frames that will dop from 100 to 24 and mostly when I move left to right now.

Win 64bit
8 gbs Ram
Gtx 460 1gb
AMD Phenom II x4 945 3.ghz

Even if I turn down to low settings, 85 view and 0 AA it does it. My old 9500 gt had no problems my 550 ti had no problems and This 460 had nothing until a few days ago. Puzzled.

SAM609, I tried your suggestion and it didn't help, unfortunately.

I also tripled my RAM to 12 GBs, and that has had no effect on the Win7 or XP problems. I am all out of ideas. Nothing has helped even a bit.

Sex_Cactus wrote:SAM609, I tried your suggestion and it didn't help, unfortunately.

I also tripled my RAM to 12 GBs, and that has had no effect on the Win7 or XP problems. I am all out of ideas. Nothing has helped even a bit.

I realize my earlier response probably got buried under the mass of replies that your thread got, so it's totally understandable how you ignored my question.

Psyrus wrote:I realize my earlier response probably got buried under the mass of replies that your thread got, so it's totally understandable how you ignored my question.

I didn't respond because there is no chance that plugging my speakers/headset into the regular jack can affect the entire computer like that.

Sex_Cactus wrote:I didn't respond because there is no chance that plugging my speakers/headset into the regular jack can affect the entire computer like that.

Ok, best of luck solving your problem, you're clearly on top of it.

Psyrus ir right on the money. I had the same problem. Computer freeze after 1 or 2 min. Then i plugged in my headphones and i could play for 30 min, then again freeze And then i disabled my sound card completely and no problems so far. Except of course playing without sound .

Weird problem. Thank you Google and Psyrus

Psyrus how does that effect the PC?

I have just had the same problem and I have just got new PC speakers!! Corsair SP2500.
I also have a USB headset plugged in too which worked fine.

(I did however have am old set of speakers in before and were fine)

PC Spec:

Win 7 64 Bit
ASUSTeK P5Q-E
Intel Core 2 Quad Q6600 @ 2.40GHz
6GB RAM
Asus NVIDIA GeForce GTX 560 Ti

SuperArmy wrote:Psyrus how does that effect the PC?

I have just had the same problem and I have just got new PC speakers!! Corsair SP2500.
I also have a USB headset plugged in too which worked fine.

(I did however have am old set of speakers in before and were fine)

PC Spec:

Win 7 64 Bit
ASUSTeK P5Q-E
Intel Core 2 Quad Q6600 @ 2.40GHz
6GB RAM
Asus NVIDIA GeForce GTX 560 Ti

The issue is usually with on-board soundcards and an incompatibility between windows 7, BF2 and the drivers for the on-board soundcard. The biggest culprit is Realtek. They basically freeze/bluescreen a player's computer when certain sounds are played in PR. Disabling the soundcard (and thus losing sound) is a good way to test.

Having a USB headset means that your soundcard will be bypassed as long as you're using it, which would explain why it doesn't freeze when using that.

I recall someone once told me that they found drivers that didn't crash the computer, but you'd have to do your own testing as I have no idea what drivers they would be, nor how to go about finding them

But it's always good to be able to isolate the source of an issue!

thanks.

would one way to fix it be to buy a sound card for the PC ?

SuperArmy wrote:thanks.

would one way to fix it be to buy a sound card for the PC ?

Yes, usually, or use USB based sound-solutions as above. Watch out for Titanium HD something something angry man, though. Don't spend money on new hardware unless you're sure (100%) that it's the soundcard. Tested by disabling the sound card in the bios.

My preferred solution would be for someone with the onboard card to test out all the drivers, find one that doesn't crash and let everyone know which one it is, so I can just tell people to install that one in the future