Where is the 196.21 3D Vision Full CD?
ETA PLZ!!!!!!!!!!!
ETA PLZ!!!!!!!!!!!

#1
Posted 01/22/2010 01:54 AM   
bump
bump

#2
Posted 01/22/2010 08:52 AM   
I assumed we were going to get them at some point today from Andrews responses.

[url="http://forums.nvidia.com/index.php?s=&showtopic=156807&view=findpost&p=985023"]http://forums.nvidia.com/index.php?s=&...st&p=985023[/url]

[url="http://forums.nvidia.com/index.php?s=&showtopic=156862&view=findpost&p=984991"]http://forums.nvidia.com/index.php?s=&...st&p=984991[/url]

So, later today... I hope
I assumed we were going to get them at some point today from Andrews responses.



http://forums.nvidia.com/index.php?s=&...st&p=985023



http://forums.nvidia.com/index.php?s=&...st&p=984991



So, later today... I hope

#3
Posted 01/22/2010 09:04 AM   
fingers crossed
fingers crossed

#4
Posted 01/22/2010 09:09 AM   
[url="http://www.nvidia.com/object/geforce_3D_vision_winvista_win7_CD_1.20.html"]http://www.nvidia.com/object/geforce_3D_vi...n7_CD_1.20.html[/url] /banana.gif' class='bbc_emoticon' alt=':banana:' />
http://www.nvidia.com/object/geforce_3D_vi...n7_CD_1.20.html /banana.gif' class='bbc_emoticon' alt=':banana:' />
Thankx for the heads up Fquillotine. First 3D package to install without hick-ups and hacks since 1.15, I followed Nvidia's quick install procedure to the letter - remove old driver/s reboot, install graphic driver reboot , install 3D Vision driver and run wizard and it actually worked!!!

EDIT Disregard above comment that 1.20 works properly, in actual fact while simplifing display detection as should have always been present this package appears to present another chapter of outright contempt for 3D Vision customers. Previously well demonstrated by Andrew replying to threads complaining about problems with a tone suggesting that he was unaware of the ongoing problems after attempted corrections despite numerous ongoing notifications that all was not well for many users. In the 1.20 offering Nvidia's sick sence of humour appears evident by Andrew's earlier teaser that this package would offer beta support for tri and quad SLI but this driver package does not allow enablement of at least Quad SLI (release notes detail that will enable but only show in control panel as SLI enabled). However, GPUZ and performance record only 2 gpu SLI (3 and 4 disabled). Great joke Nvidia, the only problems is while you seem to be getting a laugh out of your unbecoming incompetence and some users will pray to you for salvation, despite you causing their need for it, many others will not be laughing with you but instead are increasingly upset at you and the damage to Nvidia and their ongoing support and investment compounding the harm of the poor/paranoid marketplace management of Physx and 3D Vision. (This is based on the package obtained from the link in the preceding post, that is now thankfully already down)
Thankx for the heads up Fquillotine. First 3D package to install without hick-ups and hacks since 1.15, I followed Nvidia's quick install procedure to the letter - remove old driver/s reboot, install graphic driver reboot , install 3D Vision driver and run wizard and it actually worked!!!



EDIT Disregard above comment that 1.20 works properly, in actual fact while simplifing display detection as should have always been present this package appears to present another chapter of outright contempt for 3D Vision customers. Previously well demonstrated by Andrew replying to threads complaining about problems with a tone suggesting that he was unaware of the ongoing problems after attempted corrections despite numerous ongoing notifications that all was not well for many users. In the 1.20 offering Nvidia's sick sence of humour appears evident by Andrew's earlier teaser that this package would offer beta support for tri and quad SLI but this driver package does not allow enablement of at least Quad SLI (release notes detail that will enable but only show in control panel as SLI enabled). However, GPUZ and performance record only 2 gpu SLI (3 and 4 disabled). Great joke Nvidia, the only problems is while you seem to be getting a laugh out of your unbecoming incompetence and some users will pray to you for salvation, despite you causing their need for it, many others will not be laughing with you but instead are increasingly upset at you and the damage to Nvidia and their ongoing support and investment compounding the harm of the poor/paranoid marketplace management of Physx and 3D Vision. (This is based on the package obtained from the link in the preceding post, that is now thankfully already down)

EVGA X58 760 Classified (VREG,NB/SB WB Koolance seperate loop), i7 980X@4.4+GHz 33x134 1.3625V Thermaltake Venoumous S with CoolerMaster push-pull fans, 12GB OCZ 8-8-8-24@16000 1.65V, ATI 5970 WB Koolance on seperate loop @1.16V 850-1200 or Nvidia 295, Xonar HDAV 1.3 Deluxe into Yamaha RX-V3800, 4x300GB Velociraptors Raid 0 on Adaptec 4505 RAID, 4x60GB OCZ Vertex SSD RAID 0 LSI 9750, 1TB WD SATA3, 128GB Falcon SSD, Thermaltake 1200W, Thermaltake TX Mozart, Logitech diNovo Bluetooth Keyboard + MX1000 Mouse, Logitech Sphere MP webcam, Logitech cordless Rumblepad2, 50" Samsung 3D PS50B450 plasma, Samsung SSG1000 3D glasses, Nvidia 3D Vision, Windows 7 Ultimate x64 RTM

