GeForce 304.48 Beta Driver

I could notice the vsync issue in BF3 but this new driver made the game buttery smooth. I've never noticed such a big difference in performance just from a driver before. Haven't had any issue with my 680 so far.
 
Yeah I just had one of the best bf3 experiences yet with these new drivers and Ive tried a little bit of everything. Great job on these drivers.
 
Zarathustra[H];1038847668 said:
I never noticed this. Glad it's fixed though :p

You probably didn't have the problem, it only effected some user.
 
this is strange.. drivers keep telling me I have windows 8.. Ive never seen windows 8 soo.. no beta drivers for me.. pity
 
Check your link before you bitch about mine :)

Your welcome

My link was fine when I posted it, apparently at some point afterward someone was messing around in vBulletin and censored 'nvidia.com' for whatever reason. Odd...
 
I still have huge stuttering and low FPS in BC2 even with this driver, game is unplayable. set the gfx settings at the lowest and tried different vsync settings in-game and in Nvidia CP and I still have the problem with my GTX 670. no problems in BF3 though!
 
Wow... Smoothest BF3 experience I've had since I bought the game 3 months ago, runs at a constant 60fps with adaptive vsync and is smooth as hell. Also gained a few fps ( 4-5 on avg ) with physx on high and dx11 extreme..
 
I dont think you guys are actually getting a "constant" 60 fps. every single game I have fired up still goes to 59 fps every few seconds.
 
Are you getting tearing at 59fps?
with adaptive vsync there might be a really quick tear but it goes back to 60 so quick that tearing is not the problem. it just sometimes causes a tiny little stutter or hitch especially with normal vsync. after getting some more gameplay time, I would say its a huge improvement overall over what it was though. I really have to look for it now and that is because I am still paranoid based on how it was performing with the previous driver. if I just dont look at the framerate then I probably will never tell.
 
anyone still using a 460 have anything to report good or bad?
 
I dont think you guys are actually getting a "constant" 60 fps. every single game I have fired up still goes to 59 fps every few seconds.
I've seen that if I stare at the framerate graph, but my eyes don't detect anything out of the ordinary.
 
I saw a pretty definitive improvement with Arkham City. I have everything turned on except AA (PhysX on med) and in the benchmark my average went from 53fps to 58. It's "only" 5FPS, but the bottom outs in certain areas more or less went away, too.
Not bad for a driver update!
 
Yeah, my BF3 performance tanked with these drivers (4x680)...now getting about 20 FPS at 5760x1080...was getting around 60-80 FPS prior. Nothing else changed. Still no fix for PCIe 2.0 on X79, either. Abandoning ship and going Z77 this week.
 
Of interest to a very few, these drivers create an artificial pixel clock limit of 330MHz over DVI, limiting the refresh rates possible on large monitors.

For reference, that is still above 60Hz refresh @ 2560x1600 so very few people care, but it broke my 1440p@120Hz setup so I'm not happy.
 
Had to use a modified INF to get this to install for a laptop based GTX660, took me a minute to figure out how to do this. You can find a modified INF at http://laptopvideo2go.com/ just replace the cfg file in the extracted install files with the modified inf, this is for people who need these drivers but it isn't detecting your card correctly.

Once I did this it did make Tribes Ascend playable for me which is the only I have been wanting to play on this machine (ASUS G75VW). Before this beta driver the game would crash on launch which was quite disturbing considering I have a supposed gaming laptop. Now I am playing Tribes on high settings with a very acceptable framerate 40ish to 60ish, may lower the settings a little and see what I can get later but it has fixed at least one problem I was having...being able to play Tribes Ascend.
 
Of interest to a very few, these drivers create an artificial pixel clock limit of 330MHz over DVI, limiting the refresh rates possible on large monitors.

For reference, that is still above 60Hz refresh @ 2560x1600 so very few people care, but it broke my 1440p@120Hz setup so I'm not happy.

That might be my issue then! Thank you. I've got 3x120hz monitors. Man...
 
That might be my issue then! Thank you. I've got 3x120hz monitors. Man...

Unlikely, but it could be somewhat related. Really, this limits your refresh rate not your FPS, and it shouldn't have any effect on 3x monitors, since each output *should* have its own RAMDAC at up to 330MHz. But these are beta drivers so who knows what change is screwing up what :p
 
Considering STEAM is coming to Linux, I sure hope nVidia gets their ass back into fucking gear for getting parity with Linux.

Until them, I agree with Linus.
 
Previous driver versions would BSOD with my 680s, first time in months my system got a BSODed.

I am glad that reports are showing improved stability.
 
these drivers completely screw up Deus Ex HR in DX11. it only runs at 1fps so you have to go to widowed mode to get the game going properly. its shit like this that makes me hate pc gaming. its seems its always something that gets screwed up when they try to fix other screw ups. :rolleyes:
 
