Official NVIDIA 3D Vision 257.21/CD v1.29 Feedback Thread
  3 / 5    
Was there some changes made to the default look of 3d with these new drivers? Somehow things look better. The image looks a tad bit more converged at default settings and there is significantly less ghosting.
Was there some changes made to the default look of 3d with these new drivers? Somehow things look better. The image looks a tad bit more converged at default settings and there is significantly less ghosting.

#31
Posted 06/18/2010 07:27 PM   
I installed the 257.21 Display driver for my GTX 470 then the 3D vision driver 257.21, in that order now everything is broken. I wish I hadnt checked for updates. Serious Sam HD is all out of whack there are four revolvers where there are supposed to be two I,ve tried convergence, depth amount etc its all out of focus no matter what I do. Mass effect 2 exactly the same problem. Havent tried any Steam games yet but I,m assuming the worst. If anyone can recommend a fix otherwise I,m going back to the old drivers. If you have any advice please ratcat17@hotmail.com

[quote name='ratcat' post='1075812' date='Jun 19 2010, 03:15 PM']I installed the 257.21 Display driver for my GTX 470 then the 3D vision driver 257.21, in that order now everything is broken. I wish I hadnt checked for updates. Serious Sam HD is all out of whack there are four revolvers where there are supposed to be two I,ve tried convergence, depth amount etc its all out of focus no matter what I do. Mass effect 2 exactly the same problem. Havent tried any Steam games yet but I,m assuming the worst. If anyone can recommend a fix otherwise I,m going back to the old drivers. If you have any advice please ratcat17@hotmail.com[/quote]
I forgot to mention that its Windows Seven 64 bit. Maybe thats why I,m having problems

:lol: I dont know what I did, in the meantime I may have restarted my PC but now it it all working, all games and better than ever. Even SS2 HD had two cross hairs b4 now there is just one and I can add the stereoscopic 3D hair which sits in the centre of the ingame crosshair. The games all look even better somehow... clearer? crisper better defined? dont know but just looks great. Sorry nVidia for jumping up so fast. I wont need to go back to the 197.75 drivers after all.

[quote name='ratcat' post='1075825' date='Jun 19 2010, 04:24 PM']:lol: I dont know what I did, in the meantime I may have restarted my PC but now it it all working, all games and better than ever. Even SS2 HD had two cross hairs b4 now there is just one and I can add the stereoscopic 3D hair which sits in the centre of the ingame crosshair. The games all look even better somehow... clearer? crisper better defined? dont know but just looks great. Sorry nVidia for jumping up so fast. I wont need to go back to the 197.75 drivers after all.[/quote]
What the... Everything went back to haywire again. Then I played around with the in game graphics settings Alt -tabbed out and played with the control panel and got it working normally again but now the double cross hairs are back so I disabled them and just use the 3D crosshair but that dissapears from time to time as well. If I have to do this everytime its definetly back to the 197.75s unless someone out there has a solution
I installed the 257.21 Display driver for my GTX 470 then the 3D vision driver 257.21, in that order now everything is broken. I wish I hadnt checked for updates. Serious Sam HD is all out of whack there are four revolvers where there are supposed to be two I,ve tried convergence, depth amount etc its all out of focus no matter what I do. Mass effect 2 exactly the same problem. Havent tried any Steam games yet but I,m assuming the worst. If anyone can recommend a fix otherwise I,m going back to the old drivers. If you have any advice please ratcat17@hotmail.com



[quote name='ratcat' post='1075812' date='Jun 19 2010, 03:15 PM']I installed the 257.21 Display driver for my GTX 470 then the 3D vision driver 257.21, in that order now everything is broken. I wish I hadnt checked for updates. Serious Sam HD is all out of whack there are four revolvers where there are supposed to be two I,ve tried convergence, depth amount etc its all out of focus no matter what I do. Mass effect 2 exactly the same problem. Havent tried any Steam games yet but I,m assuming the worst. If anyone can recommend a fix otherwise I,m going back to the old drivers. If you have any advice please ratcat17@hotmail.com

I forgot to mention that its Windows Seven 64 bit. Maybe thats why I,m having problems



:lol: I dont know what I did, in the meantime I may have restarted my PC but now it it all working, all games and better than ever. Even SS2 HD had two cross hairs b4 now there is just one and I can add the stereoscopic 3D hair which sits in the centre of the ingame crosshair. The games all look even better somehow... clearer? crisper better defined? dont know but just looks great. Sorry nVidia for jumping up so fast. I wont need to go back to the 197.75 drivers after all.



[quote name='ratcat' post='1075825' date='Jun 19 2010, 04:24 PM']:lol: I dont know what I did, in the meantime I may have restarted my PC but now it it all working, all games and better than ever. Even SS2 HD had two cross hairs b4 now there is just one and I can add the stereoscopic 3D hair which sits in the centre of the ingame crosshair. The games all look even better somehow... clearer? crisper better defined? dont know but just looks great. Sorry nVidia for jumping up so fast. I wont need to go back to the 197.75 drivers after all.

