HL61A750/HL67A750 3D Vision tips
  1 / 2    
Might apply to other 3D ready Samsung sets as well. Some of this may have been posted before.

Biggest tip: Use the "tools" menu to switch into 3D. It saves a bunch of key presses vs. the regular menus.

If you lose the menu choice for 3D, you may be sending a signal that is "deep color" which I think is the problem I ran into when I tried the unsupported patch. I think it somehow got stuck in that mode, and it broke the option for 3D on the Samsung. Before you load 3D, you have the choice to do either standard or "deep color" for your output, but that option is removed when you load the stereo drivers. At least, that's the only thing I could figure out was the issue.

The patch did work for overscan, temporarily, but something broke. I'm hoping NVidia figures this one out because I much prefer many games without overscan because of HUD cutoff mainly. More games need the HTPC overscan friendly options Halo 2 has.

I did not have any luck with the setting during setup that is supposed to be used if you have other IR being used in a room (a typical HTPC environment). During the day in a bright room, the flicker was "skipping" in the right eye and it was horrible. Does anybody have any experience with just using the regular setting causing a problem?
Might apply to other 3D ready Samsung sets as well. Some of this may have been posted before.



Biggest tip: Use the "tools" menu to switch into 3D. It saves a bunch of key presses vs. the regular menus.



If you lose the menu choice for 3D, you may be sending a signal that is "deep color" which I think is the problem I ran into when I tried the unsupported patch. I think it somehow got stuck in that mode, and it broke the option for 3D on the Samsung. Before you load 3D, you have the choice to do either standard or "deep color" for your output, but that option is removed when you load the stereo drivers. At least, that's the only thing I could figure out was the issue.



The patch did work for overscan, temporarily, but something broke. I'm hoping NVidia figures this one out because I much prefer many games without overscan because of HUD cutoff mainly. More games need the HTPC overscan friendly options Halo 2 has.



I did not have any luck with the setting during setup that is supposed to be used if you have other IR being used in a room (a typical HTPC environment). During the day in a bright room, the flicker was "skipping" in the right eye and it was horrible. Does anybody have any experience with just using the regular setting causing a problem?

#1
Posted 04/10/2009 05:03 AM   
Only time I can get the 3D option is when I set the HDMI color options in the Nvidia control panel to "RGB". Samsung manual states that RGB is needed for 3D. Thanks for the tools tip, it works great and makes things much quicker.

As for playing in daytime, I usually don't(work and all), but I'm off today so perhaps I'll give it a go. The overscan problem you have I have as well even with my desktop. It's the nature of the beast since we don't have 1:1 pixel mapping like LCDs. you can try resizing in the Nvidia control panel, but it usually fuzzes things up. Or you can just change the screen size from the TV to PC which gives some black borders on my 67"
Only time I can get the 3D option is when I set the HDMI color options in the Nvidia control panel to "RGB". Samsung manual states that RGB is needed for 3D. Thanks for the tools tip, it works great and makes things much quicker.



As for playing in daytime, I usually don't(work and all), but I'm off today so perhaps I'll give it a go. The overscan problem you have I have as well even with my desktop. It's the nature of the beast since we don't have 1:1 pixel mapping like LCDs. you can try resizing in the Nvidia control panel, but it usually fuzzes things up. Or you can just change the screen size from the TV to PC which gives some black borders on my 67"

#2
Posted 04/12/2009 08:14 PM   
[quote name='Bahn Yuki' post='529422' date='Apr 12 2009, 03:14 PM']Only time I can get the 3D option is when I set the HDMI color options in the Nvidia control panel to "RGB". Samsung manual states that RGB is needed for 3D. Thanks for the tools tip, it works great and makes things much quicker.[/quote]

Right, but the problem is many times that option is greyed out. Its working for me right now, but since I don't know why it is there sometimes and not others, it may cause problems again.

[quote]As for playing in daytime, I usually don't(work and all), but I'm off today so perhaps I'll give it a go. The overscan problem you have I have as well even with my desktop. It's the nature of the beast since we don't have 1:1 pixel mapping like LCDs. you can try resizing in the Nvidia control panel, but it usually fuzzes things up. Or you can just change the screen size from the TV to PC which gives some black borders on my 67"[/quote]

