W3C

– DRAFT –
Immersive Web WG/CG bi-weekly call

15 October 2024

Attendees

Present
bajones, bialpio, cabanier, Leonard, m-alkalbani, matatk, MikeW
Regrets
-
Chair
yonet
Scribe
cabanier, Leonard

Meeting minutes

<bajones> Zoom link is telling me it's got an invalid meeting ID?

<cabanier> I'm in the meeting but nobody else is here

<bajones> What link did you use to join?

<cabanier> https://www.w3.org/events/meetings/efecb307-2559-4f8f-b0ac-a06a099027f2/20241015T120000/

<bajones> One sec. Mic issues

Add XRView to XRDepthInformation (immersive-web/depth-sensing#50)

Brandon: Has not had a chance to bring issue up to WebGPU WG meeting

Rik: #2: https://github.com/immersive-web/depth-sensing/pull/50
… Add array (extend API) to allow for lower frame rate texture generation
… No resolution during TPAC. Need to determine the option(s) needed to be added to the dictionary to make this work in a variety of situations
… Likely to pick an solution that is more complex to allow greater range of options. No candidate yet.

bialpio: Feels that a single PR is better than (Rik
… 's multiple PR suggestion) because the s/w is currently shipping
… No strong suggestion for name. Several come to mind, but no preferences ATM.

<bajones> "unprojected depth" or similar sounds reasonable to me.

Rik: Believes that this change is not breaking. <lots of speculation on names>

<bajones> "synchronizedDepth"?

bialpio: If XRView is never going to be populated, then change is not breaking. Advocates delaying updates so that XRView does not need to be populated

Brandel: Encourage that the name being as descriptive as possible -- looking out 15+ years

[general agreement]

<bajones> Potential last second topic: https://github.com/immersive-web/WebXR-WebGPU-Binding/issues/13

<bajones> Mostly to raise awareness

Rik: Update PR because people seem OK with proposal.

RESOLUTION: Rik & Aysegul: Propose 'synchronizedDepthBuffer' as the name

<yonet> tGuarantees about layer texture shape (immersive-web/WebXR-WebGPU-Binding#13)

Brandon: Topic from above and last minute...
… Discussion on GitHub with WebGPU/WebGL bindings with respect to the shape of the API bindings. Currently using a "side texture"
… (above should be WebGPU/WebXR)
… Looking for devices where this decision would cause problems - https://github.com/immersive-web/WebXR-WebGPU-Binding/issues/13

Rik: Good with this.
… Is there support for MultiView in WebGPU

Brandon: Not ATM. Some extensions in the overlying s/w are there, but not WebGPU level.

MikeW: Open issue for WebGPU to add MultiView handling

Leonard: I was asked about following up with body poses and hand tracking
… and I talked to Brandon Jones

bajones: I don't remember discussing body and hand pose

Leonard: openxr wants cooperation but they don't want to block us
… whoever does the path, they will be happy to follow
… I will go back and check with ????
… this thursday

yonet: they are welcome to come to our meeting

Leonard: there's some group discussion on body tracking
… I wanted to make sure that the groups didn't go in perpendicular directions

bajones: arkit has a skeletal model
… mirroring makes it easier
… there may be different joint counts
… and see how we can transpose pose to make the models match

Leonard: one of the problems is that there are over a dozen different body standards
… unfortunately, there is no movement to reduce that
… maybe the things to is to bring up in the metaverse standards group
… I think this will be a big enough issue for everyone to agree on

Summary of resolutions

  1. Rik & Aysegul: Propose 'synchronizedDepthBuffer' as the name
Minutes manually created (not a transcript), formatted by scribe.perl version 197 (Tue Nov 8 15:42:48 2022 UTC).