What the... Everything went back to haywire again. Then I played around with the in game graphics settings Alt -tabbed out and played with the control panel and got it working normally again but now the double cross hairs are back so I disabled them and just use the 3D crosshair but that dissapears from time to time as well. If I have to do this everytime its definetly back to the 197.75s unless someone out there has a solution

#32
Posted 06/19/2010 05:15 AM   
Tried to install 1.29, everything went wrong. As always tried the classic process, uninstall nvidia drivers,, reboot, windows 7 automatically installs drivers, reboot, start cd app, install new drivers, install 3d vision, 3d test, done, that should be it.

However something's really wrong for me with those drivers. When installed the nvidia drivers and rebooted, windows wouldn't start and the screen was black with really weird flashes of different colors, blue, white, orange, pink, really weird, and loads nothing else. I did reboot and windows asked to repair, I did, tried the process a few more times, always with the same outcome, so I went back to 1.25 and everything was back to normal.

My specs:

Windows 7 32 bit
q6600
9800gtx+
4gb ram
Tried to install 1.29, everything went wrong. As always tried the classic process, uninstall nvidia drivers,, reboot, windows 7 automatically installs drivers, reboot, start cd app, install new drivers, install 3d vision, 3d test, done, that should be it.



However something's really wrong for me with those drivers. When installed the nvidia drivers and rebooted, windows wouldn't start and the screen was black with really weird flashes of different colors, blue, white, orange, pink, really weird, and loads nothing else. I did reboot and windows asked to repair, I did, tried the process a few more times, always with the same outcome, so I went back to 1.25 and everything was back to normal.



My specs:



Windows 7 32 bit

q6600

9800gtx+

4gb ram

#33
Posted 06/19/2010 08:37 AM   
[quote name='Hotpot' post='1075048' date='Jun 17 2010, 12:01 PM']Fallout 3 has issues with this driver. When you access the PIP Boy with stereoscopic sight activated and then close the PIP Boy, the stereoscopic sight is at the wrong depth. I have a 480GTX.[/quote]

This has been present since at least 191.07, my current driver. It is simple to reset, just hit esc and get back in.

I would like to move to a newer driver and see if the stutter problem is any better now. Some say it is better, and I would be willing to deal with a few messed up polygons if I could eliminate the stutter. It killed the game for me so the game sits half finished on my drive. Are any of the newer drivers better for Fallout 3?
[quote name='Hotpot' post='1075048' date='Jun 17 2010, 12:01 PM']Fallout 3 has issues with this driver. When you access the PIP Boy with stereoscopic sight activated and then close the PIP Boy, the stereoscopic sight is at the wrong depth. I have a 480GTX.



This has been present since at least 191.07, my current driver. It is simple to reset, just hit esc and get back in.



I would like to move to a newer driver and see if the stutter problem is any better now. Some say it is better, and I would be willing to deal with a few messed up polygons if I could eliminate the stutter. It killed the game for me so the game sits half finished on my drive. Are any of the newer drivers better for Fallout 3?

#34
Posted 06/19/2010 11:09 PM   
[quote name='DDuckMan' post='1076147' date='Jun 19 2010, 06:09 PM']This has been present since at least 191.07, my current driver. It is simple to reset, just hit esc and get back in.

I would like to move to a newer driver and see if the stutter problem is any better now. Some say it is better, and I would be willing to deal with a few messed up polygons if I could eliminate the stutter. It killed the game for me so the game sits half finished on my drive. Are any of the newer drivers better for Fallout 3?[/quote]

nVidia doesn't bother with "older" game fixes for 3D. Fallout 3 will remain broken while they focus on tweaking games that aren't being released for 3 months. Try playing Half-Life 2 or Gears of War with the 3Da cross-hair enabled, or try playing crysis at all in 3D and you'll see what I mean. Persistent bugs for a year with no acknowledgment, let alone fixes.
[quote name='DDuckMan' post='1076147' date='Jun 19 2010, 06:09 PM']This has been present since at least 191.07, my current driver. It is simple to reset, just hit esc and get back in.



I would like to move to a newer driver and see if the stutter problem is any better now. Some say it is better, and I would be willing to deal with a few messed up polygons if I could eliminate the stutter. It killed the game for me so the game sits half finished on my drive. Are any of the newer drivers better for Fallout 3?



nVidia doesn't bother with "older" game fixes for 3D. Fallout 3 will remain broken while they focus on tweaking games that aren't being released for 3 months. Try playing Half-Life 2 or Gears of War with the 3Da cross-hair enabled, or try playing crysis at all in 3D and you'll see what I mean. Persistent bugs for a year with no acknowledgment, let alone fixes.

PC: AMD FX 8350 | eVGA nVidia GTX 970 4GB | 16GB Corsair DDR3 | 300GB SSD HD | 750W Corsair PSU | Windows 10 64-bit | Dell 24" LED Gadgets: Playstation 4 500GB | Xbox One 500GB | Microsoft Surface Pro 128GB | Samsung Galaxy S6 128GB | Lenovo Y50 laptop w/ GTX860m

