The whole display would start flickering wildly with any kind of 3D activity on screen; when I would open up the nVidia settings panel and go to...
The 162.50 caused any 3D applications to flicker on screen, so I went to 158.45, which have been working beautifully for me.
For what it's worth, I got an old laptop with a 32MB GeForce 2 Go (equivalent to a GeForce 2 MX 200) to run Vista using an XP driver. May or may...
Thanks, I'll check this out. :approval:
EDIT: Worked out great, I can now run MPEGs in Windows Media Player with BSOD. :cops:
Also a quick...
problem is, the damn nVidia Control Panel doesn't show up in Advanced Settings (I'm using 44.84; I got to see the panel when I installed modifed...
Hey man this looks rockin' gotta GeForce 4 Ti 4800 but will nontheless download and check this **** out!
Ever played Call of Duty? Didn't think so.
Anyway, yes, the Pacific Assault uses an in-house custom-built engine, but may have some obvious...
Working good for me.
In your Far Cry directory, open "system.cfg" in Notepad, and find the line:
make sure it looks like this (case sensitive!)...
Only for a PCI-Express GeForce FX - as to what THAT is, no idea.
For best performance, run with the Post Filter off and run the game in OpenGL instead of Direct3D.
Hey, I noticed the same thing! Even with normal drivers?!
Yup, everything looked good...until I fired up Painkiller....god, textures and everything look washed out, little color detail. Anyone else notice...
Everything works better with 56.72, awesome!
No problems here...everything is good.
For the time being, that is.
Besides complications with video cards, IW will need a monster CPU and lots of RAM to run smooth on max detail.
They still need to fix the FPS issues.....looks like a huge renderer overhaul IMO.
Those are multiplayer only maps, not extended single player missions.