HAND_MOVE event for PICO VR not working

[yjmade]

Thanks for the great work. Currently I'm working on make it work on PICO VR. Everything else works well, only HAND_MOVE event fetched from client has it's content empty. The event value is as follow:

client<HAND_MOVE>({'left': ExtType(code=0, data=b'\x00'), 'right': ExtType(code=0, data=b'\x00'), 'leftState': {}, 'rightState': {}})

I believe the issue is on the Vuer client js side, but unluckily I didn't find it's source on github. Please help to make it work. Thanks.

[silencht]

what is your Pico browser version?

[yjmade]

3.3.45 and the system version is 5.0.12.S, which is the just upgraded latest version.

[yjmade]

Also, MotionControllers + CONTROLLER_MOVE event doesn't work well either. Code as follows

        self.app.add_handler("CONTROLLER_MOVE")(self.on_motion_controller_move)
        session.upsert @ Hands(fps=fps, stream=True, key="hands", showLeft=False, showRight=False)
        session.upsert @ MotionControllers(stream=True, key="motion-controller", left=True, right=True)

The handler can be called, but the event is empty as follows:

 client<CONTROLLER_MOVE>({})

[yjmade]

Strangly, I just tried Quest 3, with the vuer version 0.0.41, Although The HAND_MOVE event for Quest 3 works well. But CONTROLLER_MOVE event still empty. I use eact code from the document , the printout shows same as before:

Movement Event: key-motion-controller {}
Movement Event: key-motion-controller {}
Movement Event: key-motion-controller {}
Movement Event: key-motion-controller {}
Movement Event: key-motion-controller {}
Movement Event: key-motion-controller {}
Movement Event: key-motion-controller {}
Movement Event: key-motion-controller {}

Could be some problem from my side?

[geyang]

@yjmade you should try the newest version of vuer. See what is on the doc: https://docs.vuer.ai/

[yjmade]

@yjmade you should try the newest version of vuer. See what is on the doc: https://docs.vuer.ai/

Hi, @geyang I upgrade to 0.0.42, and found that the HAND_MOVE event cannot be received on both Quest and PICO.

session.upsert @ Hands(fps=fps, stream=True, key="hands")

[geyang]

shoot let me take a look later can you try vuer.ai version to see?

[yjmade]

shoot let me take a look later can you try vuer.ai version to see?

vuer.ai behave the same with 0.0.42.

To be more clear, let me put a table

0.0.41:

	Quest 3	PICO 4
Controller	only one controller works fine, two controller results browser crash when enter VR	works fine for 1 or 2 controller
Hand	works fine	recv empty event

0.0.42

Quest 3	PICO 4
can not recv the HAND_MOVE & CONTROLLER_MOVE event	browser crash when enter VR

[silencht]

I also encountered the crash issue when using the Pico 4 browser before version 4.0.28 (hand tracking mode). Therefore, I submitted the bug log to the Pico team, and the issue has been fixed in the internal 4.0.28 beta version of the Pico browser. Since this is an internal beta version, it may not have been rolled out to all users yet. I’m sharing this as a reminder and hope it helps everyone.

[geyang]

This is very helpful @silencht !

[hejia-zhang]

I have the same issue, although I can receive controller move event, my vuer version is 0.0.42. 0.0.41 works for me. BTW, how can I visualize the hand landmarks in vr?

[hejia-zhang]

Also, MotionControllers + CONTROLLER_MOVE event doesn't work well either. Code as follows

    self.app.add_handler("CONTROLLER_MOVE")(self.on_motion_controller_move)
    session.upsert @ Hands(fps=fps, stream=True, key="hands", showLeft=False, showRight=False)
    session.upsert @ MotionControllers(stream=True, key="motion-controller", left=True, right=True)

The handler can be called, but the event is empty as follows:

 client<CONTROLLER_MOVE>({})

Why are you using showLeft/Right=False?

[Yanbing-Han]

In the latest version of Vuer (0.0.60), all these issues have been resolved—both controllers and hand tracking now work properly on Quest 3 and PICO 4. Note: For hand tracking to work on PICO 4, please make sure to install the browser linked here: https://github.com/unitreerobotics/avp_teleoperate/issues/53.

Let us know if you still encounter any problems!