#35
Posted 06/20/2010 04:55 PM   
[quote name='Frag of Fury' post='1076448' date='Jun 20 2010, 10:55 AM']nVidia doesn't bother with "older" game fixes for 3D. Fallout 3 will remain broken while they focus on tweaking games that aren't being released for 3 months. Try playing Half-Life 2 or Gears of War with the 3Da cross-hair enabled, or try playing crysis at all in 3D and you'll see what I mean. Persistent bugs for a year with no acknowledgment, let alone fixes.[/quote]

Well, in any case, I went ahead and sent some driver feedback for Fallout 3 and the new 3d vision drivers. I suppose that has more a chance of helping as anything.
[quote name='Frag of Fury' post='1076448' date='Jun 20 2010, 10:55 AM']nVidia doesn't bother with "older" game fixes for 3D. Fallout 3 will remain broken while they focus on tweaking games that aren't being released for 3 months. Try playing Half-Life 2 or Gears of War with the 3Da cross-hair enabled, or try playing crysis at all in 3D and you'll see what I mean. Persistent bugs for a year with no acknowledgment, let alone fixes.



Well, in any case, I went ahead and sent some driver feedback for Fallout 3 and the new 3d vision drivers. I suppose that has more a chance of helping as anything.

The human race divides politically into those who want people to be controlled and those who have no such desire.

--Robert A. Heinlein

#36
Posted 06/20/2010 07:20 PM   
[quote name='Frag of Fury' post='1076448' date='Jun 20 2010, 12:55 PM']nVidia doesn't bother with "older" game fixes for 3D. Fallout 3 will remain broken while they focus on tweaking games that aren't being released for 3 months. Try playing Half-Life 2 or Gears of War with the 3Da cross-hair enabled, or try playing crysis at all in 3D and you'll see what I mean. Persistent bugs for a year with no acknowledgment, let alone fixes.[/quote]
There's only certain things Nvidia can fix on their end and others that are just limitations of the technology and the game engines themselves. We can't expect Nvidia to compensate for a game rendering objects or cross-hairs at the wrong depth, or to eliminate some of the post-process, frame buffer, or lighting effects that can ruin or severely detract from the 3D experience. Even their own cross-hair is a workaround and only works in games that allow their native crosshairs to be turned off. The best we can expect is that games fix these potential problems going forward with 3D Vision compatibility in the back of their minds or at the very least, expose all such settings that might be incompatible with 3D Vision so that we can disable them as needed.

What they can fix on their side are blatant performance or scaling problems and compatibility issues in certain games and hardware configurations.
[quote name='Frag of Fury' post='1076448' date='Jun 20 2010, 12:55 PM']nVidia doesn't bother with "older" game fixes for 3D. Fallout 3 will remain broken while they focus on tweaking games that aren't being released for 3 months. Try playing Half-Life 2 or Gears of War with the 3Da cross-hair enabled, or try playing crysis at all in 3D and you'll see what I mean. Persistent bugs for a year with no acknowledgment, let alone fixes.

There's only certain things Nvidia can fix on their end and others that are just limitations of the technology and the game engines themselves. We can't expect Nvidia to compensate for a game rendering objects or cross-hairs at the wrong depth, or to eliminate some of the post-process, frame buffer, or lighting effects that can ruin or severely detract from the 3D experience. Even their own cross-hair is a workaround and only works in games that allow their native crosshairs to be turned off. The best we can expect is that games fix these potential problems going forward with 3D Vision compatibility in the back of their minds or at the very least, expose all such settings that might be incompatible with 3D Vision so that we can disable them as needed.



What they can fix on their side are blatant performance or scaling problems and compatibility issues in certain games and hardware configurations.

-=HeliX=- Mod 3DV Game Fixes
My 3D Vision Games List Ratings

Intel Core i7 5930K @4.5GHz | Gigabyte X99 Gaming 5 | Win10 x64 Pro | Corsair H105
Nvidia GeForce Titan X SLI Hybrid | ROG Swift PG278Q 144Hz + 3D Vision/G-Sync | 32GB Adata DDR4 2666
Intel Samsung 950Pro SSD | Samsung EVO 4x1 RAID 0 |
Yamaha VX-677 A/V Receiver | Polk Audio RM6880 7.1 | LG Blu-Ray
Auzen X-Fi HT HD | Logitech G710/G502/G27 | Corsair Air 540 | EVGA P2-1200W

#37
Posted 06/20/2010 07:49 PM   
[quote name='chiz' post='1076523' date='Jun 20 2010, 01:49 PM']There's only certain things Nvidia can fix on their end and others that are just limitations of the technology and the game engines themselves. We can't expect Nvidia to compensate for a game rendering objects or cross-hairs at the wrong depth, or to eliminate some of the post-process, frame buffer, or lighting effects that can ruin or severely detract from the 3D experience. Even their own cross-hair is a workaround and only works in games that allow their native crosshairs to be turned off. The best we can expect is that games fix these potential problems going forward with 3D Vision compatibility in the back of their minds or at the very least, expose all such settings that might be incompatible with 3D Vision so that we can disable them as needed.

