Teleporter gets stuck

[moniquedev]

Description
During our experiments, we have encountered a recurring issue where the teleport function gets stuck and users are unable to use it. This problem has occurred several times and has caused significant disruption to our testing process.

Symptoms

• Teleport function gets stuck
• Users are unable to use the teleport function
• The issue occurs repeatedly during experiments

To Reproduce

1. Launch the experiment
2. Attempt to use the teleport function
3. Notice that the function gets stuck and cannot be used

Expected behavior
Users should be able to use the teleport function without any issues during the experiment.

Actual Results
The teleport function gets stuck and users are unable to use it.

Screenshots

User with teleport stuck

Teleport stuck while holding an spawner

Hardware

• Device: VR headset [Quest 1 and 2]
• Browser: Meta Quest

Additional context

• Workaround: At the moment, there is no known workaround for this issue. We suggest that users restart the experiment if they encounter this problem. However, sometimes it works; sometimes not.
• We have noticed that, most of the time, it occurs with the teleport function on the left controller.

[matthewbcool]

Thank you for your help documenting this issue. I also encountered this problem on Quest2 using the meta quest browser during some live demos at the Mozilla Space in Taipei. Exiting immersive mode and refreshing the browser page reset us in that case. The related systems are being actively updated by the engineering team with the bitECS migration.

[moniquedev]

Hi Matthew - This is good to know, and this is one method of troubleshooting we’ve been using. We always have three users at a time, and the issue is that if we do this in the middle of the experiment (after they have pressed a start button), the environment will reset for that user but continue for the rest of the users, and this will lead to a console data error. Not sure if this should be added to the main post.

[matthewbcool]

@moniquedev lets keep this thread about the teleport issue but welcome any additional bug reports in a separate issue. It's possible this issue will be resolved with some incoming changes to the client. In the mean time if you could share a scene link to where you experienced the issue, that would also be helpful. Thanks!

[Powerstephan]

I'm experiencing this bug also :(

[ghobot]

I have seen this bug in VR for some time, but have not experimented yet with using the new client. The issue with the new client is it breaks how one can make buttons that are links by placing an image in front of a buttons image. The new client, the raycaster does not cause the go to pink button appear. Are there any theories how teleport is called to make it stuck like this? Has anyone seen this occur not in VR?