The site has a new content architecture. We've added the ability to select your development device to show device-specific content. Please read our blog post Oculus Developer Center Update: Device-centric Documentation Architecture for more information.
All Oculus Quest developers MUST PASS the concept review prior to gaining publishing access to the Quest Store and additional resources. Submit a concept document for review as early in your Quest application development cycle as possible. For additional information and context, please see Submitting Your App to the Oculus Quest Store.
The Oculus SDK provides APIs that return the position and state for each Oculus Touch controller.
This data is exposed through two locations:
ovrTrackingState::HandPoses: Returns the pose and tracking state for each Oculus Touch controller.
ovrInputState: The structure returned by
ovr_GetInputStatethat contains the Oculus Touch button, joystick, trigger, and capacitive touch sensor state.
The controller hand pose data is separated from the input state because it comes from a different system and is reported at separate points in time. Controller poses are returned by the constellation tracking system and are predicted simultaneously with the headset, based on the absolute time passed into
GetTrackingState. Having both hand and headset data reported together provides a consistent snapshot of the system state.