Hand / Controller models disapear which switching modes.

[KooIaIa]

This is happening in my site and another unrelated persons site so it appears to be a bug in latest A-frame.

Example: https://strata-design-demo.vercel.app/examples/1/view

Controls look like this when its working and you switch from hands to controllers:

The bug is that the hands or controllers disappear frequently when doing this switching:

Notice how the laser attached to the hand is still there and tracking is happening. It appears to just be the visual logic hiding the hands or controllers that is breaking.

The problem resolves itself on Quest when going in and out of the Oculus menu.

[electrum-bowie]

Up 😆

[vincentfretin]

Your site is down. Can you please create a simple test case with https://krabbel.dev so we see what components you're using and please tell us exactly what was the aframe version and components that was used when you saw that issue.
I'm also having sometimes that issue with handy-controls and just hiding my hand behind my back and putting it back in front fixes the issue generally. I'm not sure if the issue is in the handy-controls component, in XRControllerModelFactory or threejs or a Meta browser issue with the disconnected/connected events, I don't currently have time to spend hours debugging that, that's really low on my priority list.
My guess is that's probably a race condition with a quick succession of controller disconnected, hand connected, hand disconnected controller connected that toggles the visibility of the models.

[KooIaIa]

https://krabbel.dev/p/pretty-cougars-smash

I just did this minimal code on the default Krabbel sample.

  <a-entity id="rightController" oculus-touch-controls="hand: right"></a-entity>
  <a-entity id="leftController" oculus-touch-controls="hand: left"></a-entity>
  <a-entity id="rightHand" hand-tracking-controls="hand: right; modelStyle: mesh"></a-entity>
  <a-entity id="leftHand" hand-tracking-controls="hand: left; modelStyle: mesh"></a-entity>

I added cubes so you can see them when they turn invisible.

I agree it seems like a racing condition.

I was not able to reproduce it with this Three.js example. https://threejs.org/examples/webxr_vr_handinput_profiles

The controllers motion is still correctly being tracked. On the Three example, the moment you move your hand a small distance they appear correctly no matter what even if it seems like the transition broke.

[electrum-bowie]

I'm also having sometimes that issue with handy-controls and just hiding my hand behind my back and putting it back in front fixes the issue generally. I'm not sure if the issue is in the handy-controls component, in XRControllerModelFactory or threejs or a Meta browser issue with the disconnected/connected events, I don't currently have time to spend hours debugging that, that's really low on my priority list.

Unsure if that's the same bug, but the one we're having is critical.

Not having correct controller rendering is a huge problem for anyone using it...