30X.XX drivers for older cards? Will we get options like FXAA and Adaptive vsync?
  1 / 5    
I was wondering if we'll get some of the new features of the 300 driver series, such as FXAA (at the driver level) and adaptive vsync, or is this only for the GTX 680?
I was wondering if we'll get some of the new features of the 300 driver series, such as FXAA (at the driver level) and adaptive vsync, or is this only for the GTX 680?

#1
Posted 03/22/2012 02:13 PM   
At the moment, FXAA is working nicely for older cards. Lets hope Nvidia decides to keep it that way.

As far as adaptive vsync, I already found a bug with it.
At the moment, FXAA is working nicely for older cards. Lets hope Nvidia decides to keep it that way.



As far as adaptive vsync, I already found a bug with it.

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#2
Posted 03/22/2012 02:17 PM   
I just installed 310.10 for my GTX 580 using a modified inf file from post #10 in the 300.10 thread over at the guru3d.com forums.
That inf file only works for the English USA-Only 64-bit driver.
I just installed 310.10 for my GTX 580 using a modified inf file from post #10 in the 300.10 thread over at the guru3d.com forums.

That inf file only works for the English USA-Only 64-bit driver.

EVGA GTX 780, Haswell 4770K cpu@3.9 GHz, 16GB RAM, Win 8.1 Pro 64-bit, ASUS Maximus VI Hero motherboard, 250 GB SSD drive, 750W PC Power & Cooling power supply, Samsung 46" LED 1080p TV @60Hz, Soundblaster Z PCI-e.

#3
Posted 03/22/2012 02:36 PM   
I used the default INF, changing the hardware ID 1180 and "GTX 680" to match my own. This is what has me a bit worried. Will it still work when drivers become official. We've seen them remove FXAA before after it was already working.
I used the default INF, changing the hardware ID 1180 and "GTX 680" to match my own. This is what has me a bit worried. Will it still work when drivers become official. We've seen them remove FXAA before after it was already working.

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#4
Posted 03/22/2012 02:48 PM   
FXAA wasn't in any screenshot I took with FRAPS. Anyone else have this issue too?
FXAA wasn't in any screenshot I took with FRAPS. Anyone else have this issue too?

Intel Core i7 3770K 4,3GHz & Thermalright True Spirit | ASUS P8Z77-V | SF Golden Green Pro 600W | Define R4 | 4x4GB G.SKILL Ripjaws X 1600MHz | ASUS GeForce GTX 780 DC2OC | Fujitsu P23T-6P IPS 75Hz | Creative Sound Blaster Zx | Sennheiser HD 595 | Samsung 830 128GB & 3x Samsung F3 1TB | Windows 8.1 Pro with Media Center x64

#5
Posted 03/22/2012 03:17 PM   
For months people have been waiting for the clearly-working FXAA and other features to be enabled in official drivers, with NVIDIA always saying "we'll put them out when they're done." Now it's obvious that some users were right all along - that the new features were held back for months in order to promote the launch of a new card. Thanks for supporting your customers, jerks.
For months people have been waiting for the clearly-working FXAA and other features to be enabled in official drivers, with NVIDIA always saying "we'll put them out when they're done." Now it's obvious that some users were right all along - that the new features were held back for months in order to promote the launch of a new card. Thanks for supporting your customers, jerks.

#6
Posted 03/22/2012 03:23 PM   
[quote name='Anarion' date='22 March 2012 - 11:17 AM' timestamp='1332429459' post='1386277']
FXAA wasn't in any screenshot I took with FRAPS. Anyone else have this issue too?
[/quote]

This is why FXAA is referred to as post-processing AA. No wonder Fraps has a hard time with it.
[quote name='Anarion' date='22 March 2012 - 11:17 AM' timestamp='1332429459' post='1386277']

FXAA wasn't in any screenshot I took with FRAPS. Anyone else have this issue too?





This is why FXAA is referred to as post-processing AA. No wonder Fraps has a hard time with it.

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#7
Posted 03/22/2012 03:24 PM   
[quote name='Anarion' date='22 March 2012 - 07:17 AM' timestamp='1332429459' post='1386277']
FXAA wasn't in any screenshot I took with FRAPS. Anyone else have this issue too?
[/quote]

[color="#4169E1"]I first noticed this while using driver 295.18 months ago.
My screenshots won't capture the aliasing that the FXAA is doing.
I won't see any jaggies while in the game but my screenshots will show them.
So don't expect the visual benefits of the FXAA to show up in screenshots but in actual gameplay it is there.[/color]
[quote name='Anarion' date='22 March 2012 - 07:17 AM' timestamp='1332429459' post='1386277']

FXAA wasn't in any screenshot I took with FRAPS. Anyone else have this issue too?





I first noticed this while using driver 295.18 months ago.

My screenshots won't capture the aliasing that the FXAA is doing.

I won't see any jaggies while in the game but my screenshots will show them.

So don't expect the visual benefits of the FXAA to show up in screenshots but in actual gameplay it is there.