Yeah, I've setup my Harmony One remote to have a "pic size" hot key in any mode I use my HTPC in (I have 3 different choices now, Media Center, Play BD, and Play HTPC), because yes it makes it fuzzy but it is preferable in some cases. Problem is, on Mits DLP there is a fix for this. On Sammy DLP there is not. So yes I think the problem is 1:1 pixel mapping (or lack of it), but there are workarounds for Mits, so there should be an eventual "fix" for Sammy DLP as well. Like I've said in other posts its the one remaining major issue that I know of with Sammy DLP and 3D Vision.
[quote name='Bahn Yuki' post='529422' date='Apr 12 2009, 03:14 PM']Only time I can get the 3D option is when I set the HDMI color options in the Nvidia control panel to "RGB". Samsung manual states that RGB is needed for 3D. Thanks for the tools tip, it works great and makes things much quicker.



Right, but the problem is many times that option is greyed out. Its working for me right now, but since I don't know why it is there sometimes and not others, it may cause problems again.



As for playing in daytime, I usually don't(work and all), but I'm off today so perhaps I'll give it a go. The overscan problem you have I have as well even with my desktop. It's the nature of the beast since we don't have 1:1 pixel mapping like LCDs. you can try resizing in the Nvidia control panel, but it usually fuzzes things up. Or you can just change the screen size from the TV to PC which gives some black borders on my 67"




Yeah, I've setup my Harmony One remote to have a "pic size" hot key in any mode I use my HTPC in (I have 3 different choices now, Media Center, Play BD, and Play HTPC), because yes it makes it fuzzy but it is preferable in some cases. Problem is, on Mits DLP there is a fix for this. On Sammy DLP there is not. So yes I think the problem is 1:1 pixel mapping (or lack of it), but there are workarounds for Mits, so there should be an eventual "fix" for Sammy DLP as well. Like I've said in other posts its the one remaining major issue that I know of with Sammy DLP and 3D Vision.

#3
Posted 04/16/2009 08:09 PM   
Another tip for these TVs is to make sure and label the input as "PC" in the TV menu. It actually does help.
Another tip for these TVs is to make sure and label the input as "PC" in the TV menu. It actually does help.

#4
Posted 04/17/2009 06:32 PM   
Hi

Let me take a stab at the 1:1 pixel mapping question.

FACTS
- DLPs use a checkboard pattern 3D mode to run in 3D mode that requires no changing of the pixel sizes. Changing this will break the 3D pattern and cause it to no longer work.
- Most HDTVs typically apply overscan the signal they receive. Overscan means that they "cut off" areas some around the screen edge under the bezel. For a video, or movie you typically wont notice it since that's where a broadcaster puts line 21 data. However for a PC, that cuts of in-game menus, HUDs, and the Windows start bar. The default NVIDIA driver does have an underscan tool to resize the desktop and allow you to see full details. HOWEVER, this default underscan option breaks 3D!!

SOLUTION
- We posted a[url="http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=2370&p_created=1234213386&p_sid=lkcT7MAj&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MTAsMTAmcF9wcm9kcz0xMzImcF9jYXRzPTAmcF9wdj0xLjEzMiZwX2N2PSZwX3NlYXJjaF90eXBlPWFuc3dlcnMuc2VhcmNoX25sJnBfcGFnZT0xJnBfc2VhcmNoX3RleHQ9aGR0dg**&p_li=&p_topview=1"] DLP underscsan fix [/url]a while back which changes how that underscan function works. I know the Knowledge Base Article says certain Samsung users shouldnt try it, but I would like them to try it now.
Hi



Let me take a stab at the 1:1 pixel mapping question.



FACTS

- DLPs use a checkboard pattern 3D mode to run in 3D mode that requires no changing of the pixel sizes. Changing this will break the 3D pattern and cause it to no longer work.

- Most HDTVs typically apply overscan the signal they receive. Overscan means that they "cut off" areas some around the screen edge under the bezel. For a video, or movie you typically wont notice it since that's where a broadcaster puts line 21 data. However for a PC, that cuts of in-game menus, HUDs, and the Windows start bar. The default NVIDIA driver does have an underscan tool to resize the desktop and allow you to see full details. HOWEVER, this default underscan option breaks 3D!!



SOLUTION

- We posted a DLP underscsan fix a while back which changes how that underscan function works. I know the Knowledge Base Article says certain Samsung users shouldnt try it, but I would like them to try it now.

