BUG REPORT: CD 1.19 still NOT detects Samsung DLP 3rd botched release
  1 / 3    
One bug, all eyes, aim and miss?

At this point, even a comatose monkey must wake up out of frustration and question the competency of parties involved. Let's hear it. What's the real cause of this fiasco?
One bug, all eyes, aim and miss?



At this point, even a comatose monkey must wake up out of frustration and question the competency of parties involved. Let's hear it. What's the real cause of this fiasco?

Xeon X5675 hex cores @4.4 GHz, GTX 1070, win10 pro
i7 7700k 5GHz, RTX 2080, win10 pro
Benq 2720Z, w1070, Oculus Rift cv1, Samsung Odyssey+

#1
Posted 12/16/2009 04:02 PM   
Confirmed still not detecting

this is crazy , but at least ,well im assuming that nvidia actually wanted to fix the problem.. i guess they aren't capable of fixing their own software for their own product..


disappointing i guess ill wait for 2.0..
Confirmed still not detecting



this is crazy , but at least ,well im assuming that nvidia actually wanted to fix the problem.. i guess they aren't capable of fixing their own software for their own product..





disappointing i guess ill wait for 2.0..

intel i5 2500k @ 4.6 30C Stable

EVGA gtx 470 SLI

windows vista 64 bit

8 gig Corsair Vengeance RAM

#2
Posted 12/16/2009 04:08 PM   
Well, I guess it's good to know I'm not the only one. :unsure: At first, I thought I was doing something wrong. I was thinking the whole purpose of this driver was to fix the detection issues, so surely I must be doing something wrong. Guess not! But, it is good to know they are actively trying to fix the problem.
Well, I guess it's good to know I'm not the only one. :unsure: At first, I thought I was doing something wrong. I was thinking the whole purpose of this driver was to fix the detection issues, so surely I must be doing something wrong. Guess not! But, it is good to know they are actively trying to fix the problem.

#3
Posted 12/16/2009 04:12 PM   
i will check if my DLP crashes the setup if it makes it that far I will then try to finish the setup.

Will update here...
i will check if my DLP crashes the setup if it makes it that far I will then try to finish the setup.



Will update here...

#4
Posted 12/16/2009 04:18 PM   
Depressing news for sure. /sorcerer.gif' class='bbc_emoticon' alt=':sorcerer:' />
Depressing news for sure. /sorcerer.gif' class='bbc_emoticon' alt=':sorcerer:' />
I hope all of you are joking about 1.19. Especially in light of the fact I have been enjoying 195.81 since yesterday by using the following hack. I notified Nvidia about this success about 1 hour before Andrew appeared with his posts and also posted for members yersterday, Andrew did not say it did not work but advised to wait until 1.19, it works and 195.81 is much better than 195.39 (last working driver for me). It is absolutely dumbfounding that they could not package up a working solution, anyway if you want to use the new driver try the following (this technique did not work before 195.81 so Andrew was right about this driver enabling DLP / CRT).

WORKING 195.81 SOLUTION. Install 195.81 driver package for your OS (Geforce not 3D Vision), then install 3D Vision Sterioscopic driver from 1.15, during installation it will warn that it is incorrect for driver disregard and click OK, it will then suprisingly start to install the 1.15 package driver but request you to overwrite many newer files and then complete / finish. For me after this when starting Nvidia 3D test application it failed twice after briefly initiating (no hard lock or BSOD) then WORKED and has kept working !!!. At least in DAO and RE5 the result of 195.81 plus 1.15 Stereoscopic partially overwriting its poorly executed successor is a very clear improvement over the 1.15 package.
I hope all of you are joking about 1.19. Especially in light of the fact I have been enjoying 195.81 since yesterday by using the following hack. I notified Nvidia about this success about 1 hour before Andrew appeared with his posts and also posted for members yersterday, Andrew did not say it did not work but advised to wait until 1.19, it works and 195.81 is much better than 195.39 (last working driver for me). It is absolutely dumbfounding that they could not package up a working solution, anyway if you want to use the new driver try the following (this technique did not work before 195.81 so Andrew was right about this driver enabling DLP / CRT).



