WebXRManager: Add AR plane detection.

[richardanaya]

Related #24792.

Description

Added support for Meta Quest Pro and Quest 2 support for plane detection API along with an example.

[Mugen87]

Please add the new example to https://github.com/mrdoob/three.js/blob/dev/examples/files.json so it appears at the side menu.

Also create a thumbnail via npm run make-screenshot webxr_ar_plane_detection (even if the screenshot will be black for now).

[richardanaya]

@Mugen87 Added files.json and screenshot :)

I think there might be a problem with that link you sent to test since this example depends upon a compiled threejs. I made a test branch here that has my change to WebXRManager compiled in.

https://raw.githack.com/richardanaya/three.js/test/examples/webxr_ar_plane_detection.html

[Mugen87]

Thanks for updating the link!

How do I test this with a Quest 2? I've only used the device for VR so far. When opening the example, I see the same output like on my desktop (black screen and the "AR not supported" message).

[richardanaya]

@Mugen87 right now there's a step you have to do for Quest:

1. Go to Settings -> Experimental -> Setup Room
2. Add some walls and doors or anything.
3. Restart device and you should see the option for AR when you go to try examples in Quest Browser

If it works in the reference demo:
https://immersive-web.github.io/webxr-samples/proposals/plane-detection.html

it should work in:
https://raw.githack.com/richardanaya/three.js/test/examples/webxr_ar_plane_detection.html

[Mugen87]

Thanks for the instruction! Indeed it works as expected.

/cc @cabanier

[cabanier]

1. Go to Settings -> Experimental -> Setup Room
2. Add some walls and doors or anything.
3. Restart device and you should see the option for AR when you go to try examples in Quest Browser

You don't need to restart the device after setting up walls and doors. They are pulled each time you start an immersive session.

[cabanier]

Thanks for the instruction! Indeed it works as expected.

Does this mean that you get a plane event each frame?

[Mugen87]

Thanks for the instruction! Indeed it works as expected.

Does this mean that you get a plane event each frame?

I wanted to say that the rendering looks as expected. Meaning the configured walls are correctly displayed.

The new detectedPlanes event is fired each frame. Isn't that optimal?

[cabanier]

Thanks for the instruction! Indeed it works as expected.

Does this mean that you get a plane event each frame?

I've wanted to say that the rendering looks as expected. Meaning the configured walls are correctly displayed.

The new detectedPlanes event is fired each frame. Isn't that optimal?

It might be nice to get an event each time the planes change.
On Quest, this is only once. On Android this happens constantly.

[richardanaya]

@Mugen87 added some new events as per @rcabanier 's recommendation and updated example and test deploy.

[richardanaya]

Fixed a small issue related to removing planes while iterating and trying to conserve allocations. Should be good to merge to my knowledge.

[richardanaya]

added getKnownPlanes method as a way to acquire known planes outside of event responses.

[richardanaya]

@Mugen87 I went through once more, and tried to make sure style in example and code was consistent. I think this is ready for a review.

[richardanaya]

@Mugen87 resolved requests with name changes/deprecations and re-tested and updated test branch :)

[richardanaya]

Added documentation.

[cabanier]

LGTM!

[mrdoob]

@richardanaya Seems like you can have multiple rooms if you enter/exit XR.

Should the example delete the previous generated geometry when entering XR?

[mrdoob]

@richardanaya Seems like you can have multiple rooms if you enter/exit XR.

Should the example delete the previous generated geometry when entering XR?

Just took care of this in #26098