issues in quest 2?

[jameshdougherty]

Unable to read joints so far using either method: var joints = evt.detail.data.joints; is showing an error on load: "SyntaxError: missing : after property id" when loading the page, even when inside enter-vr condition, before vr started

Using the other method, joints shows as undefined: var leftHand = document.getElementById('left-hand'); var joints = leftHand.components["hand-tracking-extras"].joints; var Wrist = joints.Wrist;'; // Cannot read property 'Wrist' of undefined, still udf even with delay

hand-tracking-extras is showing as registered in the a-frame inspector, and is in place in the hand Not sure what I'm missing, tried many variations, including setTimeout delays

Also, added close quote to href for script to avoid 404

[gftruj]

hi, sorry for the delay, I currently have only a standard Quest, do you have a glitch, or example which i could debug? Maybe Its not related to quest2

[jameshdougherty]

A frame updated in the meantime and seems to be working ok now- thanks for following up.

Sent from my iPhone

On Feb 8, 2021, at 5:25 PM, Piotr Milewski notifications@github.com wrote:

 hi, sorry for the delay, I currently have only a standard Quest, do you have a glitch, or example which i could debug? Maybe Its not related to quest2

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

[gftruj]

Oh there were changes in aframe 1.2.0 (commit) due to WebXR API changes (old, new).

Thanks for bringing this up, I was too busy to notice the changes. Obviously I need to check out the updates thoroughly, but I've made a quick-fix for aframe-master + an example on glitch - https://gftruj-handstuff.glitch.me/. Its a visual debug of joints rotations (raw data, and re-oriented).

If you could let me know if this works for you as well it would mean a lot :)