Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request depth-sensing generates error from 161 onwards #30275

Open
darioreal opened this issue Jan 7, 2025 · 2 comments
Open

Request depth-sensing generates error from 161 onwards #30275

darioreal opened this issue Jan 7, 2025 · 2 comments
Labels

Comments

@darioreal
Copy link

Description

Adding depth-sensing requirement on requestSession generates a getDepthInformation() null error from version 161 onwards

Reproduction steps

  1. Import a jsdeliver versión greater than 160
  2. Add depth-sensing on xr.requestSession
  3. Load web on recent chrome for an android 14

Code

Import as THREE from 'https://cdn.jsdelivr.net/npm/[email protected]/+esm';

Live example

Screenshots

No response

Version

r160

Device

Mobile

Browser

Chrome

OS

Android

@Mugen87
Copy link
Collaborator

Mugen87 commented Jan 7, 2025

I'm unable to reproduce an issue with the following demo (which uses depth sensing): https://threejs.org/examples/webxr_xr_cubes

Tested on a Pixel 8a with Android 15 and Chrome 131.

I'm a bit confused about the error report since three.js officially supports depth sensing since r161. Did you use a forked version of the renderer and implement depth sensing by yourself prior to r161?

@Mugen87 Mugen87 added the WebXR label Jan 7, 2025
@dli7319
Copy link
Contributor

dli7319 commented Jan 7, 2025

Sounds like the same error we had which is fixed in #30241

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants