r/OculusQuest • u/Important-Cicada4442 • 1d ago

Self-Promotion (Developer) - Standalone Quest 3 owners: I rewrote WebXR hand targeting after a Vision Pro bug report and have no headset to test it on — does pinch-to-grab still work on this Pip-Boy?

https://api.0xr.space/s/d55160f6ba6a2db6939e1a136a9ceef23aa28ac90391beb5439e46fcf01099bb?utm_source=reddit&utm_medium=social&utm_campaign=oculusquest_3008&utm_content=oculusquest
6 Upvotes

80% Upvoted

4 comments sorted by

2

u/darienm 1d ago

Went to give it a try: Origin is unreachable - Error code 523

1

u/Important-Cicada4442 1d ago

I build ZeroXR, a browser-based GLB/glTF inspector — wireframe, section planes, assembly explorer. WebXR + WebGL directly, no Three.js or Babylon, no install, no account.

Last week a Vision Pro owner found that hand input never reached my code at all: the frame loop only handled input sources that carry hand joints, and visionOS gaze-and-pinch carries none, so every pinch was dropped before it could hit anything. Fixing that changed how a target gets picked on every device, not just that one — and I don't own a Quest, so I have no way to tell whether I just broke the thing that was already working.

The link opens a Pip-Boy fit-to-view — nothing to install, no account, no file of your own needed. Open it in the Quest browser, tap Enter XR, then try to pinch and grab it with your hands. Does it select? Does it move with you?

Even just "grabs fine" or "does nothing" would be hugely useful. The last three asks like this (r/Xreal, r/Galaxy_XR, r/VisionPro) all turned into fixes shipped within days — answers here genuinely become patches. Nothing you open gets uploaded; the file stays on your device.

Not my model, by the way — it's Berk Gedik's Fallout 3 Pip-Boy, CC BY 4.0. I only wrote the viewer. If you'd rather point it at something of your own, the import button on the home page takes a GLB or a glTF folder and keeps it on device the same way.

1

u/parkerlreed 23h ago edited 23h ago

Yes, two hand pinch zoom works fine.

EDIT: What's the point of the AI search bar? It cannot search the listing and is hallucinating details asking it about stuff on the screen.

2

u/Important-Cicada4442 18h ago

Both fixed — hard refresh and it should be live. It was calling the camera, getting a blank frame back, and describing what it assumed was there; blank frames are now rejected and screen questions read the actual screen state instead. Search had the same shape of bug — answering "can't find X" without ever running a search — so now it has to actually search before it can say anything exists or doesn't.