RebeL_717
4 months agoHonored Guest
[WebXR Hand Tracking] Quest 3 Browser Update Breaks Vuer Integration? Page Unresponsive....
When testing hand tracking on my Meta Quest 3 with the following code:
1.Install Vuer environment
conda create -n vuer python=3.8
conda activate vuer
pip install -U 'vuer[all]==0.0.32-rc7'
2. Test the Program
`from vuer import Vuer, VuerSession
from vuer.schemas import Hands
from asyncio import sleep
# app = Vuer()
app = Vuer(host='0.0.0.0', cert="./cert.pem", key="./key.pem", queries=dict(grid=False), queue_len=3)
@app.add_handler("HAND_MOVE")
async def handler(event, session):
print(f"Movement Event: key-{event.key}", event.value)
@app.spawn(start=True)
async def main(session: VuerSession):
session.upsert @ Hands(fps=60, stream=True, key="hands", showLeft=True, showRight=True)
while True:
await sleep(0.033)`
The GitHub repository for this project is maintained at:
GitHub Issue Link:
the webpage https://192.168.123.182:8012/?ws=wss://192.168.123.182:8012 got stuck on loading when accessed via the Quest Browser.😭 (192.168.123.182 is the my PC IP running the server.) Although the Wolvic browser successfully accesses the Vuer-powered interface, its WebXR implementation exhibits insufficient support for hand tracking. After initiating the 'Enter VR' procedure, the viewport displays two controller models instead of rendering the my hand movements. Consequently, this browser remains unsuitable for my workflow.😩 Back in January, my Quest's Browser was still able to access Vuer and support hand tracking normally.
I would like to confirm whether recent updates to the Quest’s Browser over the past two months have inadvertently disabled remote WebXR functionality. 🤔 Additionally, could you advise on:
1.Steps to roll back the browser to a prior version maintaining WebXR compatibility
2.Alternative VR browsers supporting both WebXR and full-hand gesture tracking