Blocking a Rift S sensors
Hello VR Experts I need to know if it is possible to cover a Rift S but still gain its head rotation? Can the headset still work if it was covered with let's say a velvet material? I don't need hands and positional tracking for the project! I understood the old Rift DK1's internal accelerometer still calculated rotation with its external sensors disconnected. (a bit cheeky, but would this also be the same situation for a Quest's head rotation?) It's for an artist instalation you see. Thanks in advance
Logging Capabilities via SDK
I have a very high-level question. Is it possible to log or the following types of information via the Oculus SDK (while e.g. using the DK2): head position with 3D coordinates/directions, eye positions, hand/controller positions, buttons pressed, the image the user is currently seeing (or video?). Is this provided by the SDK or is there a way to obtain this directly from the hardware? Or is this only accessible (and better caught) via a gaming engine, such as Unreal, that interfaces to Oculus? I only have a very basic understanding of the hardware and the SDK and want to get a better understanding of getting to low-level sensor information. I am thinking about a small project that simply records these types of low-level information and possibly getting to some derived higher-level movement information (e.g. gestures) . Any help pointing me to sections of the SDK, other documentation, other VR projects and/or tools would be highly appreciated. So far, I have looked at the Avatar, the Sound SDK, and the PC SDK but was only able to find very high-level information about gaming. Am I looking in the wrong place?
Where's the headset and controller origin point?
What position, specifically, on the physical headset and touch controllers is reported by ovr_GetTrackingState? From the doc: "The SDK reports a rough model of the user’s head in space based on a set of points and vectors. The model is defined around an origin point, which should be centered approximately at the pivot point of the user’s head and neck when they are sitting up in a comfortable position in front of the camera." However, the eye offsets provided by ovr_GetRenderDesc only have a nonzero offset in the x-direction, which doesn't jive with the above description. What physical points do ovrTrackingState.HeadPose and ovrTrackingState.HandPoses actually correspond to on the devices?
Are there examples for HMD and position tracking?
Dear community, Is there any working sample with the actual SDK version to log the HMD (axes, pitch, roll and yaw) and the position ? I'm struggling with the documentation and cannot find any supporting docs, code or examples which makes this topic easier to understand. I would be very thankful for any help on this topic. Thanks and best regards.
Disabling Oculus tracking/rotation
Hey, I'm aware that this question has been asked quite a lot (https://forums.oculus.com/community/discussion/40288/is-it-possible-to-disable-all-tracking, https://forums.oculus.com/community/discussion/comment/242286), but everything i've found has been for Unity, when I'm working with the C++ API (Using CV1, newest SDK). Anyway, I'd ideally like some function (like an ovr_DisableTracking), that i could call on initialization that would stop the Oculus from responding to any gyroscopic, accelerometer, etc, readings. Basically i want to turn the Oculus into a head mounted dumb screen. I've tried a separate thread that calls the ovr_SubmitFrame as frequently as possible, but the occasional frame drop or context switch leads to this making the image occasionally get out of sync with the actual HMD orientation, leading to black bars. Plus I'd prefer to drop an unnecessary thread. The reason i want this is because i want to have a camera mounted directly on the front of the Oculus piping into the screen, making any Oculus orientation readings redundant, since the camera moves with the user's head anyway. Any recommendations or code samples would be fantastic. Thanks.