Local Animations Not Syncing When Using ObjectSync
closed
goblox
Version: VRCSDK2
Unity: 2018.4.2041
SDK: 2020.04.01.09.57
Client: 912
Description of the bug:
Animation controllers, with object sync, are not synchronizing the current animation state to all clients when the current animation state is changed using a local-only button that sends an AnimationTrigger event.
Steps to reproduce (how did you encounter the bug?):
Setup an animation controller that will go through various animation states. Add an object sync component. Create a button that uses a local animation trigger to move through the various animation states. The current animation state is not synchronized between clients, any client can activate the button causing the animation states to change independently. Attempting to force ownership of the object with the animator component did not resolve the issue.
Any extra files? (output logs, screenshots):
Screenshot with debug messages
Unity package with an example scene: https://drive.google.com/open?id=1KG79IPZWNpn7YpNhuTZSbQEfuD41vH0M
Log In
Tupper - VRChat Head of Community
closed
Closing due to age and inactivity.
Desunyan
Just discovered from testing - it happens if Animator has more than one animation Layer. Syncing works fine with only one layer in current live build (921) but breaks when more than one layer present and triggers log spam (still happens in live 921)
Ruuubick - Designer
in progress
Log spam is removed for this patch, next one will have the full fix
goblox
In an effort to make it easier to test this out, I've built and uploaded a world using this local animator sync test package. The world ID is: wrld_1886645c-08e5-41da-a198-6c291b8f8f18
Steps to reproduce (how did you encounter the bug?):
Enter the world using two clients logged in to VRChat on two different accounts. Once the world has loaded on both clients, try using the green "Next State" and "Previous State" buttons on the master (animator owner). On the non-owner account, observe the red State Indicator does not change states along with the owner. Either client can use the Next and Previous State buttons to move through the states independently. I have also included a blue "Take Ownership of Animator" button. You can use this to attempt to force ownership transfer of the animator, but this doesn't currently resolve the issue.
Ruuubick - Designer
tracked