What they can fix on their side are blatant performance or scaling problems and compatibility issues in certain games and hardware configurations.[/quote]

The problem is that they are introducing bugs into games that worked fine previously. It has nothing to do with engine limitations at all. /confused.gif' class='bbc_emoticon' alt=':confused:' />
[quote name='chiz' post='1076523' date='Jun 20 2010, 01:49 PM']There's only certain things Nvidia can fix on their end and others that are just limitations of the technology and the game engines themselves. We can't expect Nvidia to compensate for a game rendering objects or cross-hairs at the wrong depth, or to eliminate some of the post-process, frame buffer, or lighting effects that can ruin or severely detract from the 3D experience. Even their own cross-hair is a workaround and only works in games that allow their native crosshairs to be turned off. The best we can expect is that games fix these potential problems going forward with 3D Vision compatibility in the back of their minds or at the very least, expose all such settings that might be incompatible with 3D Vision so that we can disable them as needed.



What they can fix on their side are blatant performance or scaling problems and compatibility issues in certain games and hardware configurations.



The problem is that they are introducing bugs into games that worked fine previously. It has nothing to do with engine limitations at all. /confused.gif' class='bbc_emoticon' alt=':confused:' />

The human race divides politically into those who want people to be controlled and those who have no such desire.

--Robert A. Heinlein

#38
Posted 06/23/2010 01:46 AM   
[quote name='pahncrd' post='1076640' date='Jun 22 2010, 09:46 PM']The problem is that they are introducing bugs into games that worked fine previously. It has nothing to do with engine limitations at all. /confused.gif' class='bbc_emoticon' alt=':confused:' />[/quote]
The problems Frag of Fury described are definitely game/engine limitations; Nvidia's driver cannot change the depth at which objects are rendered, it simply does as its told by the game engine. Crosshairs and objects/icons rendered at screen depth are always going to be an issue with 3D Vision until developers start rendering them at the corresponding object depth, plain and simple.

As for the problem you described, I was playing Fallout 3 earlier today without any of the problems you described with flashing polys, but that sounds like a problem adjusting frustrum could fix using F11. You get those flashing white polys when the driver thinks those objects are off-screen, I get similar problems with Neverwinter Nights 2 but cycling frustrum fixes it.
[quote name='pahncrd' post='1076640' date='Jun 22 2010, 09:46 PM']The problem is that they are introducing bugs into games that worked fine previously. It has nothing to do with engine limitations at all. /confused.gif' class='bbc_emoticon' alt=':confused:' />

The problems Frag of Fury described are definitely game/engine limitations; Nvidia's driver cannot change the depth at which objects are rendered, it simply does as its told by the game engine. Crosshairs and objects/icons rendered at screen depth are always going to be an issue with 3D Vision until developers start rendering them at the corresponding object depth, plain and simple.



As for the problem you described, I was playing Fallout 3 earlier today without any of the problems you described with flashing polys, but that sounds like a problem adjusting frustrum could fix using F11. You get those flashing white polys when the driver thinks those objects are off-screen, I get similar problems with Neverwinter Nights 2 but cycling frustrum fixes it.

-=HeliX=- Mod 3DV Game Fixes
My 3D Vision Games List Ratings

Intel Core i7 5930K @4.5GHz | Gigabyte X99 Gaming 5 | Win10 x64 Pro | Corsair H105
Nvidia GeForce Titan X SLI Hybrid | ROG Swift PG278Q 144Hz + 3D Vision/G-Sync | 32GB Adata DDR4 2666
Intel Samsung 950Pro SSD | Samsung EVO 4x1 RAID 0 |
Yamaha VX-677 A/V Receiver | Polk Audio RM6880 7.1 | LG Blu-Ray
Auzen X-Fi HT HD | Logitech G710/G502/G27 | Corsair Air 540 | EVGA P2-1200W

#39
Posted 06/23/2010 03:12 AM   
[quote name='chiz' post='1076677' date='Jun 22 2010, 09:12 PM']The problems Frag of Fury described are definitely game/engine limitations; Nvidia's driver cannot change the depth at which objects are rendered, it simply does as its told by the game engine. Crosshairs and objects/icons rendered at screen depth are always going to be an issue with 3D Vision until developers start rendering them at the corresponding object depth, plain and simple.

As for the problem you described, I was playing Fallout 3 earlier today without any of the problems you described with flashing polys, but that sounds like a problem adjusting frustrum could fix using F11. You get those flashing white polys when the driver thinks those objects are off-screen, I get similar problems with Neverwinter Nights 2 but cycling frustrum fixes it.[/quote]


It didn't fix my issues. Also, rolling back fixed the problem and then doing a clean install of 1.29 made it so I still had the issue. I mostly only have the issue in indoor cells though.

1.25 = No flashing polygons
1.27-1.29 = Flashing polygons

I'm not sure how it could be anything but a driver problem.

Plus I'm not the only one having the issue.


