06-18-2014, 11:10 AM
Hey guys,
Seeing all this activity around LightBoost and the work done to get it running on different hardware without 3D Vision makes me really happy.
Some years ago, when the first 3D Vision monitors came out I got my hands on a Samsung 2233RZ. I did a project at home trying to make a DIY "3D Vision" that used IZ3D drivers and some cheap shutter glasses.
In the end it worked quite beautifully at 120Hz, but there was one obstacle remaining: the 2233RZ had a special "3D mode" that could only be engaged when connected to a 3D Vision-compatible Nvidia card.
The DIY project worked in the standard 120Hz mode of the 2233RZ, but 3D image ghosting was pretty bad. Turns out that the special "3D mode" of the display increases the scan speed so that there is more time for shutter glasses to open (so less ghosting).
I never got the monitor to go into this mode, and could do little reverse-engineering because I didn't even have an NVidia card or 3D Vision kit. So I accepted it didn't work great and left the project at that.
Now, three years later, I see how ToastyX managed to crack the proprietary DDC handshake that NVidia uses to enable LightBoost. I know it's not the same thing, but maybe the lessons learned can also be applied to my problem?
After all, we're talking about a special mode that the 2233RZ goes into for 3D Vision gaming, that only seems to be accessible by the 3D Vision kit and cards... It has custom timings, sure, but the monitor also goes into a special state where, for example, many menu functions are disabled in this mode.
I suspect the monitor is being instructed by the NVidia card to go into 3D Vision mode. And I suspect that this may very well be the same kind of sequence used to enable LightBoost in 3D Vision 2 hardware: some proprietary handshake over DDC, then possibly some custom display timings.
It may even be the exact same handshake - for this, I really am asking the help of ToastyX's experience with reverse-engineering this stuff.
I am not very experienced in this stuff, and most importantly: I don't actually have access to the 3D Vision kit.
But I would love to find out how to trick the monitor into using 3D mode, on any video card, with or without 3D Vision. It would finish my project, and maybe help others who want a DIY shutterglass setup compatible with a 2233RZ monitor (and maybe others)!
If someone is interested, this is a link to the three-year-old project, using some old shutterglasses and the IZ3D driver:
http://www.mtbs3d.com/phpbb/viewtopic.php?f=26&t=13495
Seeing all this activity around LightBoost and the work done to get it running on different hardware without 3D Vision makes me really happy.
Some years ago, when the first 3D Vision monitors came out I got my hands on a Samsung 2233RZ. I did a project at home trying to make a DIY "3D Vision" that used IZ3D drivers and some cheap shutter glasses.
In the end it worked quite beautifully at 120Hz, but there was one obstacle remaining: the 2233RZ had a special "3D mode" that could only be engaged when connected to a 3D Vision-compatible Nvidia card.
The DIY project worked in the standard 120Hz mode of the 2233RZ, but 3D image ghosting was pretty bad. Turns out that the special "3D mode" of the display increases the scan speed so that there is more time for shutter glasses to open (so less ghosting).
I never got the monitor to go into this mode, and could do little reverse-engineering because I didn't even have an NVidia card or 3D Vision kit. So I accepted it didn't work great and left the project at that.
Now, three years later, I see how ToastyX managed to crack the proprietary DDC handshake that NVidia uses to enable LightBoost. I know it's not the same thing, but maybe the lessons learned can also be applied to my problem?
After all, we're talking about a special mode that the 2233RZ goes into for 3D Vision gaming, that only seems to be accessible by the 3D Vision kit and cards... It has custom timings, sure, but the monitor also goes into a special state where, for example, many menu functions are disabled in this mode.
I suspect the monitor is being instructed by the NVidia card to go into 3D Vision mode. And I suspect that this may very well be the same kind of sequence used to enable LightBoost in 3D Vision 2 hardware: some proprietary handshake over DDC, then possibly some custom display timings.
It may even be the exact same handshake - for this, I really am asking the help of ToastyX's experience with reverse-engineering this stuff.
I am not very experienced in this stuff, and most importantly: I don't actually have access to the 3D Vision kit.
But I would love to find out how to trick the monitor into using 3D mode, on any video card, with or without 3D Vision. It would finish my project, and maybe help others who want a DIY shutterglass setup compatible with a 2233RZ monitor (and maybe others)!
If someone is interested, this is a link to the three-year-old project, using some old shutterglasses and the IZ3D driver:
http://www.mtbs3d.com/phpbb/viewtopic.php?f=26&t=13495