Avatar spawn in twice
The last version I was on that this was not an issue was 2.12. After that, I updated to 2.14 and ever since that I've had an issue with avatars sometimes double spawning. I use Avaturn avatars and this was not an issue in Normcore up to version 2.14. I've tried out the latest Normcore recently as well to see if there was anything that was causing this that got patched up, but the issue is still there...
The way I have it setup is Avaturn requests to download an avatar from it's server (where the avatar was created online via a browser), and after that, the model is simply placed into the Normcore's avatar and it retrieves all the bones to sync up properly the movement with tracking.
The issue looks like this - you can enter the room and everything is ok, or sometimes you can enter the room and see someone spawned in double - one avatar copy will be t-posing and the other will be tracked or sometimes even the other copy looks broken if the bones were not read correctly due to double spawn.
Reverting back to Normcore version 2.12 makes the issue go away. And I have not changed anything about the logic of the code in question here.
Does anyone have any idea or pointer as to what this could be? Or maybe this is a known bug?
The way I have it setup is Avaturn requests to download an avatar from it's server (where the avatar was created online via a browser), and after that, the model is simply placed into the Normcore's avatar and it retrieves all the bones to sync up properly the movement with tracking.
The issue looks like this - you can enter the room and everything is ok, or sometimes you can enter the room and see someone spawned in double - one avatar copy will be t-posing and the other will be tracked or sometimes even the other copy looks broken if the bones were not read correctly due to double spawn.
Reverting back to Normcore version 2.12 makes the issue go away. And I have not changed anything about the logic of the code in question here.
Does anyone have any idea or pointer as to what this could be? Or maybe this is a known bug?