Also, I seriously doubt that the 3d reticle performance problems are from any engine limitations, though crysis certainly probably is. I seem to remember that the 3d crosshair used to work with the old 3d drivers in HL2 without issue, but I suppose it could be a false memory, after all it was years ago that i played through it in 3d.
[quote name='chiz' post='1076677' date='Jun 22 2010, 09:12 PM']The problems Frag of Fury described are definitely game/engine limitations; Nvidia's driver cannot change the depth at which objects are rendered, it simply does as its told by the game engine. Crosshairs and objects/icons rendered at screen depth are always going to be an issue with 3D Vision until developers start rendering them at the corresponding object depth, plain and simple.



As for the problem you described, I was playing Fallout 3 earlier today without any of the problems you described with flashing polys, but that sounds like a problem adjusting frustrum could fix using F11. You get those flashing white polys when the driver thinks those objects are off-screen, I get similar problems with Neverwinter Nights 2 but cycling frustrum fixes it.





It didn't fix my issues. Also, rolling back fixed the problem and then doing a clean install of 1.29 made it so I still had the issue. I mostly only have the issue in indoor cells though.



1.25 = No flashing polygons

1.27-1.29 = Flashing polygons



I'm not sure how it could be anything but a driver problem.



Plus I'm not the only one having the issue.





Also, I seriously doubt that the 3d reticle performance problems are from any engine limitations, though crysis certainly probably is. I seem to remember that the 3d crosshair used to work with the old 3d drivers in HL2 without issue, but I suppose it could be a false memory, after all it was years ago that i played through it in 3d.

The human race divides politically into those who want people to be controlled and those who have no such desire.

--Robert A. Heinlein

#40
Posted 06/23/2010 03:40 AM   
[quote name='chiz' post='1074141' date='Jun 15 2010, 10:30 PM']1) [b]SLI + 3D Vision lower performance with R257 compared to R197 drivers[/b]. Generally performance with the R257 drivers are better with 3DVision off, but worst with 3DVision On. Single GPU performance with 3D Vision is about the same in either driver release, the problem is mainly in SLI. Games where this is most noticeable are Assassin's Creed 2, Just Cause 2, BFBC2, Avatar, Metro 2033. All games listed exhibit low GPU utilization observed with Precision/AfterBurner despite FPS far below the 60FPS 3D Vision sync cap. Performance/GPU utilization also tends to be worst in DX10/11 compared to DX9 in games that support multiple API. I have cross-referenced some of the SLI flags in the 197 and 257 drivers and they are the same, so there's something going on with the newer drivers or the 3D Stereo driver causing performance to be worst. I plan to do a more thorough comparison when nHancer 2.6.0 is released that supports the 257 drivers but right now its just too tedious trying to switch and decipher using the GeForce SLI tool.

2) [b]Splinter Cell Conviction has no game profile.[/b] Adding the .exe and SLI flag: [b]Setting ID_0x1095def8 = 0x02500001[/b] enables SLI support, however, with 3D Vision On the result is a memory leak that results in rapid performance degredation. Please see this thread for details: [url="http://forums.nvidia.com/index.php?s=&showtopic=167838&view=findpost&p=1072536"]http://forums.nvidia.com/index.php?s=&...t&p=1072536[/url]

3) [b]3D Vision screenshots and convergence settings do not save properly [/b]if Users\%Username%\Documents folder is missing or moved in Folder properties. When using the Windows Folder Location to move the physical location of this folder/library, the 3D Vision app/driver does not properly follow the Windows junction as if the target location is hard-coded. Solution would be to allow the end-user to specify screenshot/setting location. Current workaround was to create a Junction using mklink /j.

4) [b]3D Stereo mode kicks in for some programs that do not function properly with 3D stereo, like Windows Media Center.[/b] Would be nice if we were able to enable/disable 3D Vision directly from Program Setting profiles instead of having to manually enable/disable 3D Vision globally.[/quote]

Generally agree with your observations.

Metro 2033
I cannot enable dx10 or dx11 with 3Dvision + SLI (either high or very high graphics settings), will not work, settings menu becomes corrupte and CTD.
DX9 very high actually running somewhat better than with 197 drivers but occasional incorrect rendering of light sources.


Bioshock 2
On older drivers with 2XGTX285s had excellent SLI scaling, performance in 3D vision.
On 197 drivers with 2xGTX480s SLI gave severe stutter with 3DVision, but single card worked pretty well (not quite as good as 2xGTX285s).
On 257 drivers 2xGTX480s SLI give crash to desktop before game actually starts. Haven't tried single card yet.


Just Cause 2
Performance worse with 257.21 vs 197. Actually ran better with 2xGTX285s SLI and older drivers! Benchmarks only running max 34fps with lowered quality settings. Sli utilization bar often low.
Game crashes unless 3DVision is activated at menu. (did not happen before)

Battlefield BC2
Significantly better performance with 275.21 drivers running in DX10 mode.
FPS generally 40-60 but much smoother than before.
Still seems to be poorly coded and cpu bottlenecked somewhat.
Also the game controller support does not work, pinnacle profiler required.