#5
Posted 06/19/2009 05:20 PM   
[quote name='andrewf@nvidia' post='554733' date='Jun 19 2009, 12:20 PM']SOLUTION
- We posted a[url="http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=2370&p_created=1234213386&p_sid=lkcT7MAj&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MTAsMTAmcF9wcm9kcz0xMzImcF9jYXRzPTAmcF9wdj0xLjEzMiZwX2N2PSZwX3NlYXJjaF90eXBlPWFuc3dlcnMuc2VhcmNoX25sJnBfcGFnZT0xJnBfc2VhcmNoX3RleHQ9aGR0dg**&p_li=&p_topview=1"] DLP underscsan fix [/url]a while back which changes how that underscan function works. I know the Knowledge Base Article says certain Samsung users shouldnt try it, but I would like them to try it now.[/quote]

Ok, I found this post after I just responded a minute ago to the other thread. Interesting I was pretty close in my understanding before reading this from you which helps A TON! THANKS!

In any case, is there any reason that a newer driver version would work better with Samsung DLP because I did already try the hot fix a couple of months ago and I got it to work briefly but ran into issues which caused me to have to uninstall the drivers completely and reload them.

I will try it again though if you think there is a chance a newer driver will work better. . .

Would I be better off trying under Vista x64 or Win7 x64? Sorry I don't have a way to test x86.
[quote name='andrewf@nvidia' post='554733' date='Jun 19 2009, 12:20 PM']SOLUTION

- We posted a DLP underscsan fix a while back which changes how that underscan function works. I know the Knowledge Base Article says certain Samsung users shouldnt try it, but I would like them to try it now.



Ok, I found this post after I just responded a minute ago to the other thread. Interesting I was pretty close in my understanding before reading this from you which helps A TON! THANKS!



In any case, is there any reason that a newer driver version would work better with Samsung DLP because I did already try the hot fix a couple of months ago and I got it to work briefly but ran into issues which caused me to have to uninstall the drivers completely and reload them.



I will try it again though if you think there is a chance a newer driver will work better. . .



Would I be better off trying under Vista x64 or Win7 x64? Sorry I don't have a way to test x86.

#6
Posted 06/19/2009 10:36 PM   
[quote name='turls' post='554875' date='Jun 19 2009, 05:36 PM']Ok, I found this post after I just responded a minute ago to the other thread. Interesting I was pretty close in my understanding before reading this from you which helps A TON! THANKS!

In any case, is there any reason that a newer driver version would work better with Samsung DLP because I did already try the hot fix a couple of months ago and I got it to work briefly but ran into issues which caused me to have to uninstall the drivers completely and reload them.

I will try it again though if you think there is a chance a newer driver will work better. . .

Would I be better off trying under Vista x64 or Win7 x64? Sorry I don't have a way to test x86.[/quote]

Hi

Wait for our newer drivers whiching are coming and give it a go.
[quote name='turls' post='554875' date='Jun 19 2009, 05:36 PM']Ok, I found this post after I just responded a minute ago to the other thread. Interesting I was pretty close in my understanding before reading this from you which helps A TON! THANKS!



In any case, is there any reason that a newer driver version would work better with Samsung DLP because I did already try the hot fix a couple of months ago and I got it to work briefly but ran into issues which caused me to have to uninstall the drivers completely and reload them.



I will try it again though if you think there is a chance a newer driver will work better. . .



Would I be better off trying under Vista x64 or Win7 x64? Sorry I don't have a way to test x86.



Hi



Wait for our newer drivers whiching are coming and give it a go.

#7
Posted 06/19/2009 10:46 PM   
Just tried this fix with 1.08 CD. Seems to work. However only with games that do have the corresponding resolutions. For games that don't, it's the same as before.


[quote name='andrewf@nvidia' post='554733' date='Jun 19 2009, 10:20 AM']SOLUTION
- We posted a[url="http://nvidia.custhelp.com/cgi-bin/nvidia.cfg/php/enduser/std_adp.php?p_faqid=2370&p_created=1234213386&p_sid=lkcT7MAj&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9MTAsMTAmcF9wcm9kcz0xMzImcF9jYXRzPTAmcF9wdj0xLjEzMiZwX2N2PSZwX3NlYXJjaF90eXBlPWFuc3dlcnMuc2VhcmNoX25sJnBfcGFnZT0xJnBfc2VhcmNoX3RleHQ9aGR0dg**&p_li=&p_topview=1"] DLP underscsan fix [/url]a while back which changes how that underscan function works. I know the Knowledge Base Article says certain Samsung users shouldnt try it, but I would like them to try it now.[/quote]
Just tried this fix with 1.08 CD. Seems to work. However only with games that do have the corresponding resolutions. For games that don't, it's the same as before.





