What do you call it when VR Environment is not calibrated?
And how do you fix it? I am lacking the vocabulary to even ask the right question or search for a solution. But it is like the perspective is off a little. and not consistently. As an example, the Getting Started area where you have a circular desk/table around you and you can throw paper airplanes, fly the remote-control blimp, throw the ball, the pull string bottle rockets, etc... the desk is too close and way too high. Like I can rest my chin on the tabletop without moving forward or down. I'm not sure how to recalibrate this as it seems to be better sometimes, and worse at others. It is like the scale and placement of everything is off. Controllers do not point straight forward (which I have found some possible fixes). But, if I hold the controllers like a rifle to play a shooting game, the controllers point about 15 degrees to either side. and holding them up in a position like a real rifle it is about 3-4 inches low. Making it impossible to get a sight picture using the sights, optics, or other aiming device without contorting myself in very strange positions. I am assuming there are calibration settings somewhere to correct these types of things and potentially in individual games as well. Could someone clue me in on the proper terminology and some possible fixes? On a separate note. While I usually find various controllers a little small or too cramped. Does anyone else find the controller buttons a little awkward? Like they are too far apart? Not set up to be used quickly with a natural grip. I really want to like this but so far it has been very awkward to do various things in VR. I'm sure once the perspective issues are resolved it should help with the other things.
Quest 2 calibration with external camera and access to guardian coordinates
I am working on the calibration of the Quest 2 with a physical camera. I would like to better understand how the Quest 2 establishes the coordinates of its 3D space in relation to the guardian and especially how it either re-establishes or changes this when it is turned off, sleeps or goes outside of the guardian? Is there a system 'translation vector' that could be read and used to realign local 3D space with the updated Quest 2 3D space? If not, I am interested in learning how to establish a relationship with or get access to some fixed coordinate in the guardian space such that a translation vector could be calculated. Any input on this would be appreciated. I have not been able to find reference details on this via a search - could someone point me in the right direction? If it needs context, then it would be relative to Unity. I have developed for other platforms but am new to development for the Quest 2 / Unity.
Mixed Reality Capture Tool Calibration has to be redone almost every time
I am using the Mixed Reality Capture Tool (latest version 5.1.1) with a custom Unity App using the default MRC scene template. I am doing MRC with a quest 2 using the oculus link so I choose Rift S when using the tool. When I calibrate my camera and run the app and OBS everything works fine, but then if I re-run the app later in the day the calibration is all off and I have to recalibrate. It's a painstaking process and really annoying that it gets off for some reason. The camera has not moved. Any idea what the issue could be? It would be great if the tool/api would say where the calibration is stored so it could be saved externally and verified. It's way too much of a black box now. This would also be helpful to have separate calibrations for different setups.
Saving calibration state after calling ovr_RecenterTrackingOrigin
Ingame I can call ovr_RecenterTrackingOrigin and this works, but it is not saved or made persistent when running my exe a second time. In fact, my controllers (including the Oculus) are recreated at every ingame heat, and this keeps resetting the Oculus calibration position. I can only change this in a persistent way by calibration inside the Oculus Home screen. I would however like to be able to make the calibration persistent also from within my game. I could check and save (on disk) the calibration pose after calling ovr_GetTrackingState() after having called ovr_RecenterTrackingOrigin(), but it seems silly to have my own calibration matrix on top of the Oculus provided one. Any idea how I could achieve that?