[color="#000000"][size=1]MOTHERBOARD: EVGA 780I SLI A2 P-06Bios
CPU: Intel 2 Core Quad QX9650 45nm(OC @ 3.83GHz FSB:1333 @ 1.3200V set in bios)prime95 all day
CPU Cooler: Gigabyte 3D Mercury case with integrated watercooling (cpu only at present)
RAM: 2x2GB OCZ PC8000 SLI (Timing:5-5-5-15-2T@ 2.0V, FSB:DRAM Ratio=2:3)
GRAPHICS: 2X EVGA GTX 480sc(clocks: /1007mem/1538shader, stock heatsink)
HDD1: 2X Western Digital Caviar SATA II 250GB 7200 rpm Raid 0
HDD2: Western Digital Caviar SATA II 500GB 7200 rpm
SOUND: On board
OS: Windows Vista Ultimate 64bit SP2
MONITOR: Dell 3008wfp 30" Native Res: 2560X1600 @ 60Hz, Acer235Hz120Hz-3D
PSU: Thermaltake Toughpower 1000W
CASE: Gigabyte 3D Mercury
3DMARK Vantage: 29,686p Current Display Driver:257.21, CDv1.29[/size][/color]
[quote name='chiz' post='1074141' date='Jun 15 2010, 10:30 PM']1) SLI + 3D Vision lower performance with R257 compared to R197 drivers. Generally performance with the R257 drivers are better with 3DVision off, but worst with 3DVision On. Single GPU performance with 3D Vision is about the same in either driver release, the problem is mainly in SLI. Games where this is most noticeable are Assassin's Creed 2, Just Cause 2, BFBC2, Avatar, Metro 2033. All games listed exhibit low GPU utilization observed with Precision/AfterBurner despite FPS far below the 60FPS 3D Vision sync cap. Performance/GPU utilization also tends to be worst in DX10/11 compared to DX9 in games that support multiple API. I have cross-referenced some of the SLI flags in the 197 and 257 drivers and they are the same, so there's something going on with the newer drivers or the 3D Stereo driver causing performance to be worst. I plan to do a more thorough comparison when nHancer 2.6.0 is released that supports the 257 drivers but right now its just too tedious trying to switch and decipher using the GeForce SLI tool.



2) Splinter Cell Conviction has no game profile. Adding the .exe and SLI flag: Setting ID_0x1095def8 = 0x02500001 enables SLI support, however, with 3D Vision On the result is a memory leak that results in rapid performance degredation. Please see this thread for details: http://forums.nvidia.com/index.php?s=&...t&p=1072536



3) 3D Vision screenshots and convergence settings do not save properly if Users\%Username%\Documents folder is missing or moved in Folder properties. When using the Windows Folder Location to move the physical location of this folder/library, the 3D Vision app/driver does not properly follow the Windows junction as if the target location is hard-coded. Solution would be to allow the end-user to specify screenshot/setting location. Current workaround was to create a Junction using mklink /j.



4) 3D Stereo mode kicks in for some programs that do not function properly with 3D stereo, like Windows Media Center. Would be nice if we were able to enable/disable 3D Vision directly from Program Setting profiles instead of having to manually enable/disable 3D Vision globally.



Generally agree with your observations.



Metro 2033

I cannot enable dx10 or dx11 with 3Dvision + SLI (either high or very high graphics settings), will not work, settings menu becomes corrupte and CTD.

DX9 very high actually running somewhat better than with 197 drivers but occasional incorrect rendering of light sources.





Bioshock 2

On older drivers with 2XGTX285s had excellent SLI scaling, performance in 3D vision.

On 197 drivers with 2xGTX480s SLI gave severe stutter with 3DVision, but single card worked pretty well (not quite as good as 2xGTX285s).

On 257 drivers 2xGTX480s SLI give crash to desktop before game actually starts. Haven't tried single card yet.





Just Cause 2

Performance worse with 257.21 vs 197. Actually ran better with 2xGTX285s SLI and older drivers! Benchmarks only running max 34fps with lowered quality settings. Sli utilization bar often low.

Game crashes unless 3DVision is activated at menu. (did not happen before)



Battlefield BC2

Significantly better performance with 275.21 drivers running in DX10 mode.

FPS generally 40-60 but much smoother than before.

Still seems to be poorly coded and cpu bottlenecked somewhat.

Also the game controller support does not work, pinnacle profiler required.





MOTHERBOARD: EVGA 780I SLI A2 P-06Bios

CPU: Intel 2 Core Quad QX9650 45nm(OC @ 3.83GHz FSB:1333 @ 1.3200V set in bios)prime95 all day

CPU Cooler: Gigabyte 3D Mercury case with integrated watercooling (cpu only at present)

RAM: 2x2GB OCZ PC8000 SLI (Timing:5-5-5-15-2T@ 2.0V, FSB:DRAM Ratio=2:3)

GRAPHICS: 2X EVGA GTX 480sc(clocks: /1007mem/1538shader, stock heatsink)

HDD1: 2X Western Digital Caviar SATA II 250GB 7200 rpm Raid 0

HDD2: Western Digital Caviar SATA II 500GB 7200 rpm