WORKING 195.81 SOLUTION. Install 195.81 driver package for your OS (Geforce not 3D Vision), then install 3D Vision Sterioscopic driver from 1.15, during installation it will warn that it is incorrect for driver disregard and click OK, it will then suprisingly start to install the 1.15 package driver but request you to overwrite many newer files and then complete / finish. For me after this when starting Nvidia 3D test application it failed twice after briefly initiating (no hard lock or BSOD) then WORKED and has kept working !!!. At least in DAO and RE5 the result of 195.81 plus 1.15 Stereoscopic partially overwriting its poorly executed successor is a very clear improvement over the 1.15 package.

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 12/16/2009 04:40 PM   
[quote name='MorSage' post='965836' date='Dec 16 2009, 11:40 AM']I hope all of you are joking about 1.19. Especially in light of the fact I have been enjoying 195.81 since yersterday by using the following hack. I notified Nvidia about this success about 1 hour before Andrew appeared with his posts and also posted for members yersterday, Andrew did not say it did not work but advised to wait until 1.19, it works and 195.81 is much better than 195.39 (last working driver for me). It is absolutely dumbfounding that they could not package up a working solution, anyway if you want to use the new driver try the following (this technique did not work before 195.81 so Andrew was right about this driver enabling DLP / CRT).

WORKING 195.81 SOLUTION. Install 195.81 driver package for your OS (Geforce not 3D Vision), then install 3D Vision Sterioscopic driver from 1.15, during installation it will warn that it is incorrect for driver disregard and click OK, it will then suprisingly start to install the 1.15 package driver but request you to overwrite many newer files and then complete / finish. For me after this when starting Nvidia 3D test application it failed twice after briefly initiating (no hard lock or BSOD) then WORKED and has kept working !!!. At least in DAO and RE5 the result of 195.81 plus 1.15 Stereoscopic partially overwriting its poorly executed successor is a very clear improvement over the 1.15 package.[/quote]

Hi All

3D Vision 195.81 and CD 1.19 (includes 3D Vision & GeForce 195.81 drivers) are now relesaed. This should address your CRT and Samsung DLP issues:
[list]
[*][url="http://www.nvidia.com/object/geforce_3D_vision_winvista_win7_CD_1.19.html"]CD 1.17[/url]
[*][url="http://www.nvidia.com/object/geforce_3D_vision_winvista_win7_195.81.html"]3D Vision 195.81[/url]
[/list]

Please let us know if your issues are now resolved.
[quote name='MorSage' post='965836' date='Dec 16 2009, 11:40 AM']I hope all of you are joking about 1.19. Especially in light of the fact I have been enjoying 195.81 since yersterday by using the following hack. I notified Nvidia about this success about 1 hour before Andrew appeared with his posts and also posted for members yersterday, Andrew did not say it did not work but advised to wait until 1.19, it works and 195.81 is much better than 195.39 (last working driver for me). It is absolutely dumbfounding that they could not package up a working solution, anyway if you want to use the new driver try the following (this technique did not work before 195.81 so Andrew was right about this driver enabling DLP / CRT).



WORKING 195.81 SOLUTION. Install 195.81 driver package for your OS (Geforce not 3D Vision), then install 3D Vision Sterioscopic driver from 1.15, during installation it will warn that it is incorrect for driver disregard and click OK, it will then suprisingly start to install the 1.15 package driver but request you to overwrite many newer files and then complete / finish. For me after this when starting Nvidia 3D test application it failed twice after briefly initiating (no hard lock or BSOD) then WORKED and has kept working !!!. At least in DAO and RE5 the result of 195.81 plus 1.15 Stereoscopic partially overwriting its poorly executed successor is a very clear improvement over the 1.15 package.



Hi All



3D Vision 195.81 and CD 1.19 (includes 3D Vision & GeForce 195.81 drivers) are now relesaed. This should address your CRT and Samsung DLP issues:





Please let us know if your issues are now resolved.

