VRFrameData

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 not standardized. We do not recommend using non-standard features in production, as they have limited browser support, and may change or be removed. However, they can be a suitable alternative in specific cases where no standard option exists.

The VRFrameData interface of the WebVR API represents all the information needed to render a single frame of a VR scene; constructed by VRDisplay.getFrameData().

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

Constructor

VRFrameData()

Creates a VRFrameData object instance.

Instance properties

VRFrameData.leftProjectionMatrix Read only

A Float32Array representing a 4x4 matrix that describes the projection to be used for the left eye's rendering.

VRFrameData.leftViewMatrix Read only

A Float32Array representing a 4x4 matrix that describes the view transform to be used for the left eye's rendering.

VRFrameData.pose Read only

The VRPose of the VRDisplay at the current VRFrameData.timestamp.

VRFrameData.rightProjectionMatrix Read only

A Float32Array representing a 4x4 matrix that describes the projection to be used for the right eye's rendering.

VRFrameData.rightViewMatrix Read only

A Float32Array representing a 4x4 matrix that describes the view transform to be used for the right eye's rendering.

VRFrameData.timestamp Read only

A constantly increasing timestamp value representing the time a frame update occurred.

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

Enable JavaScript to view this browser compatibility table.

Help improve MDN

Was this page helpful to you?

Yes No

Learn how to contribute

This page was last modified on Sep 20, 2024 by MDN contributors.

View this page on GitHub • Report a problem with this content