You are not logged in.

Dear visitor, welcome to krpano.com Forum. If this is your first visit here, please read the Help. It explains in detail how this page works. To use all features of this page, you should consider registering. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

1

Wednesday, April 12th 2017, 12:29pm

webVR viewer setting - read from Google Profile QRCODE

hi all! we are a software house and we are currently developing an APP for iOS and Android based on Cordova and, obviously, KRPANO HTML5 viewer. this APP shows content (stereo image) from a server using webVR plugin. we are using different kind of headset (Google Cardboard, Trust Explore, Zeiss VR ONE, Homido, ecc..) but we want to extend list of compatible headsets to many manufacturer. we know that it's possible to insert the different parameters of the specific device inside krpano, but our customer asks to adopt (if it's possible) the same logic of Google Cardboard using QRCODE provided by the devices manufacturers.
we have analyzed the parameters adopted by Google for its viewers profile generator and we have written a javascript library to read this parameters from QRCODE, but are different from krpano parameters. it's possible even with some type of calculations to convert google parameters in krpano parameters?

Reference:
Google parameters:https://vr.google.com/cardboard/viewerprofilegenerator/
WebVR parameters: https://krpano.com/plugins/webvr/#mobilevr_lens_overlap

2

Wednesday, April 12th 2017, 12:39pm

Hi,

it might be possible to convert the parameters (and I'm also considering implementing directly the cardboard distortion model as alternative), but that all would become unnecessary once WebVR gets available in the browsers, then the browser will do the VR distortion by its own.

Best regards,
Klaus

3

Wednesday, April 12th 2017, 1:38pm

Thanks for the answer.


Sorry but what do you mean for "but that all would become unnecessary once WebVR gets available in the browsers, then the browser will do the VR distortion by its own."?


You can help us with the conversion of parameters?
Or if you are considering to implementing the cardboard model, if you want, we can share our knowledge to get the result.


Best regards,

Hevolab

4

Wednesday, April 12th 2017, 2:23pm

Sorry but what do you mean for "but that all would become unnecessary once WebVR gets available in the browsers, then the browser will do the VR distortion by its own."?
The WebVR API should be available in Chrome and Firefox in 'near' feature.
And with the WebVR API the browser itself will do the VR lens distortion. That means there is no need for an lens parameters or settings in this case.

You can help us with the conversion of parameters?
Or if you are considering to implementing the cardboard model, if you want, we can share our knowledge to get the result.
Here the cardboard lens distortion model:
https://developers.google.com/vr/android…fficients(float[])
and here at 'mobilevr_lens_dist2' the krpano 'MobileVR' one:
https://krpano.com/plugins/webvr/#mobilevr_lens_dist2

But the fov and overlap parameters might be more difficult to convert...