View Full Version : How stere pairs are created?
05-23-2010, 04:44 AM
I am trying to understand, how stereoscopic pairs are created. On the internet I found a lot of information about that, but I donīt know which techniques are still actual.
On what I found, I think there are some different aproaches:
1) The scene is rotated or shifted to generate the left and right eye view. You have only one camera.
2) Something about two projection centers. I donīt realy understand.
3) As you can see here: http://local.wasp.uwa.edu.au/~pbourke/miscellaneous/stereographics/stereorender/
You use two cameras, that are viewing the same scene from two different positions.
I think number 3 is the technique which is used nowadays, right? The webpage linked at number 3 says something about a method called "off-axis". In other sources I found number 2 is called like this. Is it the same?
05-23-2010, 08:26 AM
1 and 3 are the same thing. Shifting the scene is equivalent to a second camera. Not sure about 2, but many times you have a "focus" point both cameras point at so you rotate the camera a small degree around that point. In the end you want two images, one image offset from the other. Then you have to get one image into one eye and the other image in the other eye. Polarized glasses is one method, where your left lens filters out the right image and the right image filters out the left.
05-23-2010, 03:54 PM
Thanks for your answer. It helped a lot.
I think this is the same like rotating the scene:
Then this is the two center thing, I think:
This seems to be only shifting, but no rotation:
Am I correct?
Pictures are from nvidia (http://www.nvidia.com/docs/IO/36545/parallel-dia.jpg) and Paul Bourkes Website (http://local.wasp.uwa.edu.au/~pbourke/miscellaneous/stereographics/stereorender/) [/B]
05-24-2010, 02:18 AM
first picture is a wrong method.
2) and 3) are almost the same in fact, the difference being that 2) does not need black vertical borders on the screen.
So 2) is best. And even better is to place left and right cameras exactly at the place the user has its eyes, knowing the size and distance of the screen. And on top of that, tracking eyes in real time :)
05-25-2010, 05:13 AM
Thanks for your answers.
I have another questions to the techniques above. These techniques require to render every picture twice. Isnīt that pretty slow?
The time you need for rendering wouldnīt matter that much for annimation movies. But what about applications you interact with, like medical systems or video games?
05-25-2010, 05:39 AM
It is not "pretty slow", it is only twice as slow in the worst case.
An example, instead of rendering 120fps (which gets capped to 60hz with vsync), render 60fps with stereo, it is much better.
05-25-2010, 10:19 AM
As ZbuffeR stated, twice as slow is the worst case. So many games and other applications do a lot of render-to-texture for things like environment maps and dynamic textures like fire and such. Those don't need to be rendered twice. In fact, if you look at nVidia's slides on automatically making a game 3D, they use some pretty cool tricks to decide which textures need to be rerendered, and according to them quite a bit of the render calls now days isn't for the final render. Also, work like setting up VBOs and such only need to be done once.
05-30-2010, 09:36 AM
I have a last question:
I just looked at the list of games supportet by NVIDIAS 3D Vision system: http://www.nvidia.co.uk/object/GeForce_3D_Vision_3D_Games_uk.html
There you can read:
NVIDIAŪ 3D Vision automatically transforms hundreds of PC games into full stereoscopic 3D right out of the box, without the need for special game patches.
How can the NVIDIA software do this? It cannot be one of the stereo rendering methods above, because that has to be integrated in the game engine I think. Is it simple pixel shifting?
05-30-2010, 09:55 AM
How can the NVIDIA software do this?
It cannot be one of the stereo rendering methods above, because that has to be integrated in the game engine I think. Is it simple pixel shifting?
In fact the nivida driver is somewhat part on the game engine. For 3Dvision, it stores rendering commands and view projections, and when swapbuffers is called, it replays the commands on a slighty changed projection, like methods above.
That means the following problems happen (tried) :
- badly choosen depth (focal plane is too far / too near for a game)
- most multipass and post-processing effects are broken (bloom, shadows, ...)
- hud and 2D elements are messy
"Supported" games are detected by the nv driver and some parameters are tweaked or disabled to lessen artifacts (but you loose visual features too).
Read these topics for interestings discussions and the 'merits' of Nvidia 3D vision, versus actual 3D API such as quad buffered stereo of the OpenGL spec :
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.