FXAA enabled in the NV CP causes blurry font in WLM.

boogeyman


FXAA enabled in the NV CP causes blurry font in WLM.

As stated in the release notes for this feature...
FXAA should not be enabled globally, rather it should be used on a per game basis and enabled in the "profile" settings tab.

maniacvvv

boogeyman


FXAA enabled in the NV CP causes blurry font in WLM.

As stated in the release notes for this feature...
FXAA should not be enabled globally, rather it should be used on a per game basis and enabled in the "profile" settings tab.

 
Didn't get to the notes yet, thanks for the heads up.

gonna dl this

okay so quick question... do you enable fxaa AND msaa (in game) or do you disable it and just use the fxaa in the control panel?

Please include support and performance improvements for older games in these driver updates....
 
Im talking games such as World in Conflict, Crysis 1, Bioshock, etc.
 
Also, please look at NR2003 (nascar racing 2003 season) and see if you can improve performance in a future driver update. Im getting much lower frames than i should with gtx 460 / gtx 680. It would help out many with playing that with nvidia cards

letterkilled


okay so quick question... do you enable fxaa AND msaa (in game) or do you disable it and just use the fxaa in the control panel?

Each game engine is different
 
For FXAA you can enable it in the "Program Settings" tab of the NVCP, but should NOT do so if there is an in-game option. If there -is- a in-game option (like BF3), the the NVCP Global tab should be left at default OFF and the in-game setting used....
 
For games -without- a in-game settings option for FXAA, you should enable it in the Program settings tab and then TEST the game.
 
*This will all be changing, as more games take advantage of the NVCP setting and Nvidia coding.
 
The best advice is to Google for the settings information on the game you want to play  

maniacvvv

maniacvvv

MPappas


They mention FXAA won't be available for any games that have an FXAA built-in option, such as BF3.  Can we disable BF3's FXAA and use Nvidia's?

Nope, sorry

This is because like the BF3 MSAA option, everything is custom coded by DICE...
You cannot use the NVCP (as noted in the release notes, the option is disabled by the profile)

I just got off the phone with someone I trust who says this may be incorrect.
Further testing will be needed to confirm it, as it involves modding the driver
*This -may- be detected by AE/Punkbuster as illegal, so it is suggested to WAIT and see what testing produces

I remember a long time ago Punkbuster was a program that u had to give permission to to at least do Multi-player Online, and said themselves that are essentially they do have Spyware. I know EAs stupid Origin is also completely Spyware because they admitted to it also in the Terms of Use. It Spyware should be illegal, but isn't at least here in California, and every1 know when u sign on to these Software Spyware programs u can bet they are spying on what ur useing unless ur useing special encrypted Software to prevent them from seeing what ur doing

way to jump way of topic and rant ...

packertown4


Please include support and performance improvements for older games in these driver updates....

Im talking games such as World in Conflict, Crysis 1, Bioshock, etc.

Also, please look at NR2003 (nascar racing 2003 season) and see if you can improve performance in a future driver update. Im getting much lower frames than i should with gtx 460 / gtx 680. It would help out many with playing that with nvidia cards

Need to ask Nvidia that on there forums, not EVGA. EVGA has nothing to do with the drivers.

BioHazardSperm


way to jump way of topic and rant ...

I wasn't totaly off topic as some1 else said that Punkbuster has Spyware, and could effect the driver he has, he thought. Not OFF-Topic whatsoever when ur trying to get the right driver. Maybe you should read up more and learn, and I sure as hell as didn't rant, I said that Origin is Spyware to. Which Spyware can mess up drivers like the 680 beta driver.
 
Get over it. As for me I don't like getting beta drivers, I like them when their fully done and tested by a large amount of ppl. But this driver Looks pretty good for a driver in Beta.

spyware has a  broad meaning and often exaggerated ,Altering a driver to override a games code is ? Yes technically its wrong and could be considered a violation of the TOS you agree to installing a game.That said if you are altering a driver its not PB fault if you get flagged as your completely in  the wrong .No where in this process would PB be the issue ,the user is the issue ,altering the driver .PB being installed has nothing to do with it or the fact its in your opinion spyware.That's why i consider it off topic .PB has no direct interaction with drivers only game/program files it scans for injection of illegal code into a active PB monitored process.
 
