Skip to content
Discussion options

You must be logged in to vote

So, I'd bet this is an async issue. WebXR has always required "user activation": basically you can't just have JS start a WebXR session, there has to be a user click that caused it. The trick is, that's slightly heuristic on Chrome's side. If they click something and you immediately start WebXR (like when you have a hardcoded src), then it's all fine. If you click, then wait a while for the scene to export, and then start WebXR, it may have taken long enough that your click doesn't count anymore.

I think there are a number of ways around this. You might just put in a dummy src, then on click, start WebXR first and then do your scene export and src swap in the background.

Replies: 2 comments 4 replies

Comment options

You must be logged in to vote
3 replies
@ZackARC-solutions
Comment options

@HannesAnWang
Comment options

@elalish
Comment options

Answer selected by ZackARC-solutions
Comment options

You must be logged in to vote
1 reply
@ZackARC-solutions
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
4 participants
Converted from issue

This discussion was converted from issue #3763 on September 01, 2022 21:58.