Page MenuHome

Cycles: Pole merging for spherical stereo

Authored by Sergey Sharybin (sergey) on May 17 2016, 2:14 PM.



The idea of pole merge is to fade interocular distance after a certain
altitude to zero when altitude goes closer to a pole. This should prevent
annoyances looking up in the sky or down to the bottom.

Works for both panorama and perspective cameras when Spherical Stereo
is enabled.

Diff Detail

rB Blender

Event Timeline

Sergey Sharybin (sergey) retitled this revision from to Cycles: Pole merging for spherical stereo.
Sergey Sharybin (sergey) updated this object.
Brecht Van Lommel (brecht) accepted this revision.EditedMay 17 2016, 9:34 PM
Brecht Van Lommel (brecht) edited edge metadata.

Looks good to me. Any reason not to enable this by default? How would a user decide to turn this on or off?

Would be good to avoid users rendering long animations and then noticing a problem that requires them to render again.

This revision is now accepted and ready to land.May 17 2016, 9:34 PM

For a panorama camera it makes sense to enable this by default.

For perspective camera i'm not so sure actually. Not sure it has something bigger in mind than ability to render a cubemap (in which case having pole merging for perspective camera would also make sense) or there are cases when you might want want the camera to simply render what the eye sees.

@Sebastian Koenig (sebastian_k), any idea what's the best default value here?

I would say it makes sense to have it enabled only when spherical stereo is activated too.
For stereo panoramas it just looks better on the poles. And if I render a perspective camera with spherical stereo enabled then chances are I am either rendering a cubemap (which has the same characteristics as a panorama when it comes to stereo viewing comfort) or want to integrate something into a before rendered panorama (be it cubemap or equi etc.), in which case I would want pole merging enabled as well so that it matches the panorama.

Btw, proposal for UI:

This revision was automatically updated to reflect the committed changes.

It seems in the commit this didn't end up enabled by default?

@Brecht Van Lommel (brecht), we talked to Sebastian in IRC and conclusion was that it's better not to enable this by default.

I don't really have string opinion on defaults here (it's mainly matter of documenting behaivor and when/if you might want to use some option) and fine changing it ay time in the future. But i kinda want studios who actually does VR to agree the default is useful, and for now seems they don't want it default just yet.

Ok, it's fine with me, just noticed it was different than what was said here.