Matching the field of view between Desktop and Oculus Rift DK2

[samzebrado]

Actually I just came across same question. We used CV1 instead of DK2, but nothing looks weird inside. Now I need to check whether the fov of CV1 was properly approximated in a vizconnect config preset because in the preset using Oculus and PPT, the info of the Oculus display seemed to be made for DK2.
btw. I think the Oculus app, which have to be launched by yourself or by vizard during use, might have provided some information about its resolution and fov to vizard, and that could be why we did not find distortion in CV1.
Anyway I'll keep searching for relevant info.

[samzebrado]

Hi all,

Hope this would be useful.

I've just go through Vizard5/python/oculus.py.
Line 195: left,right,bottom,top,near,far = camera.getFrustum()

The field of view could be computed from these "left, right, bottom, top" parameters.
Line 190 - 194 showed the "camera" could come from self.getCameraList(), and self.getCameraList() came from self._sensor.getCameraList(), defined after Line 340.

Similarly I found the following path of variable creation:

self._sensor <-- allSensors <-- getSensors() <-- getExtension().getHMDList() <-- getExtension() <--viz.addExtension('oculus.dle')

'oculus.dle' should be a plugin of vizard, similar to the vrpn plugin, which help getting data from other apps.

It looks like that oculus app did pass some info about the screen's real size and fov to vizard.

Thus if you wanna get that "real fov", you just need to back compute it from the Frustum parameters returned by camera.getFrustum().

p.s. maybe in oculus app you could modify this parameter, or not

Originally Posted by samzebrado

btw. I think the Oculus app, which have to be launched by yourself or by vizard during use, might have provided some information about its resolution and fov to vizard, and that could be why we did not find distortion in CV1.
Anyway I'll keep searching for relevant info.