[quote name='andrewf@nvidia' post='554733' date='Jun 19 2009, 10:20 AM']SOLUTION

- We posted a DLP underscsan fix a while back which changes how that underscan function works. I know the Knowledge Base Article says certain Samsung users shouldnt try it, but I would like them to try it 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+

#8
Posted 06/20/2009 05:23 AM   
[quote name='distant' post='554980' date='Jun 20 2009, 12:23 AM']Just tried this fix with 1.08 CD. Seems to work. However only with games that do have the corresponding resolutions. For games that don't, it's the same as before.[/quote]

When you say games with the corresponding resolutions, do you mean some games you are running dont show some of the new "funky" resolutions like 1820x1024?
[quote name='distant' post='554980' date='Jun 20 2009, 12:23 AM']Just tried this fix with 1.08 CD. Seems to work. However only with games that do have the corresponding resolutions. For games that don't, it's the same as before.



When you say games with the corresponding resolutions, do you mean some games you are running dont show some of the new "funky" resolutions like 1820x1024?

#9
Posted 06/20/2009 10:12 PM   
That's exactly what it was.
For example, if the resize res is 1882x1042, some games do have it shown in the "video options", some don't.
(Is this because the new odd resolution shown in game loaded in automatically? If so, other games must have failed to do so.)

[quote name='andrewf@nvidia' post='555361' date='Jun 20 2009, 03:12 PM']When you say games with the corresponding resolutions, do you mean some games you are running dont show some of the new "funky" resolutions like 1820x1024?[/quote]
That's exactly what it was.

For example, if the resize res is 1882x1042, some games do have it shown in the "video options", some don't.

(Is this because the new odd resolution shown in game loaded in automatically? If so, other games must have failed to do so.)



[quote name='andrewf@nvidia' post='555361' date='Jun 20 2009, 03:12 PM']When you say games with the corresponding resolutions, do you mean some games you are running dont show some of the new "funky" resolutions like 1820x1024?

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+

#10
Posted 06/20/2009 11:26 PM   
[quote name='distant' post='555385' date='Jun 20 2009, 06:26 PM']That's exactly what it was.
For example, if the resize res is 1882x1042, some games do have it shown in the "video options", some don't.
(Is this because the new odd resolution shown in game loaded in automatically? If so, other games must have failed to do so.)[/quote]

Possibly you still need to check Widescreen Gaming Forum or a similar resource for .ini tweaks to enable the new resolutions?
[quote name='distant' post='555385' date='Jun 20 2009, 06:26 PM']That's exactly what it was.

For example, if the resize res is 1882x1042, some games do have it shown in the "video options", some don't.

(Is this because the new odd resolution shown in game loaded in automatically? If so, other games must have failed to do so.)



Possibly you still need to check Widescreen Gaming Forum or a similar resource for .ini tweaks to enable the new resolutions?

#11
Posted 06/20/2009 11:45 PM   
[quote name='distant' post='555385' date='Jun 20 2009, 06:26 PM']That's exactly what it was.
For example, if the resize res is 1882x1042, some games do have it shown in the "video options", some don't.
(Is this because the new odd resolution shown in game loaded in automatically? If so, other games must have failed to do so.)[/quote]

Which games show this problem? Most modern games query the resolutions supported by the GPU and will display it. We've done a lot of investigation into this.
[quote name='distant' post='555385' date='Jun 20 2009, 06:26 PM']That's exactly what it was.

For example, if the resize res is 1882x1042, some games do have it shown in the "video options", some don't.

(Is this because the new odd resolution shown in game loaded in automatically? If so, other games must have failed to do so.)



Which games show this problem? Most modern games query the resolutions supported by the GPU and will display it. We've done a lot of investigation into this.

#12
Posted 06/21/2009 12:07 AM   
One was Need for Speed: Pro street.

