VRPose

Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.

Non-standard: This feature is non-standard and is not on a standards track. Do not use it on production sites facing the Web: it will not work for every user. There may also be large incompatibilities between implementations and the behavior may change in the future.

The VRPose interface of the WebVR API represents the state of a VR sensor at a given timestamp (which includes orientation, position, velocity, and acceleration information).

Note: This interface was part of the old WebVR API. It has been superseded by the WebXR Device API.

This interface is accessible through the VRDisplay.getPose() and VRDisplay.getFrameData() methods. VRDisplay.getPose() is deprecated.

Instance properties

VRPose.position Read only

Returns the position of the VRDisplay at the current VRFrameData.timestamp as a 3D vector

VRPose.linearVelocity Read only

Returns the linear velocity of the VRDisplay at the current VRFrameData.timestamp, in meters per second.

VRPose.linearAcceleration Read only

Returns the linear acceleration of the VRDisplay at the current VRFrameData.timestamp, in meters per second per second.

VRPose.orientation Read only

Returns the orientation of the sensor at the current VRFrameData.timestamp, as a quarternion value.

VRPose.angularVelocity Read only

Returns the angular velocity of the VRDisplay at the current VRFrameData.timestamp, in radians per second.

VRPose.angularAcceleration Read only

Returns the angular acceleration of the VRDisplay at the current VRFrameData.timestamp, in meters per second per second.

Examples

See VRDisplay.getFrameData() for example code.

Specifications

This interface was part of the old WebVR API that has been superseded by the WebXR Device API. It is no longer on track to becoming a standard.

Until all browsers have implemented the new WebXR APIs, it is recommended to rely on frameworks, like A-Frame, Babylon.js, or Three.js, or a polyfill, to develop WebXR applications that will work across all browsers. Read Meta's Porting from WebVR to WebXR guide for more information.

Browser compatibility

BCD tables only load in the browser

See also