#6
Posted 01/22/2010 02:33 PM   
I really want to know how they killed my depth hack. /down.gif' class='bbc_emoticon' alt=':down:' /> The registry entries seem to be affected by something else, but they aren't able to dictate the depth anymore. It used to be that they would auto switch back to defaults whenever a game starts, but I was able to use a brute force batch file to still get the hack to apply as the game was loading. However, they have closed up that hack out of pure malice it seems, since it wasn't exactly widely used and wasn't hurting anyone. /censored.gif' class='bbc_emoticon' alt=':censored:' />

They were quick to rip control away from me... if only they were so fast at fixing bugs.
I really want to know how they killed my depth hack. /down.gif' class='bbc_emoticon' alt=':down:' /> The registry entries seem to be affected by something else, but they aren't able to dictate the depth anymore. It used to be that they would auto switch back to defaults whenever a game starts, but I was able to use a brute force batch file to still get the hack to apply as the game was loading. However, they have closed up that hack out of pure malice it seems, since it wasn't exactly widely used and wasn't hurting anyone. /censored.gif' class='bbc_emoticon' alt=':censored:' />



They were quick to rip control away from me... if only they were so fast at fixing bugs.

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

--Robert A. Heinlein

#7
Posted 01/22/2010 04:39 PM   
[quote name='pahncrd' post='986275' date='Jan 22 2010, 09:39 AM']I really want to know how they killed my depth hack. /down.gif' class='bbc_emoticon' alt=':down:' /> The registry entries seem to be affected by something else, but they aren't able to dictate the depth anymore. It used to be that they would auto switch back to defaults whenever a game starts, but I was able to use a brute force batch file to still get the hack to apply as the game was loading. However, they have closed up that hack out of pure malice it seems, since it wasn't exactly widely used and wasn't hurting anyone. /censored.gif' class='bbc_emoticon' alt=':censored:' />

They were quick to rip control away from me... if only they were so fast at fixing bugs.[/quote]
What is that depth hack?
[quote name='pahncrd' post='986275' date='Jan 22 2010, 09:39 AM']I really want to know how they killed my depth hack. /down.gif' class='bbc_emoticon' alt=':down:' /> The registry entries seem to be affected by something else, but they aren't able to dictate the depth anymore. It used to be that they would auto switch back to defaults whenever a game starts, but I was able to use a brute force batch file to still get the hack to apply as the game was loading. However, they have closed up that hack out of pure malice it seems, since it wasn't exactly widely used and wasn't hurting anyone. /censored.gif' class='bbc_emoticon' alt=':censored:' />



They were quick to rip control away from me... if only they were so fast at fixing bugs.

What is that depth hack?

*CPU: i7 920 DO @ 4.1Ghz 1.35v HT On*CPU Cooler: Thermaltake Water 2.0 Extreme*Mobo: Evga X58 SLI / RAM: 12GB Crucial Ballistix Tactical Tracer DDR3 1600 7-7-7-21 1.5v*Video Cards:Tri Sli Evga GTX 660 ti x 2 & MSI GTX 660 ti *Speakers:CBM-170 SE*PSU: Corsair HX1000W*Display: Mitusbishi 60" DLP (3D Vision ) Qnix QX2710 27" 1440P*Case: CoolerMaster HAF X (932 side) *Windows 7 64Bit on Samsung 840 256GB*Others: Roccat Kone XTD | Roccat Alumic | Logitech G15 | *Mobile: Galaxy Note 2

#8
Posted 01/22/2010 05:07 PM   
[quote name='shaolin95' post='986296' date='Jan 22 2010, 10:07 AM']What is that depth hack?[/quote]

[url="http://forums.nvidia.com/index.php?showtopic=105628"]http://forums.nvidia.com/index.php?showtopic=105628[/url]

You could also manually do it by alt tabbing out and changing the registry entry, but that only rarely worked well for me, hence the batch file.
[quote name='shaolin95' post='986296' date='Jan 22 2010, 10:07 AM']What is that depth hack?



http://forums.nvidia.com/index.php?showtopic=105628



You could also manually do it by alt tabbing out and changing the registry entry, but that only rarely worked well for me, hence the batch file.

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

--Robert A. Heinlein

