Fielf Of View computation

[devasur]

https://w3c.github.io/webvr/#vrfieldofview

Do you have any plans to include a standardized device selection options (in lines of dbdb) to wbvr-manager? Will be very useful for setting the FoVs of the scene correctly.

If you do not have any plans, how would you recommend going about incorporating this feature?

[borismus]

FOV depends mostly on the viewer parameters, not so much the phone. Take a
look at device-info.js in polyfill

On Mon, Jun 27, 2016 at 7:16 AM Boni Gopalan [email protected]
wrote:

https://w3c.github.io/webvr/#vrfieldofview

Do you have any plans to include a standardized device selection options
(in lines of dbdb) to wbvr-manager? Will be very useful for setting the
FoVs of the scene correctly.

If you do not have any plans, how would you recommend going about
incorporating this feature?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#150, or mute the
thread
https://github.com/notifications/unsubscribe/AAQ8gEOAWOYpyHlDyY0G3QtA53Knp9aSks5qP9s1gaJpZM4I_I3k
.

[devasur]

Yes. You are right. I am still trying get that exact responsibility split arounf polyfill vs. manager constructs. IMO, wouldn't the the VR app need to query for the Viewer FoV and then use 2xFoV as the the ThreeJS camera FoV for appropriate rendering? This was my question. So, if we were to do that the viewer selection need to expand beyond Carboard V1 & Cardboard V2, with an easy to extend and expand structure. This is where a global database similar to dbdb will help. Probably it can carry identifiers, a standard icon and the rest of the parameters (that profile generator creates?) I am sure rest of the parameters are important for the polyfill to draw bevels correctly too.