Driver 1.20 - shouldn´t there be suport for Sammy DLP?
1 / 4
Installed the new driver Version minutes ago. Like Nvidia mentioned in the release notes:
- Fixed a bug with the driver that prevented Generic DLP mode from working. This should allow Samsung DLP users the ability to use 3D Vision again.
I was happy that it should work now.
But after Installation was done i wasn´t able to choose Generic DLP again!
"crap" i thought and tried the previous trick only to learn that this bug was fixed :)
Nividia you are joking or not?
Uninstalled everything and installed gpu driver and stereo driver. Again only frackn discoverer! Maybe Andrew your team forgot to add support for HL61a750 users ?
After all the problems the new driver (3d Vision Driver) made wouldn´t it be better to open it for all display methods as the old (ELSAs) one did?
Maybe the other big player in the GPU industry will make that better in future driver revisions...
Installed the new driver Version minutes ago. Like Nvidia mentioned in the release notes:
- Fixed a bug with the driver that prevented Generic DLP mode from working. This should allow Samsung DLP users the ability to use 3D Vision again.
I was happy that it should work now.
But after Installation was done i wasn´t able to choose Generic DLP again!
"crap" i thought and tried the previous trick only to learn that this bug was fixed :)
Nividia you are joking or not?
Uninstalled everything and installed gpu driver and stereo driver. Again only frackn discoverer! Maybe Andrew your team forgot to add support for HL61a750 users ?
After all the problems the new driver (3d Vision Driver) made wouldn´t it be better to open it for all display methods as the old (ELSAs) one did?
Maybe the other big player in the GPU industry will make that better in future driver revisions...
[quote name='VadersApp2' post='986227' date='Jan 22 2010, 03:25 PM']Installed the new driver Version minutes ago. Like Nvidia mentioned in the release notes:
- Fixed a bug with the driver that prevented Generic DLP mode from working. This should allow Samsung DLP users the ability to use 3D Vision again.
I was happy that it should work now.
But after Installation was done i wasn´t able to choose Generic DLP again!
"crap" i thought and tried the previous trick only to learn that this bug was fixed :)
Nividia you are joking or not?
Uninstalled everything and installed gpu driver and stereo driver. Again only frackn discoverer! Maybe Andrew your team forgot to add support for HL61a750 users ?
After all the problems the new driver (3d Vision Driver) made wouldn´t it be better to open it for all display methods as the old (ELSAs) one did?
Maybe the other big player in the GPU industry will make that better in future driver revisions...[/quote]
Where did you download driver 1.20. I cant seem to find the driver, the newest is only 1.19?
[quote name='VadersApp2' post='986227' date='Jan 22 2010, 03:25 PM']Installed the new driver Version minutes ago. Like Nvidia mentioned in the release notes:
- Fixed a bug with the driver that prevented Generic DLP mode from working. This should allow Samsung DLP users the ability to use 3D Vision again.
I was happy that it should work now.
But after Installation was done i wasn´t able to choose Generic DLP again!
"crap" i thought and tried the previous trick only to learn that this bug was fixed :)
Nividia you are joking or not?
Uninstalled everything and installed gpu driver and stereo driver. Again only frackn discoverer! Maybe Andrew your team forgot to add support for HL61a750 users ?
After all the problems the new driver (3d Vision Driver) made wouldn´t it be better to open it for all display methods as the old (ELSAs) one did?
Maybe the other big player in the GPU industry will make that better in future driver revisions...
Where did you download driver 1.20. I cant seem to find the driver, the newest is only 1.19?
I can't believe 1.20 CD still got this bug! Unforgivable cruel joke. Seriously I have a bad feeling for whomever responsible for these past 5 releases' job security. It just can't be the company policy to announce one thing and release the opposite. That's called bait and switch and they have laws against this type of business practice.
Peculiar thing is though the download driver search is showing it's not ready "try later" message so I'm thinking I should wait for it instead of installing from the link above given that vaderapp got even worse problem with the 1.20 than the 1.19 and the workaround that works for 1.19 no longer works for 1.20.
I can't believe 1.20 CD still got this bug! Unforgivable cruel joke. Seriously I have a bad feeling for whomever responsible for these past 5 releases' job security. It just can't be the company policy to announce one thing and release the opposite. That's called bait and switch and they have laws against this type of business practice.
Peculiar thing is though the download driver search is showing it's not ready "try later" message so I'm thinking I should wait for it instead of installing from the link above given that vaderapp got even worse problem with the 1.20 than the 1.19 and the workaround that works for 1.19 no longer works for 1.20.
[quote name='distant' post='986324' date='Jan 22 2010, 11:47 AM']I can't believe 1.20 CD still got this bug! Unforgivable cruel joke. Seriously I have a bad feeling for whomever responsible for these past 5 releases' job security. It just can't be the company policy to announce one thing and release the opposite. That's called bait and switch and they have laws against this type of business practice.
Peculiar thing is though the download driver search is showing it's not ready "try later" message so I'm thinking I should wait for it instead of installing from the link above given that vaderapp got even worse problem with the 1.20 than the 1.19 and the workaround that works for 1.19 no longer works for 1.20.[/quote]
I don't know how they are going to have it fixed in 1.20 when as of this past Monday they still thought they fixed everything for Samsung DLP in 1.19. That would be one heck of a turnaround time. What they should have done (maybe they still will) is delay any further updates until they nail this bug that should have been fixed 3 months ago!
[quote name='distant' post='986324' date='Jan 22 2010, 11:47 AM']I can't believe 1.20 CD still got this bug! Unforgivable cruel joke. Seriously I have a bad feeling for whomever responsible for these past 5 releases' job security. It just can't be the company policy to announce one thing and release the opposite. That's called bait and switch and they have laws against this type of business practice.
Peculiar thing is though the download driver search is showing it's not ready "try later" message so I'm thinking I should wait for it instead of installing from the link above given that vaderapp got even worse problem with the 1.20 than the 1.19 and the workaround that works for 1.19 no longer works for 1.20.
I don't know how they are going to have it fixed in 1.20 when as of this past Monday they still thought they fixed everything for Samsung DLP in 1.19. That would be one heck of a turnaround time. What they should have done (maybe they still will) is delay any further updates until they nail this bug that should have been fixed 3 months ago!
[quote name='turls' post='986478' date='Jan 22 2010, 03:59 PM']I don't know how they are going to have it fixed in 1.20 when as of this past Monday they still thought they fixed everything for Samsung DLP in 1.19. That would be one heck of a turnaround time. What they should have done (maybe they still will) is delay any further updates until they nail this bug that should have been fixed 3 months ago![/quote]
Just thought I'd add no Samsung DLP love with the 1.20 for my HL61A750A. No detection. Oh well, I've reinstalled 1.15 which are the last drivers to detect my DLP.
[quote name='turls' post='986478' date='Jan 22 2010, 03:59 PM']I don't know how they are going to have it fixed in 1.20 when as of this past Monday they still thought they fixed everything for Samsung DLP in 1.19. That would be one heck of a turnaround time. What they should have done (maybe they still will) is delay any further updates until they nail this bug that should have been fixed 3 months ago!
Just thought I'd add no Samsung DLP love with the 1.20 for my HL61A750A. No detection. Oh well, I've reinstalled 1.15 which are the last drivers to detect my DLP.
Just downloaded the official Windows certified 1.20 CD and installed.
[b]CONFIRMED THAT 1.20 CD STILL DOES [color="#ff00ff"]NOT[/color] DETECT SAMSUNG DLP!
[color="#000000"][i]WORSE[/i][/color], THE WORKAROUND NO LONGER FREAKING WORKS.
[/b]My 3D Vision product is now officially Windows certified [b]USELESS![/b]
Thank you Nvidia for a fine, fine driver release yet again. /devil.gif' class='bbc_emoticon' alt=':devil:' />
EDIT: Didn't see Andrew's post above before posting mine. Well, it's good venting anyway. But in light of Andrew's post whose spirit is just great, hope someone in the above locales can assist with the debugging, probably have to lug in the computer I imagine.
Just downloaded the official Windows certified 1.20 CD and installed.
CONFIRMED THAT 1.20 CD STILL DOES NOT DETECT SAMSUNG DLP!
WORSE, THE WORKAROUND NO LONGER FREAKING WORKS.
My 3D Vision product is now officially Windows certified USELESS!
Thank you Nvidia for a fine, fine driver release yet again. /devil.gif' class='bbc_emoticon' alt=':devil:' />
EDIT: Didn't see Andrew's post above before posting mine. Well, it's good venting anyway. But in light of Andrew's post whose spirit is just great, hope someone in the above locales can assist with the debugging, probably have to lug in the computer I imagine.
We apologize for this. I really cant explain why its not working.
Is there anyone in the Santa Clara, CA or Austin, TX area that wants to come by the office for some debugging fun? PM me![/quote]
I don't get it. We understand you don't have every device in office to test. I've offered to help remotely previously but nobody has taken me up on it.
The solution is not to try to fix every goofy thing for every one of how many dozens of devices this should work with. It is to [b]allow us to override detection[/b] which we've been asking for for at least 2 months if not longer.
Why can't we just get a response on why this is or isn't possible? Sounds like right now we are dead in the water with no hope of getting something fixed that used to work before they messed with the dual monitors. Why can't somebody just go back and figure out what changed after 1.15 also? Has anybody even checked that?
We apologize for this. I really cant explain why its not working.
Is there anyone in the Santa Clara, CA or Austin, TX area that wants to come by the office for some debugging fun? PM me!
I don't get it. We understand you don't have every device in office to test. I've offered to help remotely previously but nobody has taken me up on it.
The solution is not to try to fix every goofy thing for every one of how many dozens of devices this should work with. It is to allow us to override detection which we've been asking for for at least 2 months if not longer.
Why can't we just get a response on why this is or isn't possible? Sounds like right now we are dead in the water with no hope of getting something fixed that used to work before they messed with the dual monitors. Why can't somebody just go back and figure out what changed after 1.15 also? Has anybody even checked that?
[quote name='distant' post='986707' date='Jan 22 2010, 06:43 PM']EDIT: Didn't see Andrew's post above before posting mine. Well, it's good venting anyway. But in light of Andrew's post whose spirit is just great, hope someone in the above locales can assist with the debugging, probably have to lug in the computer I imagine.[/quote]
And the 60" + DLP? I think they can do more than they have done remotely. Shouldn't need a local person to figure this out.
[quote name='distant' post='986707' date='Jan 22 2010, 06:43 PM']EDIT: Didn't see Andrew's post above before posting mine. Well, it's good venting anyway. But in light of Andrew's post whose spirit is just great, hope someone in the above locales can assist with the debugging, probably have to lug in the computer I imagine.
And the 60" + DLP? I think they can do more than they have done remotely. Shouldn't need a local person to figure this out.
[quote name='turls' post='986966' date='Jan 23 2010, 10:26 AM']The solution is not to try to fix every goofy thing for every one of how many dozens of devices this should work with. It is to [b]allow us to override detection[/b] which we've been asking for for at least 2 months if not longer.[/quote]
[DANGER, DANGER conspiracy theory]
I guess thats the strategy. Maybe Nvidia is licencing 3D Vision and try to bind the manufacturers to their GPUs. Samsung sold their great LED-DLP Tvs and found out that they are harming their sells because of cheap big screen entertainment. So they took them out of the market. Samsung agreed to cooperate with Nvidia with their new LCD-Displays and Samsung decided not to support DLP. Thats because of getting Customers fed up with not beeing able to get 3D working and force them to buy their new products. Which seems to work, as you can read here in forums.
[/DANGER, DANGER conspiracy theory]
But as can see small 23 inch displays suffer again of the ghosting problem. All i can say DLP-Checkerboard reduces resolution but there is absolutly no ghosting. LCD is a no go for me. I hope an inexpensive 1080p 120hz projector will hit the market soon. :)
What i did not to explode yesterday was deactivate 3D Vision, activated Iz3d driver, put on my $5 shutterlglasses (which are realy bad compared to nvidias) and played a nice round L4D with a friend of mine.
I realy hope there is no conspiracy theory and Andrews team had only some bad weeks *g*
So please Nvidia open your driver for all types of Display methods, stop to gag the customers by working on recognizing algorythms and put your full power in adding features! It will be a tough year in 3D stereoscopic business.
Edit: i saw that my Hl61A750 is recognized by windows as Samsung only not as Hl61A750, maybe that could be the problem?
[quote name='turls' post='986966' date='Jan 23 2010, 10:26 AM']The solution is not to try to fix every goofy thing for every one of how many dozens of devices this should work with. It is to allow us to override detection which we've been asking for for at least 2 months if not longer.
[DANGER, DANGER conspiracy theory]
I guess thats the strategy. Maybe Nvidia is licencing 3D Vision and try to bind the manufacturers to their GPUs. Samsung sold their great LED-DLP Tvs and found out that they are harming their sells because of cheap big screen entertainment. So they took them out of the market. Samsung agreed to cooperate with Nvidia with their new LCD-Displays and Samsung decided not to support DLP. Thats because of getting Customers fed up with not beeing able to get 3D working and force them to buy their new products. Which seems to work, as you can read here in forums.
[/DANGER, DANGER conspiracy theory]
But as can see small 23 inch displays suffer again of the ghosting problem. All i can say DLP-Checkerboard reduces resolution but there is absolutly no ghosting. LCD is a no go for me. I hope an inexpensive 1080p 120hz projector will hit the market soon. :)
What i did not to explode yesterday was deactivate 3D Vision, activated Iz3d driver, put on my $5 shutterlglasses (which are realy bad compared to nvidias) and played a nice round L4D with a friend of mine.
I realy hope there is no conspiracy theory and Andrews team had only some bad weeks *g*
So please Nvidia open your driver for all types of Display methods, stop to gag the customers by working on recognizing algorythms and put your full power in adding features! It will be a tough year in 3D stereoscopic business.
Edit: i saw that my Hl61A750 is recognized by windows as Samsung only not as Hl61A750, maybe that could be the problem?
IIRC, Andrew mentioned they did have Sammy DLP @ their lab.
Alright, the way I see this is as follows: I think that 'Engineering' is aware of the problem - evident by the driver release note, and they also declared in the release note that it's solved, it must mean that they had worked on it and thought that they had solved it. But as reality proved otherwise since 1.20 CD release yesterday, the problem has not been solved which must mean it's a difficult and elusive bug that needs to be reproduced exactly as it mafinests in user's setup. This I think is the basis of why Andrew asks user to assist, and I think the most sensible thing to do at this point. In addition I think once an user agree to lug in his computer, the system needs to be setup identically as it was at home, ie. dual monitors, one LCD, one DLP TV.
If there is no user system to help reproduce the bug, it will take a long time to track this sucker. Rolling back to 1.15 might not be a desirable step for them depending on who changed what and whether that engineer is still there. What I'm saying is by having an user to easily help reproduce the case is the easiest and fastest way at this point. The difficulty is of course is there any such user available.
[quote name='turls' post='986968' date='Jan 23 2010, 01:28 AM']And the 60" + DLP? I think they can do more than they have done remotely. Shouldn't need a local person to figure this out.[/quote]
IIRC, Andrew mentioned they did have Sammy DLP @ their lab.
Alright, the way I see this is as follows: I think that 'Engineering' is aware of the problem - evident by the driver release note, and they also declared in the release note that it's solved, it must mean that they had worked on it and thought that they had solved it. But as reality proved otherwise since 1.20 CD release yesterday, the problem has not been solved which must mean it's a difficult and elusive bug that needs to be reproduced exactly as it mafinests in user's setup. This I think is the basis of why Andrew asks user to assist, and I think the most sensible thing to do at this point. In addition I think once an user agree to lug in his computer, the system needs to be setup identically as it was at home, ie. dual monitors, one LCD, one DLP TV.
If there is no user system to help reproduce the bug, it will take a long time to track this sucker. Rolling back to 1.15 might not be a desirable step for them depending on who changed what and whether that engineer is still there. What I'm saying is by having an user to easily help reproduce the case is the easiest and fastest way at this point. The difficulty is of course is there any such user available.
[quote name='turls' post='986968' date='Jan 23 2010, 01:28 AM']And the 60" + DLP? I think they can do more than they have done remotely. Shouldn't need a local person to figure this out.
[quote name='turls' post='986966' date='Jan 23 2010, 02:26 AM']The solution is not to try to fix every goofy thing for every one of how many dozens of devices this should work with. It is to [b]allow us to override detection[/b] which we've been asking for for at least 2 months if not longer.[/quote]
nV is being extremely obstinate about letting us control our hardware at the power user level. I really don't know why they are acting this way, but it makes me feel like rebelling. We need a power user mode! I am a huge fan of stereo 3d gaming, but the clamping down on end user control is really starting to piss me off. /verymad.gif' class='bbc_emoticon' alt=':verymad:' />
[rant]
The whole concept of a company wanting to strictly control the implementation and use of the hardware from beginning to end to the detriment of the end user needs to die. It is something that has really started to get out of hand over the last decade or so. The last major consumer victory we had was against the MPAA when we were allowed to be able to use VCRs as we saw fit. Ever since then, we have seen nothing but corporate controls on the end consumer becoming much more common and draconian.
First nV makes it so that if I have the wrong companies hardware in my system, theirs' won't function correctly, and now they will strictly dictate the fashion in which I am allowed to enjoy 3d stereo gaming. Every company seems to want to sell us hardware at full price and then tell us exactly how to use it for the entire life of our purchase. No thank you... my heart rejoices at every hack and workaround that comes up to combat such draconian activities. It is a blow for the consumer in the war of taking back ownership of the products we purchase with our hard earned money.
It isn't just nV, of course, almost every single company wants a piece of the control pie, Apple, MS and Steam are strong examples. After all, we haven't pushed back so far fr consumer rights, so why not take whatever control they can.
[/rant]
[quote name='turls' post='986966' date='Jan 23 2010, 02:26 AM']The solution is not to try to fix every goofy thing for every one of how many dozens of devices this should work with. It is to allow us to override detection which we've been asking for for at least 2 months if not longer.
nV is being extremely obstinate about letting us control our hardware at the power user level. I really don't know why they are acting this way, but it makes me feel like rebelling. We need a power user mode! I am a huge fan of stereo 3d gaming, but the clamping down on end user control is really starting to piss me off. /verymad.gif' class='bbc_emoticon' alt=':verymad:' />
[rant]
The whole concept of a company wanting to strictly control the implementation and use of the hardware from beginning to end to the detriment of the end user needs to die. It is something that has really started to get out of hand over the last decade or so. The last major consumer victory we had was against the MPAA when we were allowed to be able to use VCRs as we saw fit. Ever since then, we have seen nothing but corporate controls on the end consumer becoming much more common and draconian.
First nV makes it so that if I have the wrong companies hardware in my system, theirs' won't function correctly, and now they will strictly dictate the fashion in which I am allowed to enjoy 3d stereo gaming. Every company seems to want to sell us hardware at full price and then tell us exactly how to use it for the entire life of our purchase. No thank you... my heart rejoices at every hack and workaround that comes up to combat such draconian activities. It is a blow for the consumer in the war of taking back ownership of the products we purchase with our hard earned money.
It isn't just nV, of course, almost every single company wants a piece of the control pie, Apple, MS and Steam are strong examples. After all, we haven't pushed back so far fr consumer rights, so why not take whatever control they can.
[/rant]
The human race divides politically into those who want people to be controlled and those who have no such desire.
This makes me really nervous. I spent almost $2000 on my dream pc, to specificaly play games in 3d, and went with the gtx295 sli because I thought the nvidia 3d kit was the best current option. But here's the catch, I have a samsung hl67a750. I was going to order the glasses this weekend, but now it looks like my best laid plans have gone to waste. Awesome...DDD here I come to your inferior product! Because you work! /confused.gif' class='bbc_emoticon' alt=':confused:' />
This makes me really nervous. I spent almost $2000 on my dream pc, to specificaly play games in 3d, and went with the gtx295 sli because I thought the nvidia 3d kit was the best current option. But here's the catch, I have a samsung hl67a750. I was going to order the glasses this weekend, but now it looks like my best laid plans have gone to waste. Awesome...DDD here I come to your inferior product! Because you work! /confused.gif' class='bbc_emoticon' alt=':confused:' />
Asus Maximus Hero VII
i7 4790k @ 4.8ghz
SLI MSI Gaming 980 @ 1.5ghz
16gb Gskill @ 2400mhz
2x Samsung 840 500gb
Corsair HX1000i
Custom water loop
un78hu9000 with 3dplay on checkerboard 1080p
[quote name='VadersApp2' post='986997' date='Jan 23 2010, 04:21 AM']Edit: i saw that my Hl61A750 is recognized by windows as Samsung only not as Hl61A750, maybe that could be the problem?[/quote]
But it has always been that way, and 1.15 and below, it was fine.
[quote name='distant' post='987170' date='Jan 23 2010, 11:15 AM']IIRC, Andrew mentioned they did have Sammy DLP @ their lab.
Alright, the way I see this is as follows: I think that 'Engineering' is aware of the problem - evident by the driver release note, and they also declared in the release note that it's solved, it must mean that they had worked on it and thought that they had solved it. But as reality proved otherwise since 1.20 CD release yesterday, the problem has not been solved which must mean it's a difficult and elusive bug that needs to be reproduced exactly as it mafinests in user's setup. This I think is the basis of why Andrew asks user to assist, and I think the most sensible thing to do at this point. In addition I think once an user agree to lug in his computer, the system needs to be setup identically as it was at home, ie. dual monitors, one LCD, one DLP TV.
If there is no user system to help reproduce the bug, it will take a long time to track this sucker. Rolling back to 1.15 might not be a desirable step for them depending on who changed what and whether that engineer is still there. What I'm saying is by having an user to easily help reproduce the case is the easiest and fastest way at this point. The difficulty is of course is there any such user available.[/quote]
They have a Sammy DLP, just not the newest LED ones. I'm not sure if the previous gen LED ones detect or not, but we know at least some Sammy DLPs work from user reports here. That's where part of the confusion is, is that they have it working on their DLP for 1.19, so it must work for all Sammy DLPs. I don't believe they did anything between 1.19 and 1.20 on detection. Similar to how they have their hardware working without the ghosting/sync issues with the projectors in their labs, so it must work for everybody, even though not every projector is exactly the same. They were told in mid-December (Andrew was in on the conversations here) that it didn't work on the HL series, but I'm not sure they believed it then, they might believe it now, but it doesn't sound like they are trying to actively fix it, if what they are asking for is a local person to contact them. Your whole scenario to get this fixed is ridiculous you have to admit, and what happens when they break it again for us or others. [b]Give us control to override the detection[/b], if they won't do that, honestly we might as well sell our setups now.
[quote name='VadersApp2' post='986997' date='Jan 23 2010, 04:21 AM']Edit: i saw that my Hl61A750 is recognized by windows as Samsung only not as Hl61A750, maybe that could be the problem?
But it has always been that way, and 1.15 and below, it was fine.
[quote name='distant' post='987170' date='Jan 23 2010, 11:15 AM']IIRC, Andrew mentioned they did have Sammy DLP @ their lab.
Alright, the way I see this is as follows: I think that 'Engineering' is aware of the problem - evident by the driver release note, and they also declared in the release note that it's solved, it must mean that they had worked on it and thought that they had solved it. But as reality proved otherwise since 1.20 CD release yesterday, the problem has not been solved which must mean it's a difficult and elusive bug that needs to be reproduced exactly as it mafinests in user's setup. This I think is the basis of why Andrew asks user to assist, and I think the most sensible thing to do at this point. In addition I think once an user agree to lug in his computer, the system needs to be setup identically as it was at home, ie. dual monitors, one LCD, one DLP TV.
If there is no user system to help reproduce the bug, it will take a long time to track this sucker. Rolling back to 1.15 might not be a desirable step for them depending on who changed what and whether that engineer is still there. What I'm saying is by having an user to easily help reproduce the case is the easiest and fastest way at this point. The difficulty is of course is there any such user available.
They have a Sammy DLP, just not the newest LED ones. I'm not sure if the previous gen LED ones detect or not, but we know at least some Sammy DLPs work from user reports here. That's where part of the confusion is, is that they have it working on their DLP for 1.19, so it must work for all Sammy DLPs. I don't believe they did anything between 1.19 and 1.20 on detection. Similar to how they have their hardware working without the ghosting/sync issues with the projectors in their labs, so it must work for everybody, even though not every projector is exactly the same. They were told in mid-December (Andrew was in on the conversations here) that it didn't work on the HL series, but I'm not sure they believed it then, they might believe it now, but it doesn't sound like they are trying to actively fix it, if what they are asking for is a local person to contact them. Your whole scenario to get this fixed is ridiculous you have to admit, and what happens when they break it again for us or others. Give us control to override the detection, if they won't do that, honestly we might as well sell our setups now.
Did you mean "[color="#0000ff"][b]their[/b][/color]" scenario? Because I didn't propose it.
Though if given that 'engineering' had tried all their guile and still couldn't fix then the next logical step must be 'reproducing' the problem as it really occurs, there is just no easy way out. And the most accurate way to do that is to have an user setup, assuming Nv does have a LED based Sammy DLP in their lab. In case Nv doesn't have one then we're considered screwed for good if they decided not to go back to 1.15 detection scheme.
[quote name='turls' post='987661' date='Jan 24 2010, 04:23 AM']. ..
[color="#4169e1"][b]Your[/b][/color] whole scenario to get this fixed is ridiculous you have to admit, and what happens when they break it again for us or others. [b]Give us control to override the detection[/b], if they won't do that, honestly we might as well sell our setups now.[/quote]
Did you mean "their" scenario? Because I didn't propose it.
Though if given that 'engineering' had tried all their guile and still couldn't fix then the next logical step must be 'reproducing' the problem as it really occurs, there is just no easy way out. And the most accurate way to do that is to have an user setup, assuming Nv does have a LED based Sammy DLP in their lab. In case Nv doesn't have one then we're considered screwed for good if they decided not to go back to 1.15 detection scheme.
Your whole scenario to get this fixed is ridiculous you have to admit, and what happens when they break it again for us or others. Give us control to override the detection, if they won't do that, honestly we might as well sell our setups now.
- Fixed a bug with the driver that prevented Generic DLP mode from working. This should allow Samsung DLP users the ability to use 3D Vision again.
I was happy that it should work now.
But after Installation was done i wasn´t able to choose Generic DLP again!
"crap" i thought and tried the previous trick only to learn that this bug was fixed :)
Nividia you are joking or not?
Uninstalled everything and installed gpu driver and stereo driver. Again only frackn discoverer! Maybe Andrew your team forgot to add support for HL61a750 users ?
After all the problems the new driver (3d Vision Driver) made wouldn´t it be better to open it for all display methods as the old (ELSAs) one did?
Maybe the other big player in the GPU industry will make that better in future driver revisions...
- Fixed a bug with the driver that prevented Generic DLP mode from working. This should allow Samsung DLP users the ability to use 3D Vision again.
I was happy that it should work now.
But after Installation was done i wasn´t able to choose Generic DLP again!
"crap" i thought and tried the previous trick only to learn that this bug was fixed :)
Nividia you are joking or not?
Uninstalled everything and installed gpu driver and stereo driver. Again only frackn discoverer! Maybe Andrew your team forgot to add support for HL61a750 users ?
After all the problems the new driver (3d Vision Driver) made wouldn´t it be better to open it for all display methods as the old (ELSAs) one did?
Maybe the other big player in the GPU industry will make that better in future driver revisions...
- Fixed a bug with the driver that prevented Generic DLP mode from working. This should allow Samsung DLP users the ability to use 3D Vision again.
I was happy that it should work now.
But after Installation was done i wasn´t able to choose Generic DLP again!
"crap" i thought and tried the previous trick only to learn that this bug was fixed :)
Nividia you are joking or not?
Uninstalled everything and installed gpu driver and stereo driver. Again only frackn discoverer! Maybe Andrew your team forgot to add support for HL61a750 users ?
After all the problems the new driver (3d Vision Driver) made wouldn´t it be better to open it for all display methods as the old (ELSAs) one did?
Maybe the other big player in the GPU industry will make that better in future driver revisions...[/quote]
Where did you download driver 1.20. I cant seem to find the driver, the newest is only 1.19?
EDIT
Okay got it.
[url="http://www.nvidia.com/content/DriverDownload-March2009/confirmation.php?url=/Windows/3d_vision_stereo/NVIDIA_3D_Vision_CD_v1.20_WinVista_Win7_English.zip&lang=us&type=Other"]http://www.nvidia.com/content/DriverDownlo...&type=Other[/url]
- Fixed a bug with the driver that prevented Generic DLP mode from working. This should allow Samsung DLP users the ability to use 3D Vision again.
I was happy that it should work now.
But after Installation was done i wasn´t able to choose Generic DLP again!
"crap" i thought and tried the previous trick only to learn that this bug was fixed :)
Nividia you are joking or not?
Uninstalled everything and installed gpu driver and stereo driver. Again only frackn discoverer! Maybe Andrew your team forgot to add support for HL61a750 users ?
After all the problems the new driver (3d Vision Driver) made wouldn´t it be better to open it for all display methods as the old (ELSAs) one did?
Maybe the other big player in the GPU industry will make that better in future driver revisions...
Where did you download driver 1.20. I cant seem to find the driver, the newest is only 1.19?
EDIT
Okay got it.
http://www.nvidia.com/content/DriverDownlo...&type=Other
Peculiar thing is though the download driver search is showing it's not ready "try later" message so I'm thinking I should wait for it instead of installing from the link above given that vaderapp got even worse problem with the 1.20 than the 1.19 and the workaround that works for 1.19 no longer works for 1.20.
Peculiar thing is though the download driver search is showing it's not ready "try later" message so I'm thinking I should wait for it instead of installing from the link above given that vaderapp got even worse problem with the 1.20 than the 1.19 and the workaround that works for 1.19 no longer works for 1.20.
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+
Peculiar thing is though the download driver search is showing it's not ready "try later" message so I'm thinking I should wait for it instead of installing from the link above given that vaderapp got even worse problem with the 1.20 than the 1.19 and the workaround that works for 1.19 no longer works for 1.20.[/quote]
I don't know how they are going to have it fixed in 1.20 when as of this past Monday they still thought they fixed everything for Samsung DLP in 1.19. That would be one heck of a turnaround time. What they should have done (maybe they still will) is delay any further updates until they nail this bug that should have been fixed 3 months ago!
Peculiar thing is though the download driver search is showing it's not ready "try later" message so I'm thinking I should wait for it instead of installing from the link above given that vaderapp got even worse problem with the 1.20 than the 1.19 and the workaround that works for 1.19 no longer works for 1.20.
I don't know how they are going to have it fixed in 1.20 when as of this past Monday they still thought they fixed everything for Samsung DLP in 1.19. That would be one heck of a turnaround time. What they should have done (maybe they still will) is delay any further updates until they nail this bug that should have been fixed 3 months ago!
Just thought I'd add no Samsung DLP love with the 1.20 for my HL61A750A. No detection. Oh well, I've reinstalled 1.15 which are the last drivers to detect my DLP.
Just thought I'd add no Samsung DLP love with the 1.20 for my HL61A750A. No detection. Oh well, I've reinstalled 1.15 which are the last drivers to detect my DLP.
We apologize for this. I really cant explain why its not working.
Is there anyone in the Santa Clara, CA or Austin, TX area that wants to come by the office for some debugging fun? PM me!
We apologize for this. I really cant explain why its not working.
Is there anyone in the Santa Clara, CA or Austin, TX area that wants to come by the office for some debugging fun? PM me!
[b]CONFIRMED THAT 1.20 CD STILL DOES [color="#ff00ff"]NOT[/color] DETECT SAMSUNG DLP!
[color="#000000"][i]WORSE[/i][/color], THE WORKAROUND NO LONGER FREAKING WORKS.
[/b]My 3D Vision product is now officially Windows certified [b]USELESS![/b]
Thank you Nvidia for a fine, fine driver release yet again.
EDIT: Didn't see Andrew's post above before posting mine. Well, it's good venting anyway. But in light of Andrew's post whose spirit is just great, hope someone in the above locales can assist with the debugging, probably have to lug in the computer I imagine.
CONFIRMED THAT 1.20 CD STILL DOES NOT DETECT SAMSUNG DLP!
WORSE, THE WORKAROUND NO LONGER FREAKING WORKS.
My 3D Vision product is now officially Windows certified USELESS!
Thank you Nvidia for a fine, fine driver release yet again.
EDIT: Didn't see Andrew's post above before posting mine. Well, it's good venting anyway. But in light of Andrew's post whose spirit is just great, hope someone in the above locales can assist with the debugging, probably have to lug in the computer I imagine.
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+
We apologize for this. I really cant explain why its not working.
Is there anyone in the Santa Clara, CA or Austin, TX area that wants to come by the office for some debugging fun? PM me![/quote]
I don't get it. We understand you don't have every device in office to test. I've offered to help remotely previously but nobody has taken me up on it.
The solution is not to try to fix every goofy thing for every one of how many dozens of devices this should work with. It is to [b]allow us to override detection[/b] which we've been asking for for at least 2 months if not longer.
Why can't we just get a response on why this is or isn't possible? Sounds like right now we are dead in the water with no hope of getting something fixed that used to work before they messed with the dual monitors. Why can't somebody just go back and figure out what changed after 1.15 also? Has anybody even checked that?
We apologize for this. I really cant explain why its not working.
Is there anyone in the Santa Clara, CA or Austin, TX area that wants to come by the office for some debugging fun? PM me!
I don't get it. We understand you don't have every device in office to test. I've offered to help remotely previously but nobody has taken me up on it.
The solution is not to try to fix every goofy thing for every one of how many dozens of devices this should work with. It is to allow us to override detection which we've been asking for for at least 2 months if not longer.
Why can't we just get a response on why this is or isn't possible? Sounds like right now we are dead in the water with no hope of getting something fixed that used to work before they messed with the dual monitors. Why can't somebody just go back and figure out what changed after 1.15 also? Has anybody even checked that?
And the 60" + DLP? I think they can do more than they have done remotely. Shouldn't need a local person to figure this out.
And the 60" + DLP? I think they can do more than they have done remotely. Shouldn't need a local person to figure this out.
[DANGER, DANGER conspiracy theory]
I guess thats the strategy. Maybe Nvidia is licencing 3D Vision and try to bind the manufacturers to their GPUs. Samsung sold their great LED-DLP Tvs and found out that they are harming their sells because of cheap big screen entertainment. So they took them out of the market. Samsung agreed to cooperate with Nvidia with their new LCD-Displays and Samsung decided not to support DLP. Thats because of getting Customers fed up with not beeing able to get 3D working and force them to buy their new products. Which seems to work, as you can read here in forums.
[/DANGER, DANGER conspiracy theory]
But as can see small 23 inch displays suffer again of the ghosting problem. All i can say DLP-Checkerboard reduces resolution but there is absolutly no ghosting. LCD is a no go for me. I hope an inexpensive 1080p 120hz projector will hit the market soon. :)
What i did not to explode yesterday was deactivate 3D Vision, activated Iz3d driver, put on my $5 shutterlglasses (which are realy bad compared to nvidias) and played a nice round L4D with a friend of mine.
I realy hope there is no conspiracy theory and Andrews team had only some bad weeks *g*
So please Nvidia open your driver for all types of Display methods, stop to gag the customers by working on recognizing algorythms and put your full power in adding features! It will be a tough year in 3D stereoscopic business.
Edit: i saw that my Hl61A750 is recognized by windows as Samsung only not as Hl61A750, maybe that could be the problem?
[DANGER, DANGER conspiracy theory]
I guess thats the strategy. Maybe Nvidia is licencing 3D Vision and try to bind the manufacturers to their GPUs. Samsung sold their great LED-DLP Tvs and found out that they are harming their sells because of cheap big screen entertainment. So they took them out of the market. Samsung agreed to cooperate with Nvidia with their new LCD-Displays and Samsung decided not to support DLP. Thats because of getting Customers fed up with not beeing able to get 3D working and force them to buy their new products. Which seems to work, as you can read here in forums.
[/DANGER, DANGER conspiracy theory]
But as can see small 23 inch displays suffer again of the ghosting problem. All i can say DLP-Checkerboard reduces resolution but there is absolutly no ghosting. LCD is a no go for me. I hope an inexpensive 1080p 120hz projector will hit the market soon. :)
What i did not to explode yesterday was deactivate 3D Vision, activated Iz3d driver, put on my $5 shutterlglasses (which are realy bad compared to nvidias) and played a nice round L4D with a friend of mine.
I realy hope there is no conspiracy theory and Andrews team had only some bad weeks *g*
So please Nvidia open your driver for all types of Display methods, stop to gag the customers by working on recognizing algorythms and put your full power in adding features! It will be a tough year in 3D stereoscopic business.
Edit: i saw that my Hl61A750 is recognized by windows as Samsung only not as Hl61A750, maybe that could be the problem?
Alright, the way I see this is as follows: I think that 'Engineering' is aware of the problem - evident by the driver release note, and they also declared in the release note that it's solved, it must mean that they had worked on it and thought that they had solved it. But as reality proved otherwise since 1.20 CD release yesterday, the problem has not been solved which must mean it's a difficult and elusive bug that needs to be reproduced exactly as it mafinests in user's setup. This I think is the basis of why Andrew asks user to assist, and I think the most sensible thing to do at this point. In addition I think once an user agree to lug in his computer, the system needs to be setup identically as it was at home, ie. dual monitors, one LCD, one DLP TV.
If there is no user system to help reproduce the bug, it will take a long time to track this sucker. Rolling back to 1.15 might not be a desirable step for them depending on who changed what and whether that engineer is still there. What I'm saying is by having an user to easily help reproduce the case is the easiest and fastest way at this point. The difficulty is of course is there any such user available.
[quote name='turls' post='986968' date='Jan 23 2010, 01:28 AM']And the 60" + DLP? I think they can do more than they have done remotely. Shouldn't need a local person to figure this out.[/quote]
Alright, the way I see this is as follows: I think that 'Engineering' is aware of the problem - evident by the driver release note, and they also declared in the release note that it's solved, it must mean that they had worked on it and thought that they had solved it. But as reality proved otherwise since 1.20 CD release yesterday, the problem has not been solved which must mean it's a difficult and elusive bug that needs to be reproduced exactly as it mafinests in user's setup. This I think is the basis of why Andrew asks user to assist, and I think the most sensible thing to do at this point. In addition I think once an user agree to lug in his computer, the system needs to be setup identically as it was at home, ie. dual monitors, one LCD, one DLP TV.
If there is no user system to help reproduce the bug, it will take a long time to track this sucker. Rolling back to 1.15 might not be a desirable step for them depending on who changed what and whether that engineer is still there. What I'm saying is by having an user to easily help reproduce the case is the easiest and fastest way at this point. The difficulty is of course is there any such user available.
[quote name='turls' post='986968' date='Jan 23 2010, 01:28 AM']And the 60" + DLP? I think they can do more than they have done remotely. Shouldn't need a local person to figure this out.
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+
nV is being extremely obstinate about letting us control our hardware at the power user level. I really don't know why they are acting this way, but it makes me feel like rebelling. We need a power user mode! I am a huge fan of stereo 3d gaming, but the clamping down on end user control is really starting to piss me off.
[rant]
The whole concept of a company wanting to strictly control the implementation and use of the hardware from beginning to end to the detriment of the end user needs to die. It is something that has really started to get out of hand over the last decade or so. The last major consumer victory we had was against the MPAA when we were allowed to be able to use VCRs as we saw fit. Ever since then, we have seen nothing but corporate controls on the end consumer becoming much more common and draconian.
First nV makes it so that if I have the wrong companies hardware in my system, theirs' won't function correctly, and now they will strictly dictate the fashion in which I am allowed to enjoy 3d stereo gaming. Every company seems to want to sell us hardware at full price and then tell us exactly how to use it for the entire life of our purchase. No thank you... my heart rejoices at every hack and workaround that comes up to combat such draconian activities. It is a blow for the consumer in the war of taking back ownership of the products we purchase with our hard earned money.
It isn't just nV, of course, almost every single company wants a piece of the control pie, Apple, MS and Steam are strong examples. After all, we haven't pushed back so far fr consumer rights, so why not take whatever control they can.
[/rant]
nV is being extremely obstinate about letting us control our hardware at the power user level. I really don't know why they are acting this way, but it makes me feel like rebelling. We need a power user mode! I am a huge fan of stereo 3d gaming, but the clamping down on end user control is really starting to piss me off.
[rant]
The whole concept of a company wanting to strictly control the implementation and use of the hardware from beginning to end to the detriment of the end user needs to die. It is something that has really started to get out of hand over the last decade or so. The last major consumer victory we had was against the MPAA when we were allowed to be able to use VCRs as we saw fit. Ever since then, we have seen nothing but corporate controls on the end consumer becoming much more common and draconian.
First nV makes it so that if I have the wrong companies hardware in my system, theirs' won't function correctly, and now they will strictly dictate the fashion in which I am allowed to enjoy 3d stereo gaming. Every company seems to want to sell us hardware at full price and then tell us exactly how to use it for the entire life of our purchase. No thank you... my heart rejoices at every hack and workaround that comes up to combat such draconian activities. It is a blow for the consumer in the war of taking back ownership of the products we purchase with our hard earned money.
It isn't just nV, of course, almost every single company wants a piece of the control pie, Apple, MS and Steam are strong examples. After all, we haven't pushed back so far fr consumer rights, so why not take whatever control they can.
[/rant]
The human race divides politically into those who want people to be controlled and those who have no such desire.
--Robert A. Heinlein
Asus Maximus Hero VII
i7 4790k @ 4.8ghz
SLI MSI Gaming 980 @ 1.5ghz
16gb Gskill @ 2400mhz
2x Samsung 840 500gb
Corsair HX1000i
Custom water loop
un78hu9000 with 3dplay on checkerboard 1080p
But it has always been that way, and 1.15 and below, it was fine.
[quote name='distant' post='987170' date='Jan 23 2010, 11:15 AM']IIRC, Andrew mentioned they did have Sammy DLP @ their lab.
Alright, the way I see this is as follows: I think that 'Engineering' is aware of the problem - evident by the driver release note, and they also declared in the release note that it's solved, it must mean that they had worked on it and thought that they had solved it. But as reality proved otherwise since 1.20 CD release yesterday, the problem has not been solved which must mean it's a difficult and elusive bug that needs to be reproduced exactly as it mafinests in user's setup. This I think is the basis of why Andrew asks user to assist, and I think the most sensible thing to do at this point. In addition I think once an user agree to lug in his computer, the system needs to be setup identically as it was at home, ie. dual monitors, one LCD, one DLP TV.
If there is no user system to help reproduce the bug, it will take a long time to track this sucker. Rolling back to 1.15 might not be a desirable step for them depending on who changed what and whether that engineer is still there. What I'm saying is by having an user to easily help reproduce the case is the easiest and fastest way at this point. The difficulty is of course is there any such user available.[/quote]
They have a Sammy DLP, just not the newest LED ones. I'm not sure if the previous gen LED ones detect or not, but we know at least some Sammy DLPs work from user reports here. That's where part of the confusion is, is that they have it working on their DLP for 1.19, so it must work for all Sammy DLPs. I don't believe they did anything between 1.19 and 1.20 on detection. Similar to how they have their hardware working without the ghosting/sync issues with the projectors in their labs, so it must work for everybody, even though not every projector is exactly the same. They were told in mid-December (Andrew was in on the conversations here) that it didn't work on the HL series, but I'm not sure they believed it then, they might believe it now, but it doesn't sound like they are trying to actively fix it, if what they are asking for is a local person to contact them. Your whole scenario to get this fixed is ridiculous you have to admit, and what happens when they break it again for us or others. [b]Give us control to override the detection[/b], if they won't do that, honestly we might as well sell our setups now.
But it has always been that way, and 1.15 and below, it was fine.
[quote name='distant' post='987170' date='Jan 23 2010, 11:15 AM']IIRC, Andrew mentioned they did have Sammy DLP @ their lab.
Alright, the way I see this is as follows: I think that 'Engineering' is aware of the problem - evident by the driver release note, and they also declared in the release note that it's solved, it must mean that they had worked on it and thought that they had solved it. But as reality proved otherwise since 1.20 CD release yesterday, the problem has not been solved which must mean it's a difficult and elusive bug that needs to be reproduced exactly as it mafinests in user's setup. This I think is the basis of why Andrew asks user to assist, and I think the most sensible thing to do at this point. In addition I think once an user agree to lug in his computer, the system needs to be setup identically as it was at home, ie. dual monitors, one LCD, one DLP TV.
If there is no user system to help reproduce the bug, it will take a long time to track this sucker. Rolling back to 1.15 might not be a desirable step for them depending on who changed what and whether that engineer is still there. What I'm saying is by having an user to easily help reproduce the case is the easiest and fastest way at this point. The difficulty is of course is there any such user available.
They have a Sammy DLP, just not the newest LED ones. I'm not sure if the previous gen LED ones detect or not, but we know at least some Sammy DLPs work from user reports here. That's where part of the confusion is, is that they have it working on their DLP for 1.19, so it must work for all Sammy DLPs. I don't believe they did anything between 1.19 and 1.20 on detection. Similar to how they have their hardware working without the ghosting/sync issues with the projectors in their labs, so it must work for everybody, even though not every projector is exactly the same. They were told in mid-December (Andrew was in on the conversations here) that it didn't work on the HL series, but I'm not sure they believed it then, they might believe it now, but it doesn't sound like they are trying to actively fix it, if what they are asking for is a local person to contact them. Your whole scenario to get this fixed is ridiculous you have to admit, and what happens when they break it again for us or others. Give us control to override the detection, if they won't do that, honestly we might as well sell our setups now.
Though if given that 'engineering' had tried all their guile and still couldn't fix then the next logical step must be 'reproducing' the problem as it really occurs, there is just no easy way out. And the most accurate way to do that is to have an user setup, assuming Nv does have a LED based Sammy DLP in their lab. In case Nv doesn't have one then we're considered screwed for good if they decided not to go back to 1.15 detection scheme.
[quote name='turls' post='987661' date='Jan 24 2010, 04:23 AM']. ..
[color="#4169e1"][b]Your[/b][/color] whole scenario to get this fixed is ridiculous you have to admit, and what happens when they break it again for us or others. [b]Give us control to override the detection[/b], if they won't do that, honestly we might as well sell our setups now.[/quote]
Though if given that 'engineering' had tried all their guile and still couldn't fix then the next logical step must be 'reproducing' the problem as it really occurs, there is just no easy way out. And the most accurate way to do that is to have an user setup, assuming Nv does have a LED based Sammy DLP in their lab. In case Nv doesn't have one then we're considered screwed for good if they decided not to go back to 1.15 detection scheme.
[quote name='turls' post='987661' date='Jan 24 2010, 04:23 AM']. ..
Your whole scenario to get this fixed is ridiculous you have to admit, and what happens when they break it again for us or others. Give us control to override the detection, if they won't do that, honestly we might as well sell our setups now.
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+