EVGA GTX 780, Haswell 4770K cpu@3.9 GHz, 16GB RAM, Win 8.1 Pro 64-bit, ASUS Maximus VI Hero motherboard, 250 GB SSD drive, 750W PC Power & Cooling power supply, Samsung 46" LED 1080p TV @60Hz, Soundblaster Z PCI-e.

#8
Posted 03/22/2012 03:29 PM   
There is a 300.83 driver for Windows XP users being talked about in guru3d.com forums.
There is a 300.83 driver for Windows XP users being talked about in guru3d.com forums.

EVGA GTX 780, Haswell 4770K cpu@3.9 GHz, 16GB RAM, Win 8.1 Pro 64-bit, ASUS Maximus VI Hero motherboard, 250 GB SSD drive, 750W PC Power & Cooling power supply, Samsung 46" LED 1080p TV @60Hz, Soundblaster Z PCI-e.

#9
Posted 03/22/2012 03:41 PM   
Roger that, thanks. FXAA is working on that version too : )

Installed 301.10 on Win 8.
Roger that, thanks. FXAA is working on that version too : )



Installed 301.10 on Win 8.

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#10
Posted 03/22/2012 03:45 PM   
[quote name='nvtweakman' date='22 March 2012 - 06:45 PM' timestamp='1332431158' post='1386295']
Roger that, thanks. FXAA is working on that version too : )

Installed 301.10 on Win 8.
[/quote]
WDDM 1.2 support??
[quote name='nvtweakman' date='22 March 2012 - 06:45 PM' timestamp='1332431158' post='1386295']

Roger that, thanks. FXAA is working on that version too : )



Installed 301.10 on Win 8.



WDDM 1.2 support??

I7 3930k (C2) @4.5 1.32V/Rapmage 4 Formula/Corsair H80 + MX-3/4x4gb 1866MHz G.SKILL F3-14900CL9Q-16GBZL/SLI gigabyte GTX 680 +80 +500/ OCZ Vertex 3 MAX IPOS 120gb/2x seagate 7200.11 @ 560 raid0 (strap 128)/X-Fi Titanium/Corsair AX1200w/Silverstone Raven 2 (rv02b-w)/BENQ EW2730/mamba 2012/Windows 8 x64

#11
Posted 03/22/2012 04:13 PM   
WDDM 1.1 according to dxdiag
WDDM 1.1 according to dxdiag

"This is your code. These are also your bugs. Really. Yes, the API runtime and the
driver have bugs, but this is not one of them. Now go fix it already." -fgiesen

#12
Posted 03/22/2012 04:17 PM   
[quote name='nvtweakman' date='22 March 2012 - 07:17 PM' timestamp='1332433076' post='1386317']
WDDM 1.1 according to dxdiag
[/quote]
ok. thx =)
Works same as 296.17 ?
[quote name='nvtweakman' date='22 March 2012 - 07:17 PM' timestamp='1332433076' post='1386317']

WDDM 1.1 according to dxdiag



ok. thx =)

Works same as 296.17 ?

I7 3930k (C2) @4.5 1.32V/Rapmage 4 Formula/Corsair H80 + MX-3/4x4gb 1866MHz G.SKILL F3-14900CL9Q-16GBZL/SLI gigabyte GTX 680 +80 +500/ OCZ Vertex 3 MAX IPOS 120gb/2x seagate 7200.11 @ 560 raid0 (strap 128)/X-Fi Titanium/Corsair AX1200w/Silverstone Raven 2 (rv02b-w)/BENQ EW2730/mamba 2012/Windows 8 x64

#13
Posted 03/22/2012 04:26 PM   
Gigabyte NVidia driver 300.65 out for Windows XP 64-bit and XP 32-bit at Gigabyte downloads.
Gigabyte NVidia driver 300.65 out for Windows XP 64-bit and XP 32-bit at Gigabyte downloads.

EVGA GTX 780, Haswell 4770K cpu@3.9 GHz, 16GB RAM, Win 8.1 Pro 64-bit, ASUS Maximus VI Hero motherboard, 250 GB SSD drive, 750W PC Power & Cooling power supply, Samsung 46" LED 1080p TV @60Hz, Soundblaster Z PCI-e.

#14
Posted 03/22/2012 04:26 PM   
[quote name='Infinity7' date='22 March 2012 - 03:29 PM' timestamp='1332430188' post='1386289']
[color="#4169E1"]I first noticed this while using driver 295.18 months ago.
My screenshots won't capture the aliasing that the FXAA is doing.
I won't see any jaggies while in the game but my screenshots will show them.
So don't expect the visual benefits of the FXAA to show up in screenshots but in actual gameplay it is there.[/color]
[/quote]

In Windowed Mode you can FXAA capture, with "ALT"+"Print" Keys.
[quote name='Infinity7' date='22 March 2012 - 03:29 PM' timestamp='1332430188' post='1386289']

I first noticed this while using driver 295.18 months ago.

My screenshots won't capture the aliasing that the FXAA is doing.

I won't see any jaggies while in the game but my screenshots will show them.

So don't expect the visual benefits of the FXAA to show up in screenshots but in actual gameplay it is there.





In Windowed Mode you can FXAA capture, with "ALT"+"Print" Keys.

#15
Posted 03/22/2012 04:30 PM   
  1 / 5    
Scroll To Top