SOUND: On board

OS: Windows Vista Ultimate 64bit SP2

MONITOR: Dell 3008wfp 30" Native Res: 2560X1600 @ 60Hz, Acer235Hz120Hz-3D

PSU: Thermaltake Toughpower 1000W

CASE: Gigabyte 3D Mercury

3DMARK Vantage: 29,686p Current Display Driver:257.21, CDv1.29

#41
Posted 06/23/2010 12:59 PM   
I have the FO3 problems aswell, but these problems were also present for me on the last 3D Vision CD Drivers as well. To clairify I don't recall ever not having the crosshair issue. The artifacting is a new issue as of the last two cds but an easy fix.

First is the crosshair staying at a close depth after entering and leaving pipboy (or dialogue or terminals or anything that brings the crosshair really close to the screen other than just aiming at a wall). I find this a minor issue as I can quickly double tap escape to bring the escape menu up and then back down and the crosshair resets to the correct distance. One issue with this quick in game fix is that the distance that the crosshair is reset to as its maximum will be whatever you’re looking at so I find it usually best to look at the sky.

The artifacting that I see only occurs on the far right hand side of the screen any looking around and whatnot and I see white/grey polygons blinking over on that side. It has not effect on the game play but does break the immersion for me. However, I only have this artifacting when the 3d crosshair is disabled. As soon as I turn the 3d crosshair on the artifacting disappears and does not ever occur ever.
I have the FO3 problems aswell, but these problems were also present for me on the last 3D Vision CD Drivers as well. To clairify I don't recall ever not having the crosshair issue. The artifacting is a new issue as of the last two cds but an easy fix.



First is the crosshair staying at a close depth after entering and leaving pipboy (or dialogue or terminals or anything that brings the crosshair really close to the screen other than just aiming at a wall). I find this a minor issue as I can quickly double tap escape to bring the escape menu up and then back down and the crosshair resets to the correct distance. One issue with this quick in game fix is that the distance that the crosshair is reset to as its maximum will be whatever you’re looking at so I find it usually best to look at the sky.



The artifacting that I see only occurs on the far right hand side of the screen any looking around and whatnot and I see white/grey polygons blinking over on that side. It has not effect on the game play but does break the immersion for me. However, I only have this artifacting when the 3d crosshair is disabled. As soon as I turn the 3d crosshair on the artifacting disappears and does not ever occur ever.

#42
Posted 06/23/2010 05:10 PM   
[quote name='MistaP' post='1076970' date='Jun 23 2010, 07:10 PM']I have the FO3 problems aswell, but these problems were also present for me on the last 3D Vision CD Drivers as well. To clairify I don't recall ever not having the crosshair issue. The artifacting is a new issue as of the last two cds but an easy fix.

First is the crosshair staying at a close depth after entering and leaving pipboy (or dialogue or terminals or anything that brings the crosshair really close to the screen other than just aiming at a wall). I find this a minor issue as I can quickly double tap escape to bring the escape menu up and then back down and the crosshair resets to the correct distance. One issue with this quick in game fix is that the distance that the crosshair is reset to as its maximum will be whatever you’re looking at so I find it usually best to look at the sky.

The artifacting that I see only occurs on the far right hand side of the screen any looking around and whatnot and I see white/grey polygons blinking over on that side. It has not effect on the game play but does break the immersion for me. However, I only have this artifacting when the 3d crosshair is disabled. As soon as I turn the 3d crosshair on the artifacting disappears and does not ever occur ever.[/quote]

Metro 2033 runs slower with this new driver...
Id di run at +- 25 fps ,now it's back to 15 fps
Also the crossair is only located in the foreground. (like it used to do with Bioshock 2)
[quote name='MistaP' post='1076970' date='Jun 23 2010, 07:10 PM']I have the FO3 problems aswell, but these problems were also present for me on the last 3D Vision CD Drivers as well. To clairify I don't recall ever not having the crosshair issue. The artifacting is a new issue as of the last two cds but an easy fix.



First is the crosshair staying at a close depth after entering and leaving pipboy (or dialogue or terminals or anything that brings the crosshair really close to the screen other than just aiming at a wall). I find this a minor issue as I can quickly double tap escape to bring the escape menu up and then back down and the crosshair resets to the correct distance. One issue with this quick in game fix is that the distance that the crosshair is reset to as its maximum will be whatever you’re looking at so I find it usually best to look at the sky.



The artifacting that I see only occurs on the far right hand side of the screen any looking around and whatnot and I see white/grey polygons blinking over on that side. It has not effect on the game play but does break the immersion for me. However, I only have this artifacting when the 3d crosshair is disabled. As soon as I turn the 3d crosshair on the artifacting disappears and does not ever occur ever.



Metro 2033 runs slower with this new driver...

Id di run at +- 25 fps ,now it's back to 15 fps

Also the crossair is only located in the foreground. (like it used to do with Bioshock 2)

Intel I7 3820 3.8 Ghz,MSI MS7760 Motherboard, 6GB )2x MSI GTX670 (SLI),OCZ Vertex 230Gb SSD,OCZ Agility 120Gb SSD, Asus 3D VG278HR ,Optoma HD67 3D DLP Beamer with 95inch 2.5 gain screen.

