Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Oculus Quest VR: texImage3D is not a function

See original GitHub issue

Description of the problem

When calling render with renderer.vr.enabled = true; on Oculus quest, you get the error:

Error message: Uncaught TypeError: texImage3D is not a function
URL: three.js 
Line Number: 22118

This appears to be related to multiview which I presume is used for VR now.

This issue is very recent. Yesterday before my Oculus Quest automatically updated itself, I was able to run my VR game fine on it. After the update, I had to switch to using XR instead. I downloaded the latest build of three.js. Now whenever vr.enabled === true I get this error.

Three.js version

OS

Android

Issue Analytics

State:
Created 4 years ago
Comments:25 (2 by maintainers)

Top GitHub Comments

6reactions

Artyom17commented, Dec 17, 2019

7.1 should be released this week, btw.

3reactions

fernandojsgcommented, Dec 17, 2019

I just tested the apk and I can confirm OVR_multiview2 is not exposed in the WebGL1 context, and multiview is working as expected with no antialias context (Using this PR: https://github.com/mrdoob/three.js/pull/18178). I have tried also the rest of the examples and all of them works fine on the v7.1 Thanks @Artyom17 👍