WebXR Device API - Input > 자유게시판

• 목록
• 답변
• 글쓰기
• 게시판 리스트 옵션
  • 수정
  • 삭제

This doc explains the portion of the WebXR APIs for managing input throughout the range of XR hardware. For context, it may be useful to have first examine WebXR Session Establishment and Spatial Tracking. In addition to the diversity of tracking and show technology, XR hardware may assist a wide number of input mechanisms together with display taps, movement controllers (with multiple buttons, joysticks, triggers, touchpads, drive sensors, and many others), voice commands, spatially-tracked articulated arms, single button clickers, and more. Despite this variation, all XR enter mechanisms have a typical purpose: enabling customers to goal in 3D space and carry out an motion on the goal of that intention. This concept is called "target and select" and is the foundation for how input is exposed in WebXR. All WebXR input sources may be divided into certainly one of three categories primarily based on the strategy by which customers should goal: ‘gaze’, ‘tracked-pointer’, and ‘screen’.

Gaze-based enter sources shouldn't have their own tracking mechanism and as an alternative use the viewer’s head place for focusing on. Example embody 0DOF clickers, headset buttons, common gamepads, and certain voice commands. Within this class, some enter sources are persistent (e.g. these backed by hardware) whereas others will come-and-go when invoked by the user (e.g. voice commands). Tracked pointers are enter sources in a position to be tracked individually from the viewer. Examples include the Oculus Touch movement controllers and the Magic Leap hand monitoring. For movement controllers, the target ray will often have an origin on the tip of motion controller and be angled slightly downward for iTagPro features comfort. The precise orientation of the ray relative to a given machine follows platform-particular pointers if there are any. In the absence of platform-specific steering or a bodily device, the target ray points in the identical path as the user’s index finger if it was outstretched. Within this class, input sources are considered linked even when they're temporarily unable to be tracked in space.

Screen based enter is driven by mouse and touch interactions on a 2D display screen which can be then translated into a 3D concentrating on ray. The concentrating on ray originates on the interacted level on the display as mapped into the input XRSpace and extends out into the scene alongside a line from the screen’s viewer pose place via that point. The specific mapped depth of the origin point depends upon the consumer agent. It Should correspond to the actual 3D position of the point on the display screen where out there, however May also be projected onto the closest clipping plane (defined by the smaller of the depthNear and depthFar attributes of the XRSession) if the actual display screen placement is not recognized. To accomplish this, pointer events over the relevant screen areas are monitored and non permanent enter sources are generated in response to allow unified enter dealing with. For inline periods the monitored region is the canvas related to the baseLayer.

For immersive periods (e.g. hand-held AR), your entire screen is monitored. Along with a focusing on ray, all input sources present a mechanism for the person to carry out a "select" motion. This person intent is communicated to developers by means of occasions that are mentioned intimately in the Input occasions part. The physical action which triggers this choice will differ based on the input sort. The inputSources attribute on an XRSession returns a list of all XRInputSources that the user agent considers lively. The properties of an XRInputSource object are immutable. If a gadget could be manipulated in such a means that these properties can change, the XRInputSource will be faraway from the array and a brand new entry created. When input sources are added to or iTagPro features faraway from the listing of obtainable enter sources the inputsourceschange event have to be fired on the XRSession object to point that any cached copies of the checklist should be refreshed. In addition, the inputsourceschange event can even fireplace once after the session creation callback completes.