New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 836637 link

Starred by 4 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task
Proj-XR

Blocking:
issue 836926



Sign in to add a comment

Maintaining the views in XRSession is confusing

Project Member Reported by ddorwin@chromium.org, Apr 25 2018

Issue description

XRViews are a per-frame concept and thus exposed via XRPresentationFrame in the spec.

In Blink, they are tracked within XRSession. This is confusing because it makes them seem like a stable property of the session.

However, it appears we may want to be able to if we want to modify these per frame, as was the case in https://crrev.com/c/1005627/19, then things don't look right.
 
This is going to heavily depend on the type of device being used. For your average magic window or VR HMD the view set will be almost completely stable, with occasional minor tweaks for things like IPD adjustment. For mobile AR the view will get it's projection matrix tweaks on a per frame basis. For a device like zSpace the view could be massively different frame-to-frame, and it'll even switch between one and two views dynamically.

To be honest I don't know what the right way to handle the full spectrum of possibilities here, but I'm very open to suggestions.
Blocking: 836926
The relationship between update_views_next_frame_ and views_dirty_ is also not clear and neither is documented in the header.
Cc: offenwanger@chromium.org
Labels: XR-Device
Components: Blink>WebXR
Labels: BlinkWebXR
Removing Blink>WebVR component and assigning to Blink>WebXR 
Labels: -BlinkWebXR
Removing Blink>WebVR component and assigning to Blink>WebXR 
Components: -Blink>WebVR
https://github.com/immersive-web/webxr/pull/422 moves views to pose, though that is still per-frame, so I'm not sure that helps.

Sign in to add a comment