#7
Posted 12/16/2009 04:44 PM   
Just installed [url="http://www.nvidia.com/object/geforce_3D_vision_winvista_win7_195.81.html"]http://www.nvidia.com/object/geforce_3D_vi...in7_195.81.html[/url] as per Andrew's advice in preceding post but on top of the 195.81 Geforce drivers and it does work, seems you do not need my hack for 195.81 but it works.

What is very interesting though, after installing 3D VISION 195.81 when running the setup wizard it will not detect and only offers 3D Discover but if you close the application and check device manager all looks good and if you then reopen either the wizard or 3d test application it works (same quirk as my hack).
Just installed http://www.nvidia.com/object/geforce_3D_vi...in7_195.81.html as per Andrew's advice in preceding post but on top of the 195.81 Geforce drivers and it does work, seems you do not need my hack for 195.81 but it works.



What is very interesting though, after installing 3D VISION 195.81 when running the setup wizard it will not detect and only offers 3D Discover but if you close the application and check device manager all looks good and if you then reopen either the wizard or 3d test application it works (same quirk as my hack).

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

#8
Posted 12/16/2009 05:01 PM   
[quote name='MorSage' post='965854' date='Dec 16 2009, 12:01 PM']Just installed [url="http://www.nvidia.com/object/geforce_3D_vision_winvista_win7_195.81.html"]http://www.nvidia.com/object/geforce_3D_vi...in7_195.81.html[/url] as per Andrew's advice in preceding post but on top of the 195.81 Geforce drivers and it does work, seems you do not need my hack for 195.81 but it works.

What is very interesting though, after installing 3D VISION 195.81 when running the setup wizard it will not detect and only offers 3D Discover but if you close the application and check device manager all looks good and if you then reopen either the wizard or 3d test application it works (same quirk as my hack).[/quote]

Hi

Just so I understand your problem, when you run the wizard, what device is not detected? CRT or Samsung DLP?
[quote name='MorSage' post='965854' date='Dec 16 2009, 12:01 PM']Just installed http://www.nvidia.com/object/geforce_3D_vi...in7_195.81.html as per Andrew's advice in preceding post but on top of the 195.81 Geforce drivers and it does work, seems you do not need my hack for 195.81 but it works.



What is very interesting though, after installing 3D VISION 195.81 when running the setup wizard it will not detect and only offers 3D Discover but if you close the application and check device manager all looks good and if you then reopen either the wizard or 3d test application it works (same quirk as my hack).



Hi



Just so I understand your problem, when you run the wizard, what device is not detected? CRT or Samsung DLP?

#9
Posted 12/16/2009 06:09 PM   
After installing 195.81 the wizard will not precede unless 3D Discover is ticked (no other options). However, after closing wizard appearing in the install process (without ticking 3D Discover) the Nvidia control panel will now report all display type options being present, and if starting the wizard a second time (not included in install process) there is no problem and the 195.81 3D driver works. The hack I described yesterday does not have this exact weakness (wizard works in install process) but first time use a 3D application it fails, second time works, similar to the current driver (second application start needed) .
After installing 195.81 the wizard will not precede unless 3D Discover is ticked (no other options). However, after closing wizard appearing in the install process (without ticking 3D Discover) the Nvidia control panel will now report all display type options being present, and if starting the wizard a second time (not included in install process) there is no problem and the 195.81 3D driver works. The hack I described yesterday does not have this exact weakness (wizard works in install process) but first time use a 3D application it fails, second time works, similar to the current driver (second application start needed) .

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

#10
Posted 12/16/2009 06:51 PM   
Finally after the 3rd attempt I figured out the cause for not detecting DLP - at least for my system: When new driver installed, it sets the DLP TV resolution and refresh frequency to a NON COMPATIBLE selection, ie 1080p, 1758x992 by 29Hz. By selecting manually the correct resolution and fcy ie 1080p, 1920x1080 @60Hz (native), the wizard immediately recognizes the DLP TV.

Hope this clears up for some of you but I still have a nagging suspicion that a similar thing happened with the previous 2 releases as well.