[quote name='andrewf@nvidia' post='555400' date='Jun 20 2009, 05:07 PM']Which games show this problem? Most modern games query the resolutions supported by the GPU and will display it. We've done a lot of investigation into this.[/quote]
One was Need for Speed: Pro street.



[quote name='andrewf@nvidia' post='555400' date='Jun 20 2009, 05:07 PM']Which games show this problem? Most modern games query the resolutions supported by the GPU and will display it. We've done a lot of investigation into this.

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+

#13
Posted 06/21/2009 12:44 AM   
So I got everything set up on my 3D Vision, and the 3D setup isn't recognizing that I have a 3D ready display. I get "3D Ready Display Not Found" in the 3D setup wizard.

TV:
I'm connected to HDMI3/DVI, input is set to PC.
In the 3D Menu Picture/Picture Options/3D effect, I've set Mode 1 (Tried 2 as well)

PC:
3D Vision is active/recognized, and plugged into the 3D IR port on the right side of the TV set. (Tried it unplugged as well.)
Latest 270.51 drivers installed

Equipment:
GeForce 560 Ti
Samsung H67A750
Windows 7 x64

Any ideas? Internet searches make it sound like this should be plug-and-play easy with this set. I'm hoping I'm missing something obvious...
So I got everything set up on my 3D Vision, and the 3D setup isn't recognizing that I have a 3D ready display. I get "3D Ready Display Not Found" in the 3D setup wizard.



TV:

I'm connected to HDMI3/DVI, input is set to PC.

In the 3D Menu Picture/Picture Options/3D effect, I've set Mode 1 (Tried 2 as well)



PC:

3D Vision is active/recognized, and plugged into the 3D IR port on the right side of the TV set. (Tried it unplugged as well.)

Latest 270.51 drivers installed



Equipment:

GeForce 560 Ti

Samsung H67A750

Windows 7 x64



Any ideas? Internet searches make it sound like this should be plug-and-play easy with this set. I'm hoping I'm missing something obvious...

#14
Posted 04/12/2011 04:45 AM   
[quote name='DennyA' date='12 April 2011 - 12:45 AM' timestamp='1302583538' post='1223186']
So I got everything set up on my 3D Vision, and the 3D setup isn't recognizing that I have a 3D ready display. I get "3D Ready Display Not Found" in the 3D setup wizard.

TV:
I'm connected to HDMI3/DVI, input is set to PC.
In the 3D Menu Picture/Picture Options/3D effect, I've set Mode 1 (Tried 2 as well)

PC:
3D Vision is active/recognized, and plugged into the 3D IR port on the right side of the TV set. (Tried it unplugged as well.)
Latest 270.51 drivers installed

Equipment:
GeForce 560 Ti
Samsung H67A750
Windows 7 x64

Any ideas? Internet searches make it sound like this should be plug-and-play easy with this set. I'm hoping I'm missing something obvious...
[/quote]
Just making sure here...you do have a full 3D vision kit right? Not 3DTV play. This TV supports 3D vision only with the full kit.

It used to work fine for me but I haven't used it with 3D vision for about a year. It would never recognize the TV as "3D ready" but you would get a "generic DLP" option which works. You may want to try an older driver.
[quote name='DennyA' date='12 April 2011 - 12:45 AM' timestamp='1302583538' post='1223186']

So I got everything set up on my 3D Vision, and the 3D setup isn't recognizing that I have a 3D ready display. I get "3D Ready Display Not Found" in the 3D setup wizard.



TV:

I'm connected to HDMI3/DVI, input is set to PC.

In the 3D Menu Picture/Picture Options/3D effect, I've set Mode 1 (Tried 2 as well)



PC:

3D Vision is active/recognized, and plugged into the 3D IR port on the right side of the TV set. (Tried it unplugged as well.)

Latest 270.51 drivers installed



Equipment:

GeForce 560 Ti

Samsung H67A750

Windows 7 x64



Any ideas? Internet searches make it sound like this should be plug-and-play easy with this set. I'm hoping I'm missing something obvious...



Just making sure here...you do have a full 3D vision kit right? Not 3DTV play. This TV supports 3D vision only with the full kit.



It used to work fine for me but I haven't used it with 3D vision for about a year. It would never recognize the TV as "3D ready" but you would get a "generic DLP" option which works. You may want to try an older driver.

#15
Posted 04/12/2011 05:06 AM   
  1 / 2    
Scroll To Top