This repository has been archived by the owner on Feb 10, 2023. It is now read-only.
Replies: 1 comment 6 replies
-
Hi there @IRobot1 , sorry in advance. I don't have a VR set to test this out as well as I don't have enough time nowadays to work on AngularThree much. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First, this problem doesn't happen using Windows Mixed Reality in Edge browser. I can only repeat using Meta Quest 2 after Entering VR from its browser
My app page looks like this
Pages loaded via router changing the contents of the canvas. Here's a basic example of new content being added to the canvas
When navigate between router inside the Quest browser, the pages render correctly. However, when I Enter VR and navigate to a new content via a route, the canvas is blank
Using the example above, nothing is render; not the light or the mesh.
If I render using THREE objects, they're added to the scene properly.
I've tried navigating without using router, problem still happens.
I even tried forcing change detection on every tick
Its like the NG3 change detection completely stops or gets stuck rendering all changes outside of Angular zone.
I've installed the Oculus development tools and remotely monitored the browser console. No errors or warnings.
I've spent days trying to debug this problem and finally out of things to try.
Any suggestions? I'll try putting the most basic repeat case together and sharing.
If you have a Meta Quest headset, you can see the problem in this DEMO
Beta Was this translation helpful? Give feedback.
All reactions