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

Consistent crashing in AR experience with particular shader + how to debug!! #198

Open
shiukaheng opened this issue Jun 9, 2022 · 1 comment

Comments

@shiukaheng
Copy link

shiukaheng commented Jun 9, 2022

Hi, I'm developing a site that uses some custom shaders and three.js to do volumentric video, but somehow WebXR Viewer crashes every time it gets on screen (force refreshes the page). Here is a live demo, simply press the AR icon to start the experience.

I would really love to debug this myself, but I have no idea if it is even possible to open up the equivalent of the console on WebXR Viewer, so I come in deseperation for any pointers / ideas with what is going on.

This behaviour is only on the WebXR viewer in AR mode, it works fine when it's rendered from its regular viewport, and only occurs with WebXR viewer and is fine with any other browser that supports immersive-ar. I have singled out the shader crashing the site, as it only happens when the object is in the screen / scene, and has basically no logic on the javascript side.

The shaders is ripped from here, which simply uses a special VideoTexture to displace / texture the mesh.

Any help will be greatly appreciated! Thanks in advance.

@jaeh
Copy link

jaeh commented Jul 10, 2022

maybe see if your uniforms have defined types, safari tends to crash in some exotic cases when they are not.
in three.js:

const uniforms = {
  { value: 1.0, type: 'f' },
}

we are working with videotextures just fine in threejs and webxr viewer, so it's not a general issue you are facing.

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

No branches or pull requests

2 participants