You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you want to request a feature or report a bug?
🐞Report a bug 🐞
What is the current behavior?
On the first step of the tutorial as long as I can correctly render the red box using ThreeJS
Once I add the AR.js related code I start running into issues.
✅The webcam correctly requests for the needed permissions and is in use by the browser
🐞No video element is added to the dom as described in the guide
🐞The webcam cannot be seen anywhere
I am greeted by several errors and warnings in the console:
🐛WARNING: Multiple instances of Three.js being imported.
🐛THREE.PlaneBufferGeometry has been renamed to THREE.PlaneGeometry.
Hey. I figured out installing older version of three.js fixes some of the issues. However I'm still having a problem with three objects quickly appearing in the beggining and then dissapearing from the scene. Found a hacky fix for it but I would appreaciate AR.js fixing the location based bugs.
Do you want to request a feature or report a bug?
🐞Report a bug 🐞
What is the current behavior?
On the first step of the tutorial as long as I can correctly render the red box using ThreeJS
Once I add the AR.js related code I start running into issues.
I am greeted by several errors and warnings in the console:
VERTEX
SHADER_INFO_LOG:
Then a couple more warnings and:
🐞After reporting 32, no further warnings will be reported for this WebGL context.🐞
If the current behavior is a bug, please provide the steps to reproduce.
Reproduce by following the tutorial about location-based-arjs-with-threejs from the official documentation website.
Please mention other relevant information such as the browser version, Operating System and Device Name
Tested on:
What is the expected behavior?
If this is a feature request, what is motivation or use case for changing the behavior?
The text was updated successfully, but these errors were encountered: