Can you confirm you enabled this in your quest browser?
I’ve just enabled that flag and tried again with the window.location.href = “webxrUrl”; and takes me out of VR
by user 939271426349862963
I’ve just tried also with window.open(“webxrurl”); after enabling the webxrnavigation flags, and exits from VR when loading the new webxr url
by user 939271426349862963
can you try this again? https://aframe-portal-blueroom.glitch.me/
sure. I entered the blue room, and the first time I interacted with the portal, that exit me from VR and opened the red room. After entering again, I was able to switch rooms without exiting VR
by user 939271426349862963
I tried again and it didn’t exit me from VR as the first time
by user 939271426349862963
I believe the flag isn’t actually needed anymore
Ok so it works on the a-frame demo but doesn’t work on a Needle Engine page for you?
yep, I confirm that I enabled the webxr navigation flag on the chrome://flags/
by user 939271426349862963
First I enabled the webxr navigation flag. After that, I entered to the a-frame and clicked the “VR” button. Then I interacted with the portal to the red room, and that led me out of VR and opened the red room on the regular 2d quest browser. Finally I clicked the “VR” button to enter the red room, and after that I was able to switch between the rooms without exiting VR.
by user 939271426349862963
I tried with both of these, but I get out of the VR experience when my button executes any of these lines: window.open(“webxrurl”, “_self”);
window.location.href = “webxr”;
by user 939271426349862963
Thanks for the additional info, I’ll take a look
Hi @VicDev could you maybe open an issue for this on github? GitHub - needle-tools/needle-engine-support: Needle Engine is a web-based runtime for 3D apps. It runs on your machine for development, and can be deployed anywhere. It is flexible, extensible and includes networking and XR - across platforms. Documentation at https://docs.needle.tools