#9
Posted 01/22/2010 05:10 PM   
[quote name='pahncrd' post='986275' date='Jan 22 2010, 11:39 AM']I really want to know how they killed my depth hack. /down.gif' class='bbc_emoticon' alt=':down:' /> The registry entries seem to be affected by something else, but they aren't able to dictate the depth anymore. It used to be that they would auto switch back to defaults whenever a game starts, but I was able to use a brute force batch file to still get the hack to apply as the game was loading. However, they have closed up that hack out of pure malice it seems, since it wasn't exactly widely used and wasn't hurting anyone. /censored.gif' class='bbc_emoticon' alt=':censored:' />

They were quick to rip control away from me... if only they were so fast at fixing bugs.[/quote]

What is your depth hack exactly and what did it do?
[quote name='pahncrd' post='986275' date='Jan 22 2010, 11:39 AM']I really want to know how they killed my depth hack. /down.gif' class='bbc_emoticon' alt=':down:' /> The registry entries seem to be affected by something else, but they aren't able to dictate the depth anymore. It used to be that they would auto switch back to defaults whenever a game starts, but I was able to use a brute force batch file to still get the hack to apply as the game was loading. However, they have closed up that hack out of pure malice it seems, since it wasn't exactly widely used and wasn't hurting anyone. /censored.gif' class='bbc_emoticon' alt=':censored:' />



They were quick to rip control away from me... if only they were so fast at fixing bugs.



What is your depth hack exactly and what did it do?

#10
Posted 01/23/2010 03:44 AM   
[quote name='andrewf@nvidia' post='986826' date='Jan 22 2010, 08:44 PM']What is your depth hack exactly and what did it do?[/quote]

The original depth hack was simply to change the monitorsize entry to something about half the size so that 50% on the depth scale would be equal to roughly 100% before the change, and of course it allowed me to go beyond 100% depth to about 120%-150% where I like to play.

The original hack was disabled as the monitorsize registry entry would reset itself as soon as I started a game. However, I could still alt-tab out and change the registry entry and upon re-entering the game, it would use the new setting giving me up to 200% depth. Unfortunately, alt-tabbing out of many games causes problems, especially games like Fallout 3 and Oblivion, which would always crash. Plus, it was a pain in the arse to always have to do that. So finally, I created a little batch file that would apply the altered registry entry over and over hopefully catching it after it defaulted but before the game actually started. This worked quite well and was much less of a hassle than alt-tabbing out and having to manually change it every time.

Now with the most recent drivers, none of those techniques work. In fact, the monitorsize entry doesn't seem to have any direct control whatsoever. It seems to be only dictated by the monitorid or displayid registry entries which cannot seem to be changed and cause problems if i try. Even if I could change them, there wouldn't be any point as there aren't any 120hz lcd monitors that have a display size lower than 22".

I have even gone so far as to make the monitorsize entry read only and while the setting stays correctly, it still has no impact on the perceived depth allowed and even at max depth.

There you have it. I have no idea why it was disabled, but it is annoying since I am used to playing at a higher depth than what is allowed.

I am probably a bit more pissy about it than I have a right to be, but little petty controls like this tend to be my pet peeve. It seems like a strange thing to bother disabling, as it doesn't hurt anyone and it doesn't have a huge following of people in the first place, since I would guess most people play nothing near 100%.
[quote name='andrewf@nvidia' post='986826' date='Jan 22 2010, 08:44 PM']What is your depth hack exactly and what did it do?



The original depth hack was simply to change the monitorsize entry to something about half the size so that 50% on the depth scale would be equal to roughly 100% before the change, and of course it allowed me to go beyond 100% depth to about 120%-150% where I like to play.



The original hack was disabled as the monitorsize registry entry would reset itself as soon as I started a game. However, I could still alt-tab out and change the registry entry and upon re-entering the game, it would use the new setting giving me up to 200% depth. Unfortunately, alt-tabbing out of many games causes problems, especially games like Fallout 3 and Oblivion, which would always crash. Plus, it was a pain in the arse to always have to do that. So finally, I created a little batch file that would apply the altered registry entry over and over hopefully catching it after it defaulted but before the game actually started. This worked quite well and was much less of a hassle than alt-tabbing out and having to manually change it every time.



Now with the most recent drivers, none of those techniques work. In fact, the monitorsize entry doesn't seem to have any direct control whatsoever. It seems to be only dictated by the monitorid or displayid registry entries which cannot seem to be changed and cause problems if i try. Even if I could change them, there wouldn't be any point as there aren't any 120hz lcd monitors that have a display size lower than 22".



I have even gone so far as to make the monitorsize entry read only and while the setting stays correctly, it still has no impact on the perceived depth allowed and even at max depth.



There you have it. I have no idea why it was disabled, but it is annoying since I am used to playing at a higher depth than what is allowed.



I am probably a bit more pissy about it than I have a right to be, but little petty controls like this tend to be my pet peeve. It seems like a strange thing to bother disabling, as it doesn't hurt anyone and it doesn't have a huge following of people in the first place, since I would guess most people play nothing near 100%.

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

--Robert A. Heinlein

#11
Posted 01/23/2010 06:05 PM   
Scroll To Top