#43
Posted 06/23/2010 05:31 PM   
[quote name='MistaP' post='1076970' date='Jun 23 2010, 11:10 AM']I have the FO3 problems aswell, but these problems were also present for me on the last 3D Vision CD Drivers as well. To clairify I don't recall ever not having the crosshair issue. The artifacting is a new issue as of the last two cds but an easy fix.

First is the crosshair staying at a close depth after entering and leaving pipboy (or dialogue or terminals or anything that brings the crosshair really close to the screen other than just aiming at a wall). I find this a minor issue as I can quickly double tap escape to bring the escape menu up and then back down and the crosshair resets to the correct distance. One issue with this quick in game fix is that the distance that the crosshair is reset to as its maximum will be whatever you’re looking at so I find it usually best to look at the sky.

The artifacting that I see only occurs on the far right hand side of the screen any looking around and whatnot and I see white/grey polygons blinking over on that side. It has not effect on the game play but does break the immersion for me. However, I only have this artifacting when the 3d crosshair is disabled. As soon as I turn the 3d crosshair on the artifacting disappears and does not ever occur ever.[/quote]

Hmm, that might be why that guy didn't see it.
[quote name='MistaP' post='1076970' date='Jun 23 2010, 11:10 AM']I have the FO3 problems aswell, but these problems were also present for me on the last 3D Vision CD Drivers as well. To clairify I don't recall ever not having the crosshair issue. The artifacting is a new issue as of the last two cds but an easy fix.



First is the crosshair staying at a close depth after entering and leaving pipboy (or dialogue or terminals or anything that brings the crosshair really close to the screen other than just aiming at a wall). I find this a minor issue as I can quickly double tap escape to bring the escape menu up and then back down and the crosshair resets to the correct distance. One issue with this quick in game fix is that the distance that the crosshair is reset to as its maximum will be whatever you’re looking at so I find it usually best to look at the sky.



The artifacting that I see only occurs on the far right hand side of the screen any looking around and whatnot and I see white/grey polygons blinking over on that side. It has not effect on the game play but does break the immersion for me. However, I only have this artifacting when the 3d crosshair is disabled. As soon as I turn the 3d crosshair on the artifacting disappears and does not ever occur ever.



Hmm, that might be why that guy didn't see it.

The human race divides politically into those who want people to be controlled and those who have no such desire.

--Robert A. Heinlein

#44
Posted 06/23/2010 06:03 PM   
[quote name='MistaP' post='1076970' date='Jun 23 2010, 01:10 PM']I have the FO3 problems aswell, but these problems were also present for me on the last 3D Vision CD Drivers as well. To clairify I don't recall ever not having the crosshair issue. The artifacting is a new issue as of the last two cds but an easy fix.

First is the crosshair staying at a close depth after entering and leaving pipboy (or dialogue or terminals or anything that brings the crosshair really close to the screen other than just aiming at a wall). I find this a minor issue as I can quickly double tap escape to bring the escape menu up and then back down and the crosshair resets to the correct distance. One issue with this quick in game fix is that the distance that the crosshair is reset to as its maximum will be whatever you’re looking at so I find it usually best to look at the sky.

The artifacting that I see only occurs on the far right hand side of the screen any looking around and whatnot and I see white/grey polygons blinking over on that side. It has not effect on the game play but does break the immersion for me. However, I only have this artifacting when the 3d crosshair is disabled. As soon as I turn the 3d crosshair on the artifacting disappears and does not ever occur ever.[/quote]

Have you had the video stutter problem with FO3? I just moved to 197.45 from 191.07 and they don't seem to be any better. Some said that the 197s fixed it for them.
[quote name='MistaP' post='1076970' date='Jun 23 2010, 01:10 PM']I have the FO3 problems aswell, but these problems were also present for me on the last 3D Vision CD Drivers as well. To clairify I don't recall ever not having the crosshair issue. The artifacting is a new issue as of the last two cds but an easy fix.



First is the crosshair staying at a close depth after entering and leaving pipboy (or dialogue or terminals or anything that brings the crosshair really close to the screen other than just aiming at a wall). I find this a minor issue as I can quickly double tap escape to bring the escape menu up and then back down and the crosshair resets to the correct distance. One issue with this quick in game fix is that the distance that the crosshair is reset to as its maximum will be whatever you’re looking at so I find it usually best to look at the sky.



The artifacting that I see only occurs on the far right hand side of the screen any looking around and whatnot and I see white/grey polygons blinking over on that side. It has not effect on the game play but does break the immersion for me. However, I only have this artifacting when the 3d crosshair is disabled. As soon as I turn the 3d crosshair on the artifacting disappears and does not ever occur ever.



Have you had the video stutter problem with FO3? I just moved to 197.45 from 191.07 and they don't seem to be any better. Some said that the 197s fixed it for them.

#45
Posted 06/23/2010 06:13 PM   
  3 / 5    
Scroll To Top