Did you know in the beginning PB was routinely tricked by running a program inside another to mask its footprint and active interactions with a running game?That is why now most ANY/EVERY anti cheat software checks your whole PC programs to find active processes linking into your game injecting game altering code.

Hmm you can still see some jagged or step-shape edges in FXAA.

BioHazardSperm


spyware has a  broad meaning and often exaggerated ,Altering a driver to override a games code is ? Yes technically its wrong and could be considered a violation of the TOS you agree to installing a game.That said if you are altering a driver its not PB fault if you get flagged as your completely in  the wrong .No where in this process would PB be the issue ,the user is the issue ,altering the driver .PB being installed has nothing to do with it or the fact its in your opinion spyware.That's why i consider it off topic .PB has no direct interaction with drivers only game/program files it scans for injection of illegal code into a active PB monitored process.

Did you know in the beginning PB was routinely tricked by running a program inside another to mask its footprint and active interactions with a running game?That is why now most ANY/EVERY anti cheat software checks your whole PC programs to find active processes linking into your game injecting game altering code.

That's right if it goes against other games and software, then it is violation, but I was just saying that that guy was talking about the problem with his new 680 Beta driver could be spyware, and I agreed with it, as u never know these days. You may not know it but we actually agreed on the Spyware issue. The bad part is that some of Spyware can leech onto programs and put in their own code on the program, whether it's the Beta Nvidia software or other software.

PB does not drop code only scans code,thus i said PB is not a issue with a driver ,altering it (the Driver) could be considered a violation by PB(and EA )but PB itself only scans active processes .Scanning programs has never brought driver errors,as it only checks its footprints and extensions and sends a report +/- to PB .

the issue with FXAA is that BF3 is locked and only can be changed game side (code)not by the driver ,if someone was to change it ,the process would/could be flagged as its not in the range of acceptable interactions.People used to run games in 8/16 bit to see more and have visual advantages ,now most games wont even install or run with sub standard equipment 

is this driver mainly just for the 680?  will it help the end of firmi 580?
 

I wonder why they didn't have a unified driver at launch?
 
Good way to skew the reviews, eh.

I usually do not get all excited about benches and what not, but you did a damn good job on this post. I appreciate you taking the time to show things from different perspectives as well (with screenshot comparisons). Since there is not really a "Thanks" or Kudos button (which I admittedly feel turns into a popularity ranking) I will just give your well deserved thanks and appreciation here

Has anyone noticed a performance difference in the directx versions with this driver? In particular, dx9 performs much worse than dx11.
 
On my gxt 680 sig/sc, running at 2560x1440 on an i7-940@3.52Ghz, and using Heaven 3.0 at default settings:
 
Dx9 - score 1250, 49.6 fps
Dx10 - score 1775, 70.5 fps
Dx11 - score 1917, 76.1 fps
 
Directx 9 seems to do significantly worse. 
 
I've not tried the 301.10 WHQL drivers, so I don't know if they have the same issue.
 

Does FXAA only work on Kepler Chipsets?

Any news on when we'll get newer drivers? 
 
It's been over a month since I got my 2x GTX680's and we're still stuck to the 301.10 WHQL and 301.24 BETA (Which are the same to me), I think it's about time to get newer drivers. 

I've been using the 301.25 drivers with no real issues.

unless you change the 301.25 ini file its only for 670/680 GPU's .Have not heard anything bad about people with non 600's using them so far but i skipped that one .

I have a 680 lol. I just upgraded to the 301.32s. Gonna give them a whirl in a bit.

Yeah, I've been wondering the same thing. Nvidia's launch support is awful. I don't think that I've seen Nvidia respond once in the GTX600 series section of their forums. 
 

kcuestag


Any news on when we'll get newer drivers? 

It's been over a month since I got my 2x GTX680's and we're still stuck to the 301.10 WHQL and 301.24 BETA (Which are the same to me), I think it's about time to get newer drivers. 

very stable beta!