New Nvidia 344.48 Drivers Doubled My FPS

[ZATZAi]

Nvidia has released new WHQL Certified drivers, v344.48 with support for Elite Dangerous. It doesn't seem to add anything to the Geforce Experience but the drivers have optimizations for the game. Micro-stutter can still happen, and the lighting bug can still happen (Where everything is a touch too bright until you go in and out of the galaxy map), it seems these are problems with the game that Frontier has to fix not the drivers.

http://www.geforce.com/drivers

I've now installed the 344.48 drivers, I did a clean install via the Nvidia setup (So no special cleaners). This of course disabled SLI and Surround as a new driver update always does, so I re-enabled surround and configured it how I like. It also wiped some of my Display Fusion settings strangely, so that took a minute to get back the way I like (My custom taskbars specifically, maybe because it thought they were new monitors?).

Anyway now I have loaded up the game and so far it is running just fine. More than fine actually as I am getting around double the FPS that I was with the old drivers. Before I was getting 30-45 in station now I am getting 60-85 FPS in station. In space before I was getting 60-75, now I am getting 85-105 FPS in space. So at least so far I am very pleased with this driver update.

Here are my system stats for those curious.

Windows 8.1 Pro 64bit
Nvidia Driver 344.48 (Only Graphics Driver & PhysX installed, no 3D Vision or audio)
Intel i7-3770K 3.5GHz - 3.9GHz Turbo (Running Stock)
16GB DDR3 @ 800MHz RAM (Dual Channel Mode)
500GB Samsung EVO SSD (Not Encrypted)
Dual EVGA 780 ACX 3GB (Running Stock)
Three 1920 x 1080 Monitors (Connected via DVI)
Desktop Resolution 5760x1080
Fullscreen Resolution 5860x1080 (55 Pixel Bezel Correction)

Here are some screenshots from PlayClaw, you can see the FPS I am getting in the top left corner.

[DevNull]

Thanks
as soon as i come back to home i'll update mines

PS:
Behold, my gorgeous new signature (© Mobius)

[Wolf]

That sounds great. Mine didn't want to upgrade yesterday. Gave me errors. I have to look into the installation.

[Vikinger]

Ive dl it but I have no time to test it until this evening.
Iam gona check as well if there is better support for 3D vision.

[Neillm]

Downloaded and installed here but a minor irritant called work is stopping me testing. Curses!

[Avago-Earo]

My GeForce Experience update kept failing when it got to installing PhysX. Can't find a solution anywhere. Tried to install the PhysX driver (9.14.0702) directly from Nvidia but it just gave me a message. I think it was to do with file paths. Could have been permissions. Can't remember as I looked everywhere for guidance.

Un-installed all Nvidia drivers then fresh install but still the same problem.

This morning IO Bit Driver Boost identified PhysX drivers were out of date and installed new ones so maybe that's sorted it. Just don't know enough on the subject to be sure.

[Avago-Earo]

That sounds great. Mine didn't want to upgrade yesterday. Gave me errors. I have to look into the installation.

Same here. Is it the same issue as with my post above?

[Wolf]

That sounds great. Mine didn't want to upgrade yesterday. Gave me errors. I have to look into the installation.

Same here. Is it the same issue as with my post above?

Don't think so. It just hung itself. Didn't continue. So I think I won't have big problems doing a complete reinstall as it sounds just like an interupted update.
I have no idea what could cause your problems, sorry.

[Neillm]

If it's of any help, following a successful installation, here are the components that are installed:

[Brixmis]

I'm surprised to hear about the issues - I haven't noticed anything driver related in game and my FPS is normally stuck right up to the 60 limit. On very rare occasions it might drop a couple of frames under - but it's very rare and I've no reason to be unhappy at all

Will still update, of course, but actually noticing an increase in framerates isn't going to happen, for sure.

PS - just noticed the res you are running at, which could explain your previous relatively low framerates