Bottom line, the CD 1.19Beta works for Samsung DLP with some user flexibility. Not totally desirable but it's a step in the right direction.
Finally after the 3rd attempt I figured out the cause for not detecting DLP - at least for my system: When new driver installed, it sets the DLP TV resolution and refresh frequency to a NON COMPATIBLE selection, ie 1080p, 1758x992 by 29Hz. By selecting manually the correct resolution and fcy ie 1080p, 1920x1080 @60Hz (native), the wizard immediately recognizes the DLP TV.



Hope this clears up for some of you but I still have a nagging suspicion that a similar thing happened with the previous 2 releases as well.



Bottom line, the CD 1.19Beta works for Samsung DLP with some user flexibility. Not totally desirable but it's a step in the right direction.

Xeon X5675 hex cores @4.4 GHz, GTX 1070, win10 pro
i7 7700k 5GHz, RTX 2080, win10 pro
Benq 2720Z, w1070, Oculus Rift cv1, Samsung Odyssey+

#11
Posted 12/16/2009 07:07 PM   
Sadly my "solution" worked only once. After a reboot, it's back to the old problem: my Sammy is now NOT detected.

I must give up for now, life has other priorities.
Sadly my "solution" worked only once. After a reboot, it's back to the old problem: my Sammy is now NOT detected.



I must give up for now, life has other priorities.

Xeon X5675 hex cores @4.4 GHz, GTX 1070, win10 pro
i7 7700k 5GHz, RTX 2080, win10 pro
Benq 2720Z, w1070, Oculus Rift cv1, Samsung Odyssey+

#12
Posted 12/16/2009 07:38 PM   
tried changing my resolution to pc resolution but it wont let me put it at 60 hz so its a no go

i think the problem is the driver is outputting it at the hdtv res and not the pc res and maybe thats why its not detected?

theyve fixed it before..
tried changing my resolution to pc resolution but it wont let me put it at 60 hz so its a no go



i think the problem is the driver is outputting it at the hdtv res and not the pc res and maybe thats why its not detected?



theyve fixed it before..

intel i5 2500k @ 4.6 30C Stable

EVGA gtx 470 SLI

windows vista 64 bit

8 gig Corsair Vengeance RAM

#13
Posted 12/16/2009 08:53 PM   
Hi

I installed drivers for 3d vision by a device manager and everything works as expected :]
Hi



I installed drivers for 3d vision by a device manager and everything works as expected :]

Samsung 3D-Ready PLASMA PS50B450

#14
Posted 12/16/2009 10:14 PM   
OK I'm back for more pain.

My Dell LCD (not compatible with 3DVision) and my Sammy both connected to the PC, and while the Sammy was NOT detected as a 3D ready display, the 24" Dell actually got detected, and as a result under the "stereoscopic setup" panel it got all 3 choices Discover, DLP and CRT. Wonderful.

NOT.

I want my Sammy got detected, not the stupid Dell. What can I do with the dumb 60Hz Dell? In CRT mode it almost poked my eyes out and in DLP mode it just sit there like a stiff hinge.

Let's hope Andrew and the driver team will continue to work on resolving this issue.
OK I'm back for more pain.



My Dell LCD (not compatible with 3DVision) and my Sammy both connected to the PC, and while the Sammy was NOT detected as a 3D ready display, the 24" Dell actually got detected, and as a result under the "stereoscopic setup" panel it got all 3 choices Discover, DLP and CRT. Wonderful.



NOT.



I want my Sammy got detected, not the stupid Dell. What can I do with the dumb 60Hz Dell? In CRT mode it almost poked my eyes out and in DLP mode it just sit there like a stiff hinge.



Let's hope Andrew and the driver team will continue to work on resolving this issue.

Xeon X5675 hex cores @4.4 GHz, GTX 1070, win10 pro
i7 7700k 5GHz, RTX 2080, win10 pro
Benq 2720Z, w1070, Oculus Rift cv1, Samsung Odyssey+

#15
Posted 12/16/2009 10:16 PM   
  1 / 3    
Scroll To Top