I've Had It With the 175.16s!

[BoeingGuy 0]

OK, I'm certainly going back to 169.25.175.16s may give much better image quality, BUT:FSX stutters humongously, with frames locked or unlocked. Too many blurries, and nHancer or not, I get about 10 FPS slower than with the older drivers. Way too many driver lock-ups and freezes.So I get bored of these problems and I open up Midtown Madness 2 (a 2001 game), and within about 2 minutes of opening it, the video driver permanently crashes and I have to reboot. I've had it! Could NVIDIA stoop any lower?

[Guest JIMJAM]

I went back to the 169.28 drivers.Of course now If I try to run one of the latest games, I might run into problems but Im done with the driver shuffle.Instead of chasing the FSX carrot and spending $400+ for the 768 meg 8800, I went and bought a PS3.My BFG 8800gt will just have to do until the fall when I plan on moving to intel.BTW- My PS3 has not crashed or locked up yet.Whens the PS3 FSX version coming out.:-wink2 That will stir em up......

[BoeingGuy 0]

:-lolSadly I only have a Wii. Oh well. Went back to the 169.25s and everything works like a charm all of a sudden!

[Guest D17S]

I had my 8800GT bios O/C'd to 700Mhz and all was well with the previous driver. I loaded up the latest and greatest and I started getting the dreaded "Driver has stopped responding . . . and recovered." Seemed this tended to happen at a max-load moment, like a PMDG 744 flare. Since this was a bios mod, I had to use Riva to declock back to the 600mhz default. It's been fine at this default clock. Is an extra FPS worth going though the driver reload drill to go-back? Not right now. Maybe later. It was just a dumb Nvidia annoyance had me ready to RMA that Vcard.

[BoeingGuy 0]

I suppose so.Anyways, with the 169.25s I'm getting splendid performance even in the most dense cities WITH nHancer. I'll probably try out the 169.28s later and see what difference that makes.