these drivers completely screw up Deus Ex HR in DX11. it only runs at 1fps so you have to go to widowed mode to get the game going properly. its shit like this that makes me hate pc gaming. its seems its always something that gets screwed up when they try to fix other screw ups. :rolleyes:

Thats odd, I'm getting great FPS with it in DX11 mode. Perhaps a local setting is messing things up?

Of course I'm using the "Advanced 3D settings" in the NV control panel and I'm also running SLI, which may make a big difference if you're on a single card.

Sitting here with VSync off and 300+ FPS showing on FRAPS.

Overall these drivers have been pretty solid for me, though I've yet to really test all my normal games due to work etc.
 
Thats odd, I'm getting great FPS with it in DX11 mode. Perhaps a local setting is messing things up?

Of course I'm using the "Advanced 3D settings" in the NV control panel and I'm also running SLI, which may make a big difference if you're on a single card.

Sitting here with VSync off and 300+ FPS showing on FRAPS.

Overall these drivers have been pretty solid for me, though I've yet to really test all my normal games due to work etc.
its the start up movie in DX11 and it is a confirmed issue by many others that it runs a 1fps unless you alt tab until it gets to the menu. its the new drivers and the problem is not just on 6 series cards.
 
its the start up movie in DX11 and it is a confirmed issue by many others that it runs a 1fps unless you alt tab until it gets to the menu. its the new drivers and the problem is not just on 6 series cards.

Ah ok. I dont get that problem on my machine, but it's likely something the devs did to "work around" something in the drivers and when NV made their changes, it borked something.

It's always been that way it seems. The price we pay for gaming on the better platform. ;)
 
Could be a game bug exposed by the new drivers; wouldn't be the first time. Or maybe it's the drivers. Either way, gamers are pissed, haha.
 
these drivers completely screw up Deus Ex HR in DX11. it only runs at 1fps so you have to go to widowed mode to get the game going properly. its shit like this that makes me hate pc gaming. its seems its always something that gets screwed up when they try to fix other screw ups. :rolleyes:

BETA driver!

You brought this pain onto yourself. ;)
 
BETA driver!

You brought this pain onto yourself. ;)
um you must be kidding if you think WHQL drivers means anything better than "BETA". Nvidia's worst drivers, such as the one that lets cards overheat, were WHQL.
 
I take it all back...somehow everything is now working fine in BF3 MP with these new drivers. Must have been the reboots or perhaps my OC. Who knows. Anyway...best experience yet with BF3 MP, quad-SLI, at 5760x1080. Really smooth. Nice work, NVIDIA.
 
Guys these drivers are constantly crashing for me in BF3.

1. Constant Crashing in BF3 - I never had this issue with the earlier ones. The microstutter is definitely improved but not worth it FOR ME at this cost. The system is 690 Quad SLI at +100 core and +150 mem. Heaven runs just fine for several runs without crashin on this OC. Could it be the OC causing the crashing and somehow destabilising the hardware?

2. Absolutely ZERO improvement in Shogun2. Can someone else please verify the Shogun 2 issue?
 
Last edited:
um you must be kidding if you think WHQL drivers means anything better than "BETA". Nvidia's worst drivers, such as the one that lets cards overheat, were WHQL.

I equally don't care for WHQL, however, beta drivers are clearly those which have not undergone nvidia's full testing procedure.

I interpret nvidia's 'beta' to simply mean, "not 100% tested, there may be issues, but as this is beta you're on you're own.".


Anyway, installed these last night on my 470 and everything seems good. Couldn't say if there's any real improvement over last WHQL, but nothing appears to be broken.
 
Installed lastnight and seems to be working as intended. I didn't really have any issues prior but this also didn't affect OCing either way.
 
Wow...been playing with this driver for a day and I think it's absolutely great. While Diablo III was patched at the same time, performance there is definitely smoother. Batman AC's benchmark showed a 5FPS improvement and the game no longer bottom's out with Penguin's machinegun. Crysis 2 never seems to drop under 60FPS no matter what's going on (maxed out) even when it used to go under 50fps in some areas.
Something they did with this driver has made me a happy man.
 
Guys these drivers are constantly crashing for me in BF3.

1. Constant Crashing in BF3 - I never had this issue with the earlier ones. The microstutter is definitely improved but not worth it FOR ME at this cost. The system is 690 Quad SLI at +100 core and +150 mem. Heaven runs just fine for several runs without crashin on this OC. Could it be the OC causing the crashing and somehow destabilising the hardware?

Why do people ask this without first trying stock clocks or even underclocking first? Like somehow forum members can divine from great distance if their oc is flaky or not with a crystal ball. Certainly new drivers could lean on the hardware harder (more efficiently) or in a different way. Or it could be a driver bug, or even a game bug exposed by new drivers.
 
Back
Top