I think we have a repro case in house, which was caused by a bad USB cable.
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.
I think we have a repro case in house, which was caused by a bad USB cable.
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.
I did switch USB port, but not USB cable - (However it is ensured that the USB cable was good because with CD 1.15, (before the 1.19 and after rolling back ato 1.15), the USB cable and the emitter work fine and the Sammy is being detected right now with 1.15)
And yes, during the wizard (1.19) when emitter plugged in, it DOES glow faint green.
[quote name='andrewf@nvidia' post='966664' date='Dec 17 2009, 04:55 PM']Hi all
I think we have a repro case in house, which was caused by a bad USB cable.
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.[/quote]
I did switch USB port, but not USB cable - (However it is ensured that the USB cable was good because with CD 1.15, (before the 1.19 and after rolling back ato 1.15), the USB cable and the emitter work fine and the Sammy is being detected right now with 1.15)
And yes, during the wizard (1.19) when emitter plugged in, it DOES glow faint green.
[quote name='andrewf@nvidia' post='966664' date='Dec 17 2009, 04:55 PM']Hi all
I think we have a repro case in house, which was caused by a bad USB cable.
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.
What I'm afraid is that there are cases in which, even with the identical model Sammys for testing, the driver being installed in a development environment may likely passes tests that it shouldn't due to the test software environment itself, ie. padded and residual codes/patches/lib files/dlls/configs/inits etc. on a dev. machine, these settings can act to provide the missing components/switches/triggers to the driver and in effect, cover up the bug.
[quote name='turls' post='966654' date='Dec 17 2009, 04:41 PM']Ditto. All the other Samsung specific fixes Nvidia did before for Samsung improved things greatly.
I'm more than open to be contacted directly to work through this with Nvidia if you don't have this specific model.[/quote]
What I'm afraid is that there are cases in which, even with the identical model Sammys for testing, the driver being installed in a development environment may likely passes tests that it shouldn't due to the test software environment itself, ie. padded and residual codes/patches/lib files/dlls/configs/inits etc. on a dev. machine, these settings can act to provide the missing components/switches/triggers to the driver and in effect, cover up the bug.
[quote name='turls' post='966654' date='Dec 17 2009, 04:41 PM']Ditto. All the other Samsung specific fixes Nvidia did before for Samsung improved things greatly.
I'm more than open to be contacted directly to work through this with Nvidia if you don't have this specific model.
[quote name='distant' post='966690' date='Dec 17 2009, 07:37 PM']I did switch USB port, but not USB cable - (However it is ensured that the USB cable was good because with CD 1.15, (before the 1.19 and after rolling back ato 1.15), the USB cable and the emitter work fine and the Sammy is being detected right now with 1.15)
And yes, during the wizard (1.19) when emitter plugged in, it DOES glow faint green.[/quote]
Many of us besides distant and me have been able to go back and forth between 1.15 and 1.17, 1.19, etc. and always get it working again with 1.15. It isn't a hardware issue, unless for some unknown reason the issue doesn't show up until newer than 1.15 (and then a LOT of us have bad hardware).
[quote name='distant' post='966690' date='Dec 17 2009, 07:37 PM']I did switch USB port, but not USB cable - (However it is ensured that the USB cable was good because with CD 1.15, (before the 1.19 and after rolling back ato 1.15), the USB cable and the emitter work fine and the Sammy is being detected right now with 1.15)
And yes, during the wizard (1.19) when emitter plugged in, it DOES glow faint green.
Many of us besides distant and me have been able to go back and forth between 1.15 and 1.17, 1.19, etc. and always get it working again with 1.15. It isn't a hardware issue, unless for some unknown reason the issue doesn't show up until newer than 1.15 (and then a LOT of us have bad hardware).
Intalled Driver version 195.81 for both Geforce and 3D vision. Setup behaves exactly the same as previous version I tried (195.62 I believe).
1. Choose 3D vision or 3D discover - i choose 3D vision
2. Plug usb and Vesa - done
3. Choose TV setup - I choose the middle one which has a giant TV
4. Display not detected - options are re-detect my tv, back, next, exit...and thats it.
If I choose next, it proceeds with 3D discover mediacl and image test...and thats all she wrote.
I tried different USB ports, different cable... didn't work.
I'll go back to 1.15 I guess for now and wait for future update?
[quote name='andrewf@nvidia' post='966664' date='Dec 17 2009, 06:55 PM']I think we have a repro case in house, which was caused by a bad USB cable.
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.[/quote]
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:
[quote]Device Manager(devmgmt.msc) > expand Display Adapters > right click on Display Adapter > Uninstall.
Control Panel > Programs and Settings(appwiz.cpl) > Uninstall Nvidia PhysX, Uninstall Nvidia Stereoscopic 3D Driver.
Unplug IR transmitter from USB cable.
Run Driversweeper > tick Nvidia Display, Nvidia PhysX > Analyze and Clean. Reboot.
F8 boot into Safe Mode, run Driversweeper again as before to delete locked/in-use files. Reboot.
Install new Driver set from CD directory using Launch.exe: first GPU driver is installed, reboots, then 3D Vision driver is installed, plug in IR transmitter when prompted by setup.[/quote]
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 understand wanting to dumb down the detection of devices and not give us control, but at this point we can't count on newer drivers to detect hardware like it always has in the past. We need some way of overriding the dumbed down drivers so we can force stuff when we run into garbage like this, especially after we see how hard it is to replicate by Nvidia QA!
[quote name='andrewf@nvidia' post='966664' date='Dec 17 2009, 06:55 PM']I think we have a repro case in house, which was caused by a bad USB cable.
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.
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:
Device Manager(devmgmt.msc) > expand Display Adapters > right click on Display Adapter > Uninstall.
Control Panel > Programs and Settings(appwiz.cpl) > Uninstall Nvidia PhysX, Uninstall Nvidia Stereoscopic 3D Driver.
Unplug IR transmitter from USB cable.
Run Driversweeper > tick Nvidia Display, Nvidia PhysX > Analyze and Clean. Reboot.
F8 boot into Safe Mode, run Driversweeper again as before to delete locked/in-use files. Reboot.
Install new Driver set from CD directory using Launch.exe: first GPU driver is installed, reboots, then 3D Vision driver is installed, plug in IR transmitter when prompted by setup.
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 understand wanting to dumb down the detection of devices and not give us control, but at this point we can't count on newer drivers to detect hardware like it always has in the past. We need some way of overriding the dumbed down drivers so we can force stuff when we run into garbage like this, especially after we see how hard it is to replicate by Nvidia QA!
[quote name='dreamingawake' post='967088' date='Dec 18 2009, 12:57 PM']I want to go try these new drivers on my 50" Samsung Plasma but I have a
feeling it would just be more time wasted.
Think I'll wait for confirmation that it works, and another bleepin' driver fix..
Awesome. /pirate.gif' class='bbc_emoticon' alt=':pirate:' />[/quote]
Well so far the only people that have confirmed the new driver DOESN'T work are those with Samsung LED DLPs. So yes, we need other people to try unfortunately to make sure this stays on Nvidia's radar. We're all "generic unsupported" so there is strength in numbers. Where is everybody anyway?
Well so far the only people that have confirmed the new driver DOESN'T work are those with Samsung LED DLPs. So yes, we need other people to try unfortunately to make sure this stays on Nvidia's radar. We're all "generic unsupported" so there is strength in numbers. Where is everybody anyway?
Can the users that arent seeing the Generic DLP step tell me your Samsung DLP model numbers?
Can the users that arent seeing the Generic DLP step tell me your Samsung DLP model numbers?
[quote name='andrewf@nvidia' post='966636' date='Dec 17 2009, 03:49 PM']Ok we are making some progress.
Can the users that arent seeing the Generic DLP step tell me your Samsung DLP model numbers?[/quote]
[quote name='andrewf@nvidia' post='966636' date='Dec 17 2009, 03:49 PM']Ok we are making some progress.
Can the users that arent seeing the Generic DLP step tell me your Samsung DLP model numbers?
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+
Ditto. All the other Samsung specific fixes Nvidia did before for Samsung improved things greatly.
I'm more than open to be contacted directly to work through this with Nvidia if you don't have this specific model.
Ditto. All the other Samsung specific fixes Nvidia did before for Samsung improved things greatly.
I'm more than open to be contacted directly to work through this with Nvidia if you don't have this specific model.
I think we have a repro case in house, which was caused by a bad USB cable.
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.
I think we have a repro case in house, which was caused by a bad USB cable.
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.
And yes, during the wizard (1.19) when emitter plugged in, it DOES glow faint green.
[quote name='andrewf@nvidia' post='966664' date='Dec 17 2009, 04:55 PM']Hi all
I think we have a repro case in house, which was caused by a bad USB cable.
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.[/quote]
And yes, during the wizard (1.19) when emitter plugged in, it DOES glow faint green.
[quote name='andrewf@nvidia' post='966664' date='Dec 17 2009, 04:55 PM']Hi all
I think we have a repro case in house, which was caused by a bad USB cable.
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.
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+
[quote name='turls' post='966654' date='Dec 17 2009, 04:41 PM']Ditto. All the other Samsung specific fixes Nvidia did before for Samsung improved things greatly.
I'm more than open to be contacted directly to work through this with Nvidia if you don't have this specific model.[/quote]
[quote name='turls' post='966654' date='Dec 17 2009, 04:41 PM']Ditto. All the other Samsung specific fixes Nvidia did before for Samsung improved things greatly.
I'm more than open to be contacted directly to work through this with Nvidia if you don't have this specific model.
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+
And yes, during the wizard (1.19) when emitter plugged in, it DOES glow faint green.[/quote]
Many of us besides distant and me have been able to go back and forth between 1.15 and 1.17, 1.19, etc. and always get it working again with 1.15. It isn't a hardware issue, unless for some unknown reason the issue doesn't show up until newer than 1.15 (and then a LOT of us have bad hardware).
And yes, during the wizard (1.19) when emitter plugged in, it DOES glow faint green.
Many of us besides distant and me have been able to go back and forth between 1.15 and 1.17, 1.19, etc. and always get it working again with 1.15. It isn't a hardware issue, unless for some unknown reason the issue doesn't show up until newer than 1.15 (and then a LOT of us have bad hardware).
Can not get it to work as well...
Using samsung hl67a750. 67 inch LED monster...
Intalled Driver version 195.81 for both Geforce and 3D vision. Setup behaves exactly the same as previous version I tried (195.62 I believe).
1. Choose 3D vision or 3D discover - i choose 3D vision
2. Plug usb and Vesa - done
3. Choose TV setup - I choose the middle one which has a giant TV
4. Display not detected - options are re-detect my tv, back, next, exit...and thats it.
If I choose next, it proceeds with 3D discover mediacl and image test...and thats all she wrote.
I tried different USB ports, different cable... didn't work.
I'll go back to 1.15 I guess for now and wait for future update?
Can not get it to work as well...
Using samsung hl67a750. 67 inch LED monster...
Intalled Driver version 195.81 for both Geforce and 3D vision. Setup behaves exactly the same as previous version I tried (195.62 I believe).
1. Choose 3D vision or 3D discover - i choose 3D vision
2. Plug usb and Vesa - done
3. Choose TV setup - I choose the middle one which has a giant TV
4. Display not detected - options are re-detect my tv, back, next, exit...and thats it.
If I choose next, it proceeds with 3D discover mediacl and image test...and thats all she wrote.
I tried different USB ports, different cable... didn't work.
I'll go back to 1.15 I guess for now and wait for future update?
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.[/quote]
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:
[quote]Device Manager(devmgmt.msc) > expand Display Adapters > right click on Display Adapter > Uninstall.
Control Panel > Programs and Settings(appwiz.cpl) > Uninstall Nvidia PhysX, Uninstall Nvidia Stereoscopic 3D Driver.
Unplug IR transmitter from USB cable.
Run Driversweeper > tick Nvidia Display, Nvidia PhysX > Analyze and Clean. Reboot.
F8 boot into Safe Mode, run Driversweeper again as before to delete locked/in-use files. Reboot.
Install new Driver set from CD directory using Launch.exe: first GPU driver is installed, reboots, then 3D Vision driver is installed, plug in IR transmitter when prompted by setup.[/quote]
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 understand wanting to dumb down the detection of devices and not give us control, but at this point we can't count on newer drivers to detect hardware like it always has in the past. We need some way of overriding the dumbed down drivers so we can force stuff when we run into garbage like this, especially after we see how hard it is to replicate by Nvidia QA!
Can anyone with a failure now confirm this by trying to a different USB port, USB cable, or ensure you are not connected to an emitter? In addition, make sure during the wizard when you plug in the emitter, it glows faint green. If it doesnt, that's a problem.
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 understand wanting to dumb down the detection of devices and not give us control, but at this point we can't count on newer drivers to detect hardware like it always has in the past. We need some way of overriding the dumbed down drivers so we can force stuff when we run into garbage like this, especially after we see how hard it is to replicate by Nvidia QA!
feeling it would just be more time wasted.
Think I'll wait for confirmation that it works, and another bleepin' driver fix..
Awesome.
feeling it would just be more time wasted.
Think I'll wait for confirmation that it works, and another bleepin' driver fix..
Awesome.
feeling it would just be more time wasted.
Think I'll wait for confirmation that it works, and another bleepin' driver fix..
Awesome.
Well so far the only people that have confirmed the new driver DOESN'T work are those with Samsung LED DLPs. So yes, we need other people to try unfortunately to make sure this stays on Nvidia's radar. We're all "generic unsupported" so there is strength in numbers. Where is everybody anyway?
feeling it would just be more time wasted.
Think I'll wait for confirmation that it works, and another bleepin' driver fix..
Awesome.
Well so far the only people that have confirmed the new driver DOESN'T work are those with Samsung LED DLPs. So yes, we need other people to try unfortunately to make sure this stays on Nvidia's radar. We're all "generic unsupported" so there is strength in numbers. Where is everybody anyway?
[i]Andrew, if you're reading this, please check your PM's :) [/i]
Andrew, if you're reading this, please check your PM's :)
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
My setup:
Windows 7 (64-bit)
v 1.19, both drivers installed
Samsung HL61A750
9800 GTX (Black)
No option to select Generic DLP, same as others
v 1.15 works
My setup:
Windows 7 (64-bit)
v 1.19, both drivers installed
Samsung HL61A750
9800 GTX (Black)
No option to select Generic DLP, same as others
v 1.15 works
My set up...
Windows 7 (64-bit)
v 1.19, both drivers installed using Nvidia install method with driver cleaner thrown in for good measure.
Samsung HL61A750
295 GTX
I had to re-install v 1.15 to get 3D back.
My set up...
Windows 7 (64-bit)
v 1.19, both drivers installed using Nvidia install method with driver cleaner thrown in for good measure.
Samsung HL61A750
295 GTX
I had to re-install v 1.15 to get 3D back.