[quote name='dreamingawake' post='967281' date='Dec 19 2009, 09:44 AM']Okay, doesn't work here either. Samsumg PN50B450 50" Plasma.. 3d display not detected..[/quote]
I have the same TV as you and the new drivers work great with the proviso that I never installed the 1.19 package I installed the Geforce 195.81 package and then the 3D Stereoscopic driver from the 1.15 package (full process described in 1.19 bug thread) this got the driver working before even 1.19 was released with the quirk that upon completion it did not work until initiating a 3d application twice the first time after that perfect.
After 1.19 was released I tried to upgrade using only the 3D Stereoscopic driver added to the already installed 195.81 Geforce driver, result 3D discover only, however exiting install after driver installed but display not set up and going to Nvidia control panel found DLP etc in drop down menu and could setup display normally.
Moral of the story I do not know if 1.19 package works, but do know that clean installed (driver sweeper safe mode + manual remove all nvidia corporation folders after stopping nvidia processes for all users in task manager + removing all nvidia related registry entries in both software and wow64 folder in all sections where listed) 195.81 + 1.15 3D driver (only) overwriting some files installed in the 195.81 geforce drivers do work and after this installing the 195.81 3d driver (17mb) also works and exceptionally well (less convergence / lighting issues). Both of these solutions appear to fail like the previous drivers but in reality do not, first detects display and allows display setup but applications fail a couple of times before everything perfectly Ok afterwards (no re-installing!), second will not detect display during installation but will after closing installation and enabling 3d through nvidia control panel where you will be able to select DLP.
BOTTOM LINE: 1.95.81 WORKS BUT NVIDIA HAS MESSED UP FOR THE THIRD CONSECUTIVE TIME BUT LESS SERIOUSLY THAN THE FIRST 2 TIMES.
[quote name='dreamingawake' post='967281' date='Dec 19 2009, 09:44 AM']Okay, doesn't work here either. Samsumg PN50B450 50" Plasma.. 3d display not detected..
I have the same TV as you and the new drivers work great with the proviso that I never installed the 1.19 package I installed the Geforce 195.81 package and then the 3D Stereoscopic driver from the 1.15 package (full process described in 1.19 bug thread) this got the driver working before even 1.19 was released with the quirk that upon completion it did not work until initiating a 3d application twice the first time after that perfect.
After 1.19 was released I tried to upgrade using only the 3D Stereoscopic driver added to the already installed 195.81 Geforce driver, result 3D discover only, however exiting install after driver installed but display not set up and going to Nvidia control panel found DLP etc in drop down menu and could setup display normally.
Moral of the story I do not know if 1.19 package works, but do know that clean installed (driver sweeper safe mode + manual remove all nvidia corporation folders after stopping nvidia processes for all users in task manager + removing all nvidia related registry entries in both software and wow64 folder in all sections where listed) 195.81 + 1.15 3D driver (only) overwriting some files installed in the 195.81 geforce drivers do work and after this installing the 195.81 3d driver (17mb) also works and exceptionally well (less convergence / lighting issues). Both of these solutions appear to fail like the previous drivers but in reality do not, first detects display and allows display setup but applications fail a couple of times before everything perfectly Ok afterwards (no re-installing!), second will not detect display during installation but will after closing installation and enabling 3d through nvidia control panel where you will be able to select DLP.
BOTTOM LINE: 1.95.81 WORKS BUT NVIDIA HAS MESSED UP FOR THE THIRD CONSECUTIVE TIME BUT LESS SERIOUSLY THAN THE FIRST 2 TIMES.
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
[quote name='turls' post='967072' date='Dec 18 2009, 01:22 PM']Andrew, are you here today?
I've confirmed there is no detection of Generic DLP (Saumsung HL61A750) using the following steps with the newest 1.19 CD:
Again this is not a hardware issue because the hardware works with 1.15. The emitter is blinking red when it is supposed to be and glowing green when it is supposed to be. Of course never bright green, because we never get the choice of Generic DLP to choose.[/quote]
I also have this television and it works fantastic in 3D.
Please fix this issue.... I miss my 3D :( (with up to date drivers)
Can't even play Avatar now :(
After the avatar update my game will lag now with even the 1.15 driver
[quote name='turls' post='967072' date='Dec 18 2009, 01:22 PM']Andrew, are you here today?
I've confirmed there is no detection of Generic DLP (Saumsung HL61A750) using the following steps with the newest 1.19 CD:
Again this is not a hardware issue because the hardware works with 1.15. The emitter is blinking red when it is supposed to be and glowing green when it is supposed to be. Of course never bright green, because we never get the choice of Generic DLP to choose.
I also have this television and it works fantastic in 3D.
Please fix this issue.... I miss my 3D :( (with up to date drivers)
Can't even play Avatar now :(
After the avatar update my game will lag now with even the 1.15 driver
[quote name='MorSage' post='967301' date='Dec 19 2009, 06:17 AM']I have the same TV as you and the new drivers work great with the proviso that I never installed the 1.19 package I installed the Geforce 195.81 package and then the 3D Stereoscopic driver from the 1.15 package (full process described in 1.19 bug thread) this got the driver working before even 1.19 was released with the quirk that upon completion it did not work until initiating a 3d application twice the first time after that perfect.
After 1.19 was released I tried to upgrade using only the 3D Stereoscopic driver added to the already installed 195.81 Geforce driver, result 3D discover only, however exiting install after driver installed but display not set up and going to Nvidia control panel found DLP etc in drop down menu and could setup display normally.
Moral of the story I do not know if 1.19 package works, but do know that clean installed (driver sweeper safe mode + manual remove all nvidia corporation folders after stopping nvidia processes for all users in task manager + removing all nvidia related registry entries in both software and wow64 folder in all sections where listed) 195.81 + 1.15 3D driver (only) overwriting some files installed in the 195.81 geforce drivers do work and after this installing the 195.81 3d driver (17mb) also works and exceptionally well (less convergence / lighting issues). Both of these solutions appear to fail like the previous drivers but in reality do not, first detects display and allows display setup but applications fail a couple of times before everything perfectly Ok afterwards (no re-installing!), second will not detect display during installation but will after closing installation and enabling 3d through nvidia control panel where you will be able to select DLP.
BOTTOM LINE: 1.95.81 WORKS BUT NVIDIA HAS MESSED UP FOR THE THIRD CONSECUTIVE TIME BUT LESS SERIOUSLY THAN THE FIRST 2 TIMES.[/quote]
I agree 1.19 works grate with SAMSUNG PLASMA PS50B450(vesa cable)... detect as a generic DLP
[quote name='MorSage' post='967301' date='Dec 19 2009, 06:17 AM']I have the same TV as you and the new drivers work great with the proviso that I never installed the 1.19 package I installed the Geforce 195.81 package and then the 3D Stereoscopic driver from the 1.15 package (full process described in 1.19 bug thread) this got the driver working before even 1.19 was released with the quirk that upon completion it did not work until initiating a 3d application twice the first time after that perfect.
After 1.19 was released I tried to upgrade using only the 3D Stereoscopic driver added to the already installed 195.81 Geforce driver, result 3D discover only, however exiting install after driver installed but display not set up and going to Nvidia control panel found DLP etc in drop down menu and could setup display normally.
Moral of the story I do not know if 1.19 package works, but do know that clean installed (driver sweeper safe mode + manual remove all nvidia corporation folders after stopping nvidia processes for all users in task manager + removing all nvidia related registry entries in both software and wow64 folder in all sections where listed) 195.81 + 1.15 3D driver (only) overwriting some files installed in the 195.81 geforce drivers do work and after this installing the 195.81 3d driver (17mb) also works and exceptionally well (less convergence / lighting issues). Both of these solutions appear to fail like the previous drivers but in reality do not, first detects display and allows display setup but applications fail a couple of times before everything perfectly Ok afterwards (no re-installing!), second will not detect display during installation but will after closing installation and enabling 3d through nvidia control panel where you will be able to select DLP.
BOTTOM LINE: 1.95.81 WORKS BUT NVIDIA HAS MESSED UP FOR THE THIRD CONSECUTIVE TIME BUT LESS SERIOUSLY THAN THE FIRST 2 TIMES.
I agree 1.19 works grate with SAMSUNG PLASMA PS50B450(vesa cable)... detect as a generic DLP
So... I just got the test application to work on my HL61A750 using 1.19 only just by running the wizard on my Samsung Syncmaster 245BW, picking answers I know are right, then switching my primary monitor back to the HL61A750.
I don't know how, but it seems the only time the Wizard [u][b]won't[/b][/u] let you run it to completion is when your 3D-Ready DLP is your primary monitor.
Almost like there's a '!' in the code somewhere that shouldn't be. The behaviour is the exact opposite of what it should be.
So... I just got the test application to work on my HL61A750 using 1.19 only just by running the wizard on my Samsung Syncmaster 245BW, picking answers I know are right, then switching my primary monitor back to the HL61A750.
I don't know how, but it seems the only time the Wizard won't let you run it to completion is when your 3D-Ready DLP is your primary monitor.
Almost like there's a '!' in the code somewhere that shouldn't be. The behaviour is the exact opposite of what it should be.
[quote name='Dr Nick' post='967212' date='Dec 18 2009, 05:24 PM']Keep in mind that these DLP's are working for NVIDIA, just not for you guys... Hopefully, there will be an easy fix :P
[i]Andrew, if you're reading this, please check your PM's :) [/i][/quote]
They supposedly have DLP working, but have not specified that they have it working on the top of the line finale never to be repeated or duplicated LED DLP TVs ;)
Not all DLPs are equal--unfortunately Samsung dropped DLP and Nvidia hitched their wagon to inferior tech Mits (LaserVue being the exception).
They have it working on a Mits, an earlier Samsung, or a projector, but not Samsung LED DLP, at least not the HL series.
[quote name='Dr Nick' post='967212' date='Dec 18 2009, 05:24 PM']Keep in mind that these DLP's are working for NVIDIA, just not for you guys... Hopefully, there will be an easy fix :P
Andrew, if you're reading this, please check your PM's :)
They supposedly have DLP working, but have not specified that they have it working on the top of the line finale never to be repeated or duplicated LED DLP TVs ;)
Not all DLPs are equal--unfortunately Samsung dropped DLP and Nvidia hitched their wagon to inferior tech Mits (LaserVue being the exception).
They have it working on a Mits, an earlier Samsung, or a projector, but not Samsung LED DLP, at least not the HL series.
Let me explain my situation to solve my problem that many of you are having and forced into discover mode.
I run the Wizard and on the step where it asks me to plug in the emitter, if I have it already plugged in, the SW fails and its forcing into discover mode (I actually think that is where our issue is).
If I unplug and replug it back in, I can then select Generic DLP mode.
There isnt a lot more I can today, as its the weekend, and the engs are hopefully getting some rest.
Let me explain my situation to solve my problem that many of you are having and forced into discover mode.
I run the Wizard and on the step where it asks me to plug in the emitter, if I have it already plugged in, the SW fails and its forcing into discover mode (I actually think that is where our issue is).
If I unplug and replug it back in, I can then select Generic DLP mode.
There isnt a lot more I can today, as its the weekend, and the engs are hopefully getting some rest.
When it comes to that step, I've always unplugged the emitter then replugged it in. It didn't make any difference in my case, time and time again, I even unplugged it before running the wizard and only plugged it in when it asked for, the Sammy was never detected.
I mentioned it before but will repeated here just in case it could shed any kind of light to the situation:
My Dell lcd monitor is not compatible with 3DVision but got detected as any of the 3 choices, DLP, CRT or Discover and after running the wizard, in the drop down menu all these 3 options are available. Ironically my Sammy DLP which is fully capable of S3D and had been working with 3D Vision couldn't be detected by the past 3 releases 1.16, 1.17 and 1.19CD. This is the opposite of what it should be, and another poster cited similar case with his system in one of the threads as well.
[quote]Let me explain my situation to solve my problem that many of you are having and forced into discover mode.
I run the Wizard and on the step where it asks me to plug in the emitter, if I have it already plugged in, the SW fails and its forcing into discover mode (I actually think that is where our issue is).
If I unplug and replug it back in, I can then select Generic DLP mode.[/quote]
When it comes to that step, I've always unplugged the emitter then replugged it in. It didn't make any difference in my case, time and time again, I even unplugged it before running the wizard and only plugged it in when it asked for, the Sammy was never detected.
I mentioned it before but will repeated here just in case it could shed any kind of light to the situation:
My Dell lcd monitor is not compatible with 3DVision but got detected as any of the 3 choices, DLP, CRT or Discover and after running the wizard, in the drop down menu all these 3 options are available. Ironically my Sammy DLP which is fully capable of S3D and had been working with 3D Vision couldn't be detected by the past 3 releases 1.16, 1.17 and 1.19CD. This is the opposite of what it should be, and another poster cited similar case with his system in one of the threads as well.
Let me explain my situation to solve my problem that many of you are having and forced into discover mode.
I run the Wizard and on the step where it asks me to plug in the emitter, if I have it already plugged in, the SW fails and its forcing into discover mode (I actually think that is where our issue is).
If I unplug and replug it back in, I can then select Generic DLP mode.
I was getting all sorts of errors with my CRT being detected, and this is how I fixed it... (after reading these last two posts its got me thinking it might work for DLP's too...)
In the start menu, click on devices and printers. You should see your "NVIDIA stereo controller". Right Click it and select "Properties". Navigate to the "Hardware" tab, and click "Properties" again. Go into the "Driver" tab and click on the "Update Driver..." button. You will get two options, click on "Search automatically for updated driver software".
You may have to have Windows Update enabled for this to work.
I'm not sure why this worked exactly, but I think there may be a problem with the NVIDIA stereo controller driver in the 1.19 CD drivers, so it doesn't detect it correctly... Has anyone tried this driver with a 2233RZ or other supported monitor? Probably not... Which is why this error has only been reported for DLP's.
As soon as I installed the driver that windows found for me, the setup wizard detected everything perfectly.
I'm not sure if this will fix the problem you guys' are having, but I sure hope so...
Nick
I was getting all sorts of errors with my CRT being detected, and this is how I fixed it... (after reading these last two posts its got me thinking it might work for DLP's too...)
In the start menu, click on devices and printers. You should see your "NVIDIA stereo controller". Right Click it and select "Properties". Navigate to the "Hardware" tab, and click "Properties" again. Go into the "Driver" tab and click on the "Update Driver..." button. You will get two options, click on "Search automatically for updated driver software".
You may have to have Windows Update enabled for this to work.
I'm not sure why this worked exactly, but I think there may be a problem with the NVIDIA stereo controller driver in the 1.19 CD drivers, so it doesn't detect it correctly... Has anyone tried this driver with a 2233RZ or other supported monitor? Probably not... Which is why this error has only been reported for DLP's.
As soon as I installed the driver that windows found for me, the setup wizard detected everything perfectly.
I'm not sure if this will fix the problem you guys' are having, but I sure hope so...
Nick
Twitter: @Dr_Inkduff
<b>Processor:</b> Intel Core i7 920 D0 (4Ghz) <b>Motherboard:</b> ASUS P6T
[quote name='Dr Nick' post='967729' date='Dec 19 2009, 11:29 PM']OK guys... Hopefully I have solution.
I was getting all sorts of errors with my CRT being detected, and this is how I fixed it... (after reading these last two posts its got me thinking it might work for DLP's too...)
In the start menu, click on devices and printers. You should see your "NVIDIA stereo controller". Right Click it and select "Properties". Navigate to the "Hardware" tab, and click "Properties" again. Go into the "Driver" tab and click on the "Update Driver..." button. You will get two options, click on "Search automatically for updated driver software".
You may have to have Windows Update enabled for this to work.
I'm not sure why this worked exactly, but I think there may be a problem with the NVIDIA stereo controller driver in the 1.19 CD drivers, so it doesn't detect it correctly... Has anyone tried this driver with a 2233RZ or other supported monitor? Probably not... Which is why this error has only been reported for DLP's.
As soon as I installed the driver that windows found for me, the setup wizard detected everything perfectly.
I'm not sure if this will fix the problem you guys' are having, but I sure hope so...
Nick[/quote]
Can you confirm that driver is the lastest one...195.8-something?
No use if the driver is an old version. When I installed Nvidia Geforce drivers like this, Windows found an old version to install automatically...
[quote name='Dr Nick' post='967729' date='Dec 19 2009, 11:29 PM']OK guys... Hopefully I have solution.
I was getting all sorts of errors with my CRT being detected, and this is how I fixed it... (after reading these last two posts its got me thinking it might work for DLP's too...)
In the start menu, click on devices and printers. You should see your "NVIDIA stereo controller". Right Click it and select "Properties". Navigate to the "Hardware" tab, and click "Properties" again. Go into the "Driver" tab and click on the "Update Driver..." button. You will get two options, click on "Search automatically for updated driver software".
You may have to have Windows Update enabled for this to work.
I'm not sure why this worked exactly, but I think there may be a problem with the NVIDIA stereo controller driver in the 1.19 CD drivers, so it doesn't detect it correctly... Has anyone tried this driver with a 2233RZ or other supported monitor? Probably not... Which is why this error has only been reported for DLP's.
As soon as I installed the driver that windows found for me, the setup wizard detected everything perfectly.
I'm not sure if this will fix the problem you guys' are having, but I sure hope so...
Nick
Can you confirm that driver is the lastest one...195.8-something?
No use if the driver is an old version. When I installed Nvidia Geforce drivers like this, Windows found an old version to install automatically...
Chock me up as another Samsung DLP user with issues. I also have an LED set model # HL-67A750. Works fine with Geforce 195.39, anything newer than that has issues and doesn't detect the set.
BTW Andrew I have a GTX 295 and plan on getting Fermi, will 3Dvision work with Fermi SLI just like the 295? It may be too soon to ask that, but I was wondering if 2 x GTX 295s > 2 X Fermi.
Chock me up as another Samsung DLP user with issues. I also have an LED set model # HL-67A750. Works fine with Geforce 195.39, anything newer than that has issues and doesn't detect the set.
BTW Andrew I have a GTX 295 and plan on getting Fermi, will 3Dvision work with Fermi SLI just like the 295? It may be too soon to ask that, but I was wondering if 2 x GTX 295s > 2 X Fermi.
[quote name='andrewf@nvidia' post='967679' date='Dec 19 2009, 07:36 PM']Hi All
Let me explain my situation to solve my problem that many of you are having and forced into discover mode.
I run the Wizard and on the step where it asks me to plug in the emitter, if I have it already plugged in, the SW fails and its forcing into discover mode (I actually think that is where our issue is).
If I unplug and replug it back in, I can then select Generic DLP mode.
There isnt a lot more I can today, as its the weekend, and the engs are hopefully getting some rest.[/quote]
I appreciate your continued presence here, and your responses. But [b]please[/b] have the engineers look at our responses over the last few days so we don't get more "this is what you are doing wrong" solutions and close the book before Christmas/New Years on this. It is most definitely not anything to do with how we are installing the drivers, plugging in the emitter, hardware, etc. Between all of us we have tried every different way of installing these drivers imaginable. And even if that was the case, there is absolutely something that has changed in the detection routines since 1.15 [i]for the worse[/i]. [b]That is what the engineers need to concentrate on.[/b]
[quote name='andrewf@nvidia' post='967679' date='Dec 19 2009, 07:36 PM']Hi All
Let me explain my situation to solve my problem that many of you are having and forced into discover mode.
I run the Wizard and on the step where it asks me to plug in the emitter, if I have it already plugged in, the SW fails and its forcing into discover mode (I actually think that is where our issue is).
If I unplug and replug it back in, I can then select Generic DLP mode.
There isnt a lot more I can today, as its the weekend, and the engs are hopefully getting some rest.
I appreciate your continued presence here, and your responses. But please have the engineers look at our responses over the last few days so we don't get more "this is what you are doing wrong" solutions and close the book before Christmas/New Years on this. It is most definitely not anything to do with how we are installing the drivers, plugging in the emitter, hardware, etc. Between all of us we have tried every different way of installing these drivers imaginable. And even if that was the case, there is absolutely something that has changed in the detection routines since 1.15 for the worse. That is what the engineers need to concentrate on.
[quote name='turls' post='967845' date='Dec 20 2009, 05:20 AM']I appreciate your continued presence here, and your responses. But [b]please[/b] have the engineers look at our responses over the last few days so we don't get more "this is what you are doing wrong" solutions and close the book before Christmas/New Years on this. It is most definitely not anything to do with how we are installing the drivers, plugging in the emitter, hardware, etc. Between all of us we have tried every different way of installing these drivers imaginable. And even if that was the case, there is absolutely something that has changed in the detection routines since 1.15 [i]for the worse[/i]. [b]That is what the engineers need to concentrate on.[/b][/quote]
[quote name='turls' post='967845' date='Dec 20 2009, 05:20 AM']I appreciate your continued presence here, and your responses. But please have the engineers look at our responses over the last few days so we don't get more "this is what you are doing wrong" solutions and close the book before Christmas/New Years on this. It is most definitely not anything to do with how we are installing the drivers, plugging in the emitter, hardware, etc. Between all of us we have tried every different way of installing these drivers imaginable. And even if that was the case, there is absolutely something that has changed in the detection routines since 1.15 for the worse. That is what the engineers need to concentrate on.
Keep in mind that I only updated the driver for the little IR Transmitter you plug in, not the graphics driver, and not the 3D driver. I just checked to completely make sure, and both are 195.81...
Does anyone want to try this to see if it works? (I'm not lucky enough to have my own LED DLP to try it on :( )
Keep in mind that I only updated the driver for the little IR Transmitter you plug in, not the graphics driver, and not the 3D driver. I just checked to completely make sure, and both are 195.81...
Does anyone want to try this to see if it works? (I'm not lucky enough to have my own LED DLP to try it on :( )
Nick
Twitter: @Dr_Inkduff
<b>Processor:</b> Intel Core i7 920 D0 (4Ghz) <b>Motherboard:</b> ASUS P6T
OK, just thought of another possible short-tern solution (until an easy solution, or river update is found).
If any of you have an old CRT laying around, that is capable of 3D, plug it in, and install 3D vision, and run the 3D setup wizard for a CRT.
Then unplug the CRT, and plug in your DLP (or if you have both in at the same time, change your default monitor to the DLP) and VESA cable etc. The, in the 3D part of the NVIDIA control panel, change from Generic CRT display to Generic 3D DLP HDTV. Then try running a 3D game... I think this should wok, but you will need a CRT to get the initial setup (i know I have about 10 old CRT's in my shed lol)
OK, just thought of another possible short-tern solution (until an easy solution, or river update is found).
If any of you have an old CRT laying around, that is capable of 3D, plug it in, and install 3D vision, and run the 3D setup wizard for a CRT.
Then unplug the CRT, and plug in your DLP (or if you have both in at the same time, change your default monitor to the DLP) and VESA cable etc. The, in the 3D part of the NVIDIA control panel, change from Generic CRT display to Generic 3D DLP HDTV. Then try running a 3D game... I think this should wok, but you will need a CRT to get the initial setup (i know I have about 10 old CRT's in my shed lol)
Nick
Twitter: @Dr_Inkduff
<b>Processor:</b> Intel Core i7 920 D0 (4Ghz) <b>Motherboard:</b> ASUS P6T
I have the same TV as you and the new drivers work great with the proviso that I never installed the 1.19 package I installed the Geforce 195.81 package and then the 3D Stereoscopic driver from the 1.15 package (full process described in 1.19 bug thread) this got the driver working before even 1.19 was released with the quirk that upon completion it did not work until initiating a 3d application twice the first time after that perfect.
After 1.19 was released I tried to upgrade using only the 3D Stereoscopic driver added to the already installed 195.81 Geforce driver, result 3D discover only, however exiting install after driver installed but display not set up and going to Nvidia control panel found DLP etc in drop down menu and could setup display normally.
Moral of the story I do not know if 1.19 package works, but do know that clean installed (driver sweeper safe mode + manual remove all nvidia corporation folders after stopping nvidia processes for all users in task manager + removing all nvidia related registry entries in both software and wow64 folder in all sections where listed) 195.81 + 1.15 3D driver (only) overwriting some files installed in the 195.81 geforce drivers do work and after this installing the 195.81 3d driver (17mb) also works and exceptionally well (less convergence / lighting issues). Both of these solutions appear to fail like the previous drivers but in reality do not, first detects display and allows display setup but applications fail a couple of times before everything perfectly Ok afterwards (no re-installing!), second will not detect display during installation but will after closing installation and enabling 3d through nvidia control panel where you will be able to select DLP.
BOTTOM LINE: 1.95.81 WORKS BUT NVIDIA HAS MESSED UP FOR THE THIRD CONSECUTIVE TIME BUT LESS SERIOUSLY THAN THE FIRST 2 TIMES.
I have the same TV as you and the new drivers work great with the proviso that I never installed the 1.19 package I installed the Geforce 195.81 package and then the 3D Stereoscopic driver from the 1.15 package (full process described in 1.19 bug thread) this got the driver working before even 1.19 was released with the quirk that upon completion it did not work until initiating a 3d application twice the first time after that perfect.
After 1.19 was released I tried to upgrade using only the 3D Stereoscopic driver added to the already installed 195.81 Geforce driver, result 3D discover only, however exiting install after driver installed but display not set up and going to Nvidia control panel found DLP etc in drop down menu and could setup display normally.
Moral of the story I do not know if 1.19 package works, but do know that clean installed (driver sweeper safe mode + manual remove all nvidia corporation folders after stopping nvidia processes for all users in task manager + removing all nvidia related registry entries in both software and wow64 folder in all sections where listed) 195.81 + 1.15 3D driver (only) overwriting some files installed in the 195.81 geforce drivers do work and after this installing the 195.81 3d driver (17mb) also works and exceptionally well (less convergence / lighting issues). Both of these solutions appear to fail like the previous drivers but in reality do not, first detects display and allows display setup but applications fail a couple of times before everything perfectly Ok afterwards (no re-installing!), second will not detect display during installation but will after closing installation and enabling 3d through nvidia control panel where you will be able to select DLP.
BOTTOM LINE: 1.95.81 WORKS BUT NVIDIA HAS MESSED UP FOR THE THIRD CONSECUTIVE TIME BUT LESS SERIOUSLY THAN THE FIRST 2 TIMES.
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
I've confirmed there is no detection of Generic DLP (Saumsung HL61A750) using the following steps with the newest 1.19 CD:
Again this is not a hardware issue because the hardware works with 1.15. The emitter is blinking red when it is supposed to be and glowing green when it is supposed to be. Of course never bright green, because we never get the choice of Generic DLP to choose.[/quote]
I also have this television and it works fantastic in 3D.
Please fix this issue.... I miss my 3D :( (with up to date drivers)
Can't even play Avatar now :(
After the avatar update my game will lag now with even the 1.15 driver
Thanks
I've confirmed there is no detection of Generic DLP (Saumsung HL61A750) using the following steps with the newest 1.19 CD:
Again this is not a hardware issue because the hardware works with 1.15. The emitter is blinking red when it is supposed to be and glowing green when it is supposed to be. Of course never bright green, because we never get the choice of Generic DLP to choose.
I also have this television and it works fantastic in 3D.
Please fix this issue.... I miss my 3D :( (with up to date drivers)
Can't even play Avatar now :(
After the avatar update my game will lag now with even the 1.15 driver
Thanks
Crimsonland (10Tons) Discord
https://discord.gg/M8BbwAC
Wallpaper Engine Discord
https://discord.gg/mVXX8x9
Clash of Clans Discord
https://discord.gg/pxE6r3K
Shadowrun Grind Discord
https://discord.gg/vS3qdRz
Shadowrun Grind Facebook Fan Page
https://www.facebook.com/Shadowrungrind/
Clash of Clans Facebook Fan Page
https://www.facebook.com/clashfire/
Xbox Profile
https://account.xbox.com/en-US/Profile?xr=mebarnav
Twitch
https://www.twitch.tv/crimsonland1
Steam Profile
http://steamcommunity.com/profiles/76561197998165812/
Youtube
https://www.youtube.com/crimsonland1
After 1.19 was released I tried to upgrade using only the 3D Stereoscopic driver added to the already installed 195.81 Geforce driver, result 3D discover only, however exiting install after driver installed but display not set up and going to Nvidia control panel found DLP etc in drop down menu and could setup display normally.
Moral of the story I do not know if 1.19 package works, but do know that clean installed (driver sweeper safe mode + manual remove all nvidia corporation folders after stopping nvidia processes for all users in task manager + removing all nvidia related registry entries in both software and wow64 folder in all sections where listed) 195.81 + 1.15 3D driver (only) overwriting some files installed in the 195.81 geforce drivers do work and after this installing the 195.81 3d driver (17mb) also works and exceptionally well (less convergence / lighting issues). Both of these solutions appear to fail like the previous drivers but in reality do not, first detects display and allows display setup but applications fail a couple of times before everything perfectly Ok afterwards (no re-installing!), second will not detect display during installation but will after closing installation and enabling 3d through nvidia control panel where you will be able to select DLP.
BOTTOM LINE: 1.95.81 WORKS BUT NVIDIA HAS MESSED UP FOR THE THIRD CONSECUTIVE TIME BUT LESS SERIOUSLY THAN THE FIRST 2 TIMES.[/quote]
I agree 1.19 works grate with SAMSUNG PLASMA PS50B450(vesa cable)... detect as a generic DLP
After 1.19 was released I tried to upgrade using only the 3D Stereoscopic driver added to the already installed 195.81 Geforce driver, result 3D discover only, however exiting install after driver installed but display not set up and going to Nvidia control panel found DLP etc in drop down menu and could setup display normally.
Moral of the story I do not know if 1.19 package works, but do know that clean installed (driver sweeper safe mode + manual remove all nvidia corporation folders after stopping nvidia processes for all users in task manager + removing all nvidia related registry entries in both software and wow64 folder in all sections where listed) 195.81 + 1.15 3D driver (only) overwriting some files installed in the 195.81 geforce drivers do work and after this installing the 195.81 3d driver (17mb) also works and exceptionally well (less convergence / lighting issues). Both of these solutions appear to fail like the previous drivers but in reality do not, first detects display and allows display setup but applications fail a couple of times before everything perfectly Ok afterwards (no re-installing!), second will not detect display during installation but will after closing installation and enabling 3d through nvidia control panel where you will be able to select DLP.
BOTTOM LINE: 1.95.81 WORKS BUT NVIDIA HAS MESSED UP FOR THE THIRD CONSECUTIVE TIME BUT LESS SERIOUSLY THAN THE FIRST 2 TIMES.
I agree 1.19 works grate with SAMSUNG PLASMA PS50B450(vesa cable)... detect as a generic DLP
Samsung 3D-Ready PLASMA PS50B450
I don't know how, but it seems the only time the Wizard [u][b]won't[/b][/u] let you run it to completion is when your 3D-Ready DLP is your primary monitor.
Almost like there's a '!' in the code somewhere that shouldn't be. The behaviour is the exact opposite of what it should be.
I don't know how, but it seems the only time the Wizard won't let you run it to completion is when your 3D-Ready DLP is your primary monitor.
Almost like there's a '!' in the code somewhere that shouldn't be. The behaviour is the exact opposite of what it should be.
[i]Andrew, if you're reading this, please check your PM's :) [/i][/quote]
They supposedly have DLP working, but have not specified that they have it working on the top of the line finale never to be repeated or duplicated LED DLP TVs ;)
Not all DLPs are equal--unfortunately Samsung dropped DLP and Nvidia hitched their wagon to inferior tech Mits (LaserVue being the exception).
They have it working on a Mits, an earlier Samsung, or a projector, but not Samsung LED DLP, at least not the HL series.
Andrew, if you're reading this, please check your PM's :)
They supposedly have DLP working, but have not specified that they have it working on the top of the line finale never to be repeated or duplicated LED DLP TVs ;)
Not all DLPs are equal--unfortunately Samsung dropped DLP and Nvidia hitched their wagon to inferior tech Mits (LaserVue being the exception).
They have it working on a Mits, an earlier Samsung, or a projector, but not Samsung LED DLP, at least not the HL series.
Let me explain my situation to solve my problem that many of you are having and forced into discover mode.
I run the Wizard and on the step where it asks me to plug in the emitter, if I have it already plugged in, the SW fails and its forcing into discover mode (I actually think that is where our issue is).
If I unplug and replug it back in, I can then select Generic DLP mode.
There isnt a lot more I can today, as its the weekend, and the engs are hopefully getting some rest.
Let me explain my situation to solve my problem that many of you are having and forced into discover mode.
I run the Wizard and on the step where it asks me to plug in the emitter, if I have it already plugged in, the SW fails and its forcing into discover mode (I actually think that is where our issue is).
If I unplug and replug it back in, I can then select Generic DLP mode.
There isnt a lot more I can today, as its the weekend, and the engs are hopefully getting some rest.
I mentioned it before but will repeated here just in case it could shed any kind of light to the situation:
My Dell lcd monitor is not compatible with 3DVision but got detected as any of the 3 choices, DLP, CRT or Discover and after running the wizard, in the drop down menu all these 3 options are available. Ironically my Sammy DLP which is fully capable of S3D and had been working with 3D Vision couldn't be detected by the past 3 releases 1.16, 1.17 and 1.19CD. This is the opposite of what it should be, and another poster cited similar case with his system in one of the threads as well.
[quote]Let me explain my situation to solve my problem that many of you are having and forced into discover mode.
I run the Wizard and on the step where it asks me to plug in the emitter, if I have it already plugged in, the SW fails and its forcing into discover mode (I actually think that is where our issue is).
If I unplug and replug it back in, I can then select Generic DLP mode.[/quote]
I mentioned it before but will repeated here just in case it could shed any kind of light to the situation:
My Dell lcd monitor is not compatible with 3DVision but got detected as any of the 3 choices, DLP, CRT or Discover and after running the wizard, in the drop down menu all these 3 options are available. Ironically my Sammy DLP which is fully capable of S3D and had been working with 3D Vision couldn't be detected by the past 3 releases 1.16, 1.17 and 1.19CD. This is the opposite of what it should be, and another poster cited similar case with his system in one of the threads as well.
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+
I was getting all sorts of errors with my CRT being detected, and this is how I fixed it... (after reading these last two posts its got me thinking it might work for DLP's too...)
In the start menu, click on devices and printers. You should see your "NVIDIA stereo controller". Right Click it and select "Properties". Navigate to the "Hardware" tab, and click "Properties" again. Go into the "Driver" tab and click on the "Update Driver..." button. You will get two options, click on "Search automatically for updated driver software".
You may have to have Windows Update enabled for this to work.
I'm not sure why this worked exactly, but I think there may be a problem with the NVIDIA stereo controller driver in the 1.19 CD drivers, so it doesn't detect it correctly... Has anyone tried this driver with a 2233RZ or other supported monitor? Probably not... Which is why this error has only been reported for DLP's.
As soon as I installed the driver that windows found for me, the setup wizard detected everything perfectly.
I'm not sure if this will fix the problem you guys' are having, but I sure hope so...
Nick
I was getting all sorts of errors with my CRT being detected, and this is how I fixed it... (after reading these last two posts its got me thinking it might work for DLP's too...)
In the start menu, click on devices and printers. You should see your "NVIDIA stereo controller". Right Click it and select "Properties". Navigate to the "Hardware" tab, and click "Properties" again. Go into the "Driver" tab and click on the "Update Driver..." button. You will get two options, click on "Search automatically for updated driver software".
You may have to have Windows Update enabled for this to work.
I'm not sure why this worked exactly, but I think there may be a problem with the NVIDIA stereo controller driver in the 1.19 CD drivers, so it doesn't detect it correctly... Has anyone tried this driver with a 2233RZ or other supported monitor? Probably not... Which is why this error has only been reported for DLP's.
As soon as I installed the driver that windows found for me, the setup wizard detected everything perfectly.
I'm not sure if this will fix the problem you guys' are having, but I sure hope so...
Nick
Twitter: @Dr_Inkduff
<b>Processor:</b> Intel Core i7 920 D0 (4Ghz) <b>Motherboard:</b> ASUS P6T
<b>Memory:</b> 6GB DDR3 RAM (Kingston) <b>Graphics:</b> GTX 260 (216 cores, physX); EVGA GTX 480 SC
<b>OS:</b> Win7 Home Premium 64-bit / Vista Home Premium 64-bit
<b>Hard Disks:</b> 750GB + 500GB <b>Tower:</b> Antec 'Twelve Hundred' Gaming Tower
<b>Monitors:</b> 24" ACER GD245HQbd 120Hz 1920*1080 + 22" widescreen LCD 1680x1050
http://bit.ly/Bluesteel
I was getting all sorts of errors with my CRT being detected, and this is how I fixed it... (after reading these last two posts its got me thinking it might work for DLP's too...)
In the start menu, click on devices and printers. You should see your "NVIDIA stereo controller". Right Click it and select "Properties". Navigate to the "Hardware" tab, and click "Properties" again. Go into the "Driver" tab and click on the "Update Driver..." button. You will get two options, click on "Search automatically for updated driver software".
You may have to have Windows Update enabled for this to work.
I'm not sure why this worked exactly, but I think there may be a problem with the NVIDIA stereo controller driver in the 1.19 CD drivers, so it doesn't detect it correctly... Has anyone tried this driver with a 2233RZ or other supported monitor? Probably not... Which is why this error has only been reported for DLP's.
As soon as I installed the driver that windows found for me, the setup wizard detected everything perfectly.
I'm not sure if this will fix the problem you guys' are having, but I sure hope so...
Nick[/quote]
Can you confirm that driver is the lastest one...195.8-something?
No use if the driver is an old version. When I installed Nvidia Geforce drivers like this, Windows found an old version to install automatically...
I was getting all sorts of errors with my CRT being detected, and this is how I fixed it... (after reading these last two posts its got me thinking it might work for DLP's too...)
In the start menu, click on devices and printers. You should see your "NVIDIA stereo controller". Right Click it and select "Properties". Navigate to the "Hardware" tab, and click "Properties" again. Go into the "Driver" tab and click on the "Update Driver..." button. You will get two options, click on "Search automatically for updated driver software".
You may have to have Windows Update enabled for this to work.
I'm not sure why this worked exactly, but I think there may be a problem with the NVIDIA stereo controller driver in the 1.19 CD drivers, so it doesn't detect it correctly... Has anyone tried this driver with a 2233RZ or other supported monitor? Probably not... Which is why this error has only been reported for DLP's.
As soon as I installed the driver that windows found for me, the setup wizard detected everything perfectly.
I'm not sure if this will fix the problem you guys' are having, but I sure hope so...
Nick
Can you confirm that driver is the lastest one...195.8-something?
No use if the driver is an old version. When I installed Nvidia Geforce drivers like this, Windows found an old version to install automatically...
BTW Andrew I have a GTX 295 and plan on getting Fermi, will 3Dvision work with Fermi SLI just like the 295? It may be too soon to ask that, but I was wondering if 2 x GTX 295s > 2 X Fermi.
BTW Andrew I have a GTX 295 and plan on getting Fermi, will 3Dvision work with Fermi SLI just like the 295? It may be too soon to ask that, but I was wondering if 2 x GTX 295s > 2 X Fermi.
Let me explain my situation to solve my problem that many of you are having and forced into discover mode.
I run the Wizard and on the step where it asks me to plug in the emitter, if I have it already plugged in, the SW fails and its forcing into discover mode (I actually think that is where our issue is).
If I unplug and replug it back in, I can then select Generic DLP mode.
There isnt a lot more I can today, as its the weekend, and the engs are hopefully getting some rest.[/quote]
I appreciate your continued presence here, and your responses. But [b]please[/b] have the engineers look at our responses over the last few days so we don't get more "this is what you are doing wrong" solutions and close the book before Christmas/New Years on this. It is most definitely not anything to do with how we are installing the drivers, plugging in the emitter, hardware, etc. Between all of us we have tried every different way of installing these drivers imaginable. And even if that was the case, there is absolutely something that has changed in the detection routines since 1.15 [i]for the worse[/i]. [b]That is what the engineers need to concentrate on.[/b]
Let me explain my situation to solve my problem that many of you are having and forced into discover mode.
I run the Wizard and on the step where it asks me to plug in the emitter, if I have it already plugged in, the SW fails and its forcing into discover mode (I actually think that is where our issue is).
If I unplug and replug it back in, I can then select Generic DLP mode.
There isnt a lot more I can today, as its the weekend, and the engs are hopefully getting some rest.
I appreciate your continued presence here, and your responses. But please have the engineers look at our responses over the last few days so we don't get more "this is what you are doing wrong" solutions and close the book before Christmas/New Years on this. It is most definitely not anything to do with how we are installing the drivers, plugging in the emitter, hardware, etc. Between all of us we have tried every different way of installing these drivers imaginable. And even if that was the case, there is absolutely something that has changed in the detection routines since 1.15 for the worse. That is what the engineers need to concentrate on.
[quote name='turls' post='967845' date='Dec 20 2009, 05:20 AM']I appreciate your continued presence here, and your responses. But [b]please[/b] have the engineers look at our responses over the last few days so we don't get more "this is what you are doing wrong" solutions and close the book before Christmas/New Years on this. It is most definitely not anything to do with how we are installing the drivers, plugging in the emitter, hardware, etc. Between all of us we have tried every different way of installing these drivers imaginable. And even if that was the case, there is absolutely something that has changed in the detection routines since 1.15 [i]for the worse[/i]. [b]That is what the engineers need to concentrate on.[/b][/quote]
[quote name='turls' post='967845' date='Dec 20 2009, 05:20 AM']I appreciate your continued presence here, and your responses. But please have the engineers look at our responses over the last few days so we don't get more "this is what you are doing wrong" solutions and close the book before Christmas/New Years on this. It is most definitely not anything to do with how we are installing the drivers, plugging in the emitter, hardware, etc. Between all of us we have tried every different way of installing these drivers imaginable. And even if that was the case, there is absolutely something that has changed in the detection routines since 1.15 for the worse. That is what the engineers need to concentrate on.
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+
Does anyone want to try this to see if it works? (I'm not lucky enough to have my own LED DLP to try it on :( )
Nick
Does anyone want to try this to see if it works? (I'm not lucky enough to have my own LED DLP to try it on :( )
Nick
Twitter: @Dr_Inkduff
<b>Processor:</b> Intel Core i7 920 D0 (4Ghz) <b>Motherboard:</b> ASUS P6T
<b>Memory:</b> 6GB DDR3 RAM (Kingston) <b>Graphics:</b> GTX 260 (216 cores, physX); EVGA GTX 480 SC
<b>OS:</b> Win7 Home Premium 64-bit / Vista Home Premium 64-bit
<b>Hard Disks:</b> 750GB + 500GB <b>Tower:</b> Antec 'Twelve Hundred' Gaming Tower
<b>Monitors:</b> 24" ACER GD245HQbd 120Hz 1920*1080 + 22" widescreen LCD 1680x1050
http://bit.ly/Bluesteel
If any of you have an old CRT laying around, that is capable of 3D, plug it in, and install 3D vision, and run the 3D setup wizard for a CRT.
Then unplug the CRT, and plug in your DLP (or if you have both in at the same time, change your default monitor to the DLP) and VESA cable etc. The, in the 3D part of the NVIDIA control panel, change from Generic CRT display to Generic 3D DLP HDTV. Then try running a 3D game... I think this should wok, but you will need a CRT to get the initial setup (i know I have about 10 old CRT's in my shed lol)
Nick
If any of you have an old CRT laying around, that is capable of 3D, plug it in, and install 3D vision, and run the 3D setup wizard for a CRT.
Then unplug the CRT, and plug in your DLP (or if you have both in at the same time, change your default monitor to the DLP) and VESA cable etc. The, in the 3D part of the NVIDIA control panel, change from Generic CRT display to Generic 3D DLP HDTV. Then try running a 3D game... I think this should wok, but you will need a CRT to get the initial setup (i know I have about 10 old CRT's in my shed lol)
Nick
Twitter: @Dr_Inkduff
<b>Processor:</b> Intel Core i7 920 D0 (4Ghz) <b>Motherboard:</b> ASUS P6T
<b>Memory:</b> 6GB DDR3 RAM (Kingston) <b>Graphics:</b> GTX 260 (216 cores, physX); EVGA GTX 480 SC
<b>OS:</b> Win7 Home Premium 64-bit / Vista Home Premium 64-bit
<b>Hard Disks:</b> 750GB + 500GB <b>Tower:</b> Antec 'Twelve Hundred' Gaming Tower
<b>Monitors:</b> 24" ACER GD245HQbd 120Hz 1920*1080 + 22" widescreen LCD 1680x1050
http://bit.ly/Bluesteel