Movatterモバイル変換


[0]ホーム

URL:


  1. Web
  2. Web APIs
  3. VRPose
  4. linearVelocity

VRPose: linearVelocity property

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 thecompatibility 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.

ThelinearVelocity read-only property of theVRPose interface returns an array representing the linear velocity vector of theVRDisplay at the current timestamp, in meters per second.

Note:This property was part of the oldWebVR API. It has been superseded by theWebXR Device API.

In other words, the current velocity at which the sensor is moving along thex,y, andz axes.

Value

AFloat32Array, ornull if the VR sensor is not able to provide linear velocity data.

Examples

js
// rendering loop for a VR scenefunction drawVRScene() {  // WebVR: Request the next frame of the animation  vrSceneFrame = vrDisplay.requestAnimationFrame(drawVRScene);  // Populate frameData with the data of the next frame to display  vrDisplay.getFrameData(frameData);  // Retrieve the linear velocity values for use in rendering  // curFramePose is a VRPose object  const curFramePose = frameData.pose;  const linVel = curFramePose.linearVelocity;  const lvx = linVel[0];  const lvy = linVel[1];  const lvz = linVel[2];  // render the scene  // …  // WebVR: submit the rendered frame to the VR display  vrDisplay.submitFrame();}

Specifications

This property was part of the oldWebVR API that has been superseded by theWebXR Device API. It is no longer on track to becoming a standard.

Until all browsers have implemented the newWebXR APIs, it is recommended to rely on frameworks, likeA-Frame,Babylon.js, orThree.js, or apolyfill, to develop WebXR applications that will work across all browsers. ReadMeta's Porting from WebVR to WebXR guide for more information.

Browser compatibility

See also

Help improve MDN

Learn how to contribute

This page was last modified on byMDN contributors.


[8]ページ先頭

©2009-2026 Movatter.jp