> While there seems to be no restrictions in terms of TV size, a 3D TV
> needs a minimum refresh rate of 120Hz (a basic 60Hz displayed for each
> eye). The higher the refresh rate, the smoother the 3D effect. So a
> 240Hz set will be capable of outputting 120Hz to each eye.
>
> HDMI 1.4 will also be required for full HD per eye viewing."

According to the wikipedia article on HDMI there seems to be various 
options for how to actually send the 3D data along the link (frame by 
frame or left/right image joined together in each frame).  It's a bit 
unclear exactly how this is sent, but the table further down says that 
3D over 1080p60 is not possible.

> The forum post I found explaining why I couldn't just use a TV that
> claims 120hz, but isn't, I don't remember the link to. But, basically,
> while, in theory, you only need 25 frames a second to "see" an image,
> this isn't practical for various reasons, especially motion issues,
> which is why games *attempt* to always produce at least 50 frames a
> second, if not 60. The difference "is" visible, since even though the
> eye only needs 25, those 25 don't necessarily match the "frame rate" the
> eye is looking at the screen with (i.e., your meat system isn't
> "synchronized" with the refresh rate on the display). So, trying to use
> 30 frames a second, by splitting 60hz (i.e. 60 frames) flat out won't
> work properly. The closer you can get to 60 frames a second per eye, the
> less likely you are to notice any sort of flicker, blurring, etc., from
> desynching.

I guess the TV processes whatever input it is getting and then decides 
how to display it.  If it's getting a 2xp24 input then it probably shows 
each eye frame twice alternately.

Next step is to find out if it's possible to coax a standard PC/GPU/3DTV 
to show a 120 Hz 2D image...

Post a reply to this message