Widescreen Gaming Forum

No AA or AF have ever been forced, which is another odd part.

Games in general are fine. My 3D Mark score is up in 5000 and CS: Source runs at 120 frames per second with everything maxed out. Battlefield 2 runs slightly better than usual because of the lower resolution..

Absoloutely everything is 100% perfect apart from F.E.A.R. That's a good thing, I suppose. I just really, really want to play F.E.A.R though. If the expansion doesn't come out for the 360, I'm gonna be a little upset.

is there a profile for fear in that forceware? if so, any dodgy settings, sometimes the nV drivers force stuff that shouldnt be, at least the gfx card isnt faulty :)

_________________
P8Z68-V Pro | 2600K | HR02 | HD5850 | 2x4GB Vengeance LP | 128GB M4 + 6TB | X-Fi > HD595 | AX850 | Tai Chi | PB278Q | G110 + Deathadder 2013
P8Z77-V | 3570K | Mugen 2 | HD5850 | 2x4GB Vengeance LP | 500GB | X-750 | Fractal R3 | U2212HM | G110 + G400
P8H77-I | G860 | 4650 | 2x2GB XMS | 320GB | CX500 | Prodigy | T22B350EW | MX518
DC3217IYE | 1x4GB Vengeance | 64GB M4 | TX-42VT20E

sorry about the long delay in my reply. but no my computer is not over clocked. the only thing i have running in the background/systray are my logitech mouse control panel and the nvidia control panel. how did you reset the hardware acceleration? i'd like to try that so at least it i can get it to work temporarily.

edit: ha! i just reinstalled fear and it works fine. i didn't patch it yet and i didn't change settings file yet to run it in widescreen so i'm keeping my fingers crossed.

nevermind... i was playing unreal tournament and day of defeat source... went back to play some fear and alas, same slow framerate...

i wonder if this has anything to do with it... i tried playing a really, really old game called forsaken by acclaim that was released in 1998. it supports widescreen. i just tried playing it and it says CreateSurface for Z-buffer failed. The pixel format was invalid as specified.

is there a profile for fear in that forceware? if so, any dodgy settings, sometimes the nV drivers force stuff that shouldnt be, at least the gfx card isnt faulty :)

Eh, stupid question, but how do I find out if there's a profile for F.E.A.R. in the forceware?

Eh, stupid question, but how do I find out if there's a profile for F.E.A.R. in the forceware?

Take a look here.

This is strange - I have much the same problem. Can't say it's exactly the same, but close.

Before I bought my widescreen, I only had the single player demo of FEAR - and the time demo to check my frame rates.

When I bought my widescreen, I picked up a full copy of FEAR.

I was expecting it to run better, because I knew the full game had been patched at least once, and had read that it had been optimized since the demo came out, etc ...

Right away I was let down. Frame rates were very inconsistent - I mean I could just be walking down an alley and it would start stuttering.

Okay, I think, maybe it doesn't like the new 1440x900 resolution I forced it into through the .cfg file as specified here. After all, before on my old 4:3 monitor I was only running it at 1024x768 ... Maybe the res is too high for my low level system (Athlon 64 3500, Geforce 6800, gig of ram).

So I drop it down to 640x480 and ... no improvement. I mean, maybe a little faster in some places, but the stuttering and poor frame rate was exactly the same.

Haven't tried uninstalling/reinstalling yet, but I will if that might help ... It is frustrating, because like the thread starter I was really looking forward to playing this in widescreen ...

EDIT: Forgot to say that the timedemo - which looks exactly the same for the full version as it did for the multiplayer demo - now suffers from a major drop in frame rate/stuttering too ...

WTF?

Update: Checked for forceware profiles, everything is pretty much set to "let application decide", so that's not the problem, it seems.

Edit: Just curious if anyone else with this problem has tried a hard drive reformat? I'm starting to consider that option.

Okay, new update.

Question: is there any way to set the heapsize in FEAR, like you can in Source games? Because I've discovered that if I set a heapsize in Half-Life 2 or CS Source, etc, my PC will have the very same crash as it would with FEAR (before it stopped itself working.. hm, perhaps the heapsize it attempts to set it to is too high, and so it auto-turns it down for me? hmm.. maybe some extra memory may be needed... but still, why the monitor triggering?).

I feel really bad about the triple post, but considering the timespace between each, I think it should be acceptable.

Anyway, I got it working, and in case anyone else had problems, I think this will fix it.

After the FEAR: Extraction Point demo came out, I really wanted to try it out. Not just because I've been looking forward to this expansion for what seems like ages, but also because I wanted to see if it would run. It did, and I rejoiced. This rekindled my faith in FEAR, and I set out to try and find the solution.

I read on a forum about this guy who deleted the FEAR folder and didn't actually officially 'uninstall it' and the advice was to delete the registry files. Now, considering re-installing worked for others, this made sense to me. The only thing was that I tried deleting the registry files, to no avail. But it looks like I must have missed some, because desparately, I downloaded CCleaner and wiped FEAR from the registry, re-installed - and bam - it works. I'm currently running FEAR at 1400x900 with all textures, sounds, and particle effects cranked up to max (included x4 AA and x166 AF), without soft shadows. This used to run at 12-18fps. But the Performance Test this time claimed 87% was above 40fps, and the lowest fps was 33. So, yeah. I think it worked.

So, in case you can't be bothered reading this long winded story and just want the solution, if re-installing did not work, I strongly suggest you un-install, delete all registry entries, then re-install.

Happiness ensues.

Edit: In fact, ignore ALL of that. I've found the source of the problem! Are any of you guys running Xfire? I went to play again today, and found the stuttering was back. So, getting annoyed, I checked to see if there were any resource allocation issues. So I closed Xfire and stopped Avast!, and hey presto! It worked! Curious, I tried running it with/without Xfire, and I finally concluded Xfire was the problem. Very, very curious indeed. Of note was that last night, when it did work, Xfire did not detect me playing it.

So, I'll repeat that: XFIRE IS THE PROBLEM. Unless any of the others who had the same problem as me don't run Xfire, in which case, I'm stumped. I'm pretty sure this thread is now finished, so thanks to everyone for their support!