Ghostbusters - I can't get past the cemetery

[ShawnD1]

Has anyone else run into a problem in the cemetery stage? I'm at the part where I tether the gate to the car and they pull it down. Up until this point, I was getting a solid 60fps and the game ran great. At this part of the game, the frame rate is totally fucked. I'm getting 1-5 frames per second even when I turn the resolution down to 640x480 and all graphics options are turned off.

Has anyone else had this problem? I tried loading past stages and they all worked fine. It's only this one part that doesn't work at all.

 

[Kalmah]

Yeah, same thing for me. From that point on out until the end of the game is bad framerates.
What ended up helping me, after turning settings down in the game, was going into the nvidia control panel and lowering all of the settings for that specific game.

 

[ShawnD1]

I found a solution to this. After googling around for a while, a guy suggested setting the game to low CPU priority. It's really stupid, but it actually worked.

I guess it's possible the game is calling on some important background task. Quake 4 has severe mouse lag when running at high priority. Gears of War can't load maps if priority is given to "background tasks" in system settings.

 

[bunnyfubbles]

Sounds like pretty ignorant computing for gamers to change such settings such as processor scheduling and CPU priority

Its one thing to change it to fix a problem, but its another to change it in the first place (hopefully for some legitimate reason and not some un or misinformed notion that it will improve gaming performance) so that it actually causes the problem.

 

[GaryJohnson]

Originally posted by: bunnyfubbles
Sounds like pretty ignorant computing for gamers to change such settings such as processor scheduling and CPU priority

Its one thing to change it to fix a problem, but its another to change it in the first place (hopefully for some legitimate reason and not some un or misinformed notion that it will improve gaming performance) so that it actually causes the problem.

It's pretty ignorant to assume whoever changed it didn't have a legitimate reason for doing so.