Avatar disappearance in a Shapespark scene – presence synchronization issue

Hello,

We’re encountering a recurring issue in a Shapespark scene integrated into our platform.


:mag_right: Context:

  • Multiple users connect simultaneously to a Shapespark scene.
  • Everything works as expected at first: avatars are visible to all participants.
  • After a certain period of time, one or more users become invisible to others, without any apparent disconnection.
  • New users who join the scene after this occurs can see the missing avatars normally.

:boom: Worsened scenario:

In some cases, all avatars disappear for all participants at the same time.

We observed the following console log at that moment:

txt

CopierModifier

walk.min.js:6711 Cannot attach presentation stream of a user u-1006 The user was not found.

This suggests a desynchronization between users and their visual representation in the scene.


:question: Questions:

  1. Is there a way to force an update or resynchronization of user presence without reloading the scene?
  2. Is this behavior known, and are there recommended settings or best practices to avoid this type of desynchronization?
  3. Is there any method to detect on the client side when an avatar becomes invisible to others, so we can respond accordingly?

We’re happy to provide additional logs or screen captures if needed.

Thank you in advance for your help,

Cédric

Thanks for the detailed report! We’ll be working on reproducing it. Does it happen for short meetings, early after the meeting start? Or does it happen when one of the users is in the meeting (perhaps idle) for many hours?

This happens after a few minutes. I’m using a Mac with the latest version of Chrome.

Hello Shapespark team,

We have identified that the disconnection issues we encountered are caused by micro internet dropouts due to an unstable connection.

The main problem is the following: as soon as a micro-cut occurs, our avatar disappears for users who are already connected, but remains visible for those who join afterward. This creates a visible desynchronization and makes the experience confusing for all participants.

Thank you for reporting this issue, we will look into this and try to find a solution.