Avatar Bugs & Feature Requests

When other players load an avatar faster than the avatar wearer, the avatar's Expression Parameters can have unintended values from the perspective of those who have loaded the avatar. This may cause the animator to execute remotely in a way that was not designed by the avatar author. For instance, when all of the following are combined: the avatar have pieces of clothing enabled by default in the hierarchy the animator states are entering a default state that makes sure they are enabled on entry the expression parameters has a default value properly set in a way that the entry state will not transition to another state unless manually acted upon ...even when all of these conditions are satisfied, when the other players load the avatar faster than the wearer, then the Expression Parameters may be seen by others with an unintended value that is non-default, causing the animator to transition to other states after loading, which may disable said clothing. This kind of behavior is invisible to the avatar wearer who may never be aware that this is happening. It puts a lot of burden onto the avatar creator to handle this edge case properly.

All right, VRChat removed avatar remeasure function in August 2020 and said they would correct the bug and put it back. But far from such a hint, time is just passing, and frankly, it is questionable whether they really intend to return the function to us at this point. Would you be able to answer whether you want to permanently delete a feature or if you really implement it? sorry for translating text.

I have compiled a list of regressions that I have observed while testing on Vive wands on Live and Avatars3-Beta branch, with both Vive advanced controls disabled and Vive advanced controls enabled. The regressions boil down to: Vive advanced controls turned ON can no longer perform analog fist gestures Vive advanced controls turned OFF has completely regressed, such as the grip button having a lower priority than the trackpad, fist not triggering automatically when pressing the trigger, gestures not persisting when the thumb is released from the trackpad Thumbs up is missing from the wheel, whereas handopen has appeared on the trackpad I'm unable to tell which of these changes might have been intentional.

Any animation that changed the material on a mesh to another material is only changing in the mirror it is not changing locally or for others. You can test this on my public model in the av3 beta world. This was working fine in previous vrchat build.

There seems to be an issue where your mirror reflection clone does not behave as expected with regards to layer weights changed by the animator layer control behaviour for animations in that layer that involve material swap and material settings. I am not entirely certain when this issue started happening, but it was not observed to effect my avatars when physbones was released to live. As material swaps and material property animations are only supposed to happen on the FX layer, I would assume this bug only affects the FX layer. I've reproduced the problem in this avatar id : avtr_56d9d511-2f9e-4ba0-b33a-c06c81f1497b There are 2 layers in this avatar labled SphereGreen and SphereRed respectively on the FX controller. The avatar has a coloured sphere in front of it SphereGreen has a single animation that Sets the colour of the sphere to green via material colour property Sets the size of the sphere to a scale of 0.1 Disables a second sphere green in colour SphereRed has a single animation that Sets the colour of the sphere to red via material colour property Sets the size of the sphere to a scale of 0.5 Enables a second sphere green in colour Write defaults are off. The layer weights of SphereGreen and SphereRed are set to 1 SphereGreen is layer 4 while SphereRed is layer 5, as such SphereRed's animation should take priority if the layer weight is not 0. SphereGreen has an animator layer control behaviour that sets SphereRed layer weight to 0. Expected behaviour: sphere is green for local, remote players, and mirror reflection. Outcome: sphere is green for local and remote players, but is red in mirror reflection. The size of the sphere and the toggling of the second sphere are behaving as expected. The above was also tested using material swaps to the same result. To be clear, if the layer weight of SphereRed was set to 0 by default and not via the avatar layer control behaviour, it behaves as expected. The inverse is also true, if SphereRed was initially set to a weight of 0 and set to 1 via an avatar layer control behaviour, the mirror reflection has a green sphere instead of an expected red sphere. As you can see in the screenshot, the layer weight for SphereRed is 0, and the sphere for my player local avatar is green, but the sphere in the mirror reflection is red.

Problem: Clicking the reset button after setting the view with Animator Set View doesn't unset the view in Desktop. Steps to Reproduce: Use Animator Set View to set the view. Select the reset button in the first Expressions Menu.

When an avatar is uploaded with a non-unity scale, animations when viewed by others are shifted. See below (Left is the avatar wearer, right is from a secondary player's perspective) https://cdn.discordapp.com/attachments/730948173379535022/741992149494792263/2020-08-09_12-36-38-1.mp4 The avatar in question has a scale of ~0.454, which shifts the animation down. If the model is scaled up (to say a scale of 1.4) then the animation is shifted up This issue was also reproduced with another model, so it's unlikely to be a rigging issue. The SDK 2.0 version of this avatar doesn't have the same issue. so I believe the issue to be SDK 3 exclusive

When you enter a station, a few values don't get reset to default values. Velocity and isGrounded is some of them that is stuck in the state they were in before you entered the station. Which we also have no control over. --- Could also be that this is intended, but filling a bug report so that a clear answer can be given, and possibly fixed/updated documentation to include this. Repo example; Stand by a station Jump Enter station mid jump Look at the avatar debug menu See isGrounded is False, while you're in the station. Exit station isGrounded is now True It's the same for Velocity

This bug is new to the Open-beta AV3SDK ever since there were changes made to example layers and as said in the title Example locomotion layer that comes with SDK doesn't have "proxy_stand_still" animation assigned by default for "Reset Tracking" state where jump landing happens which means if players had to use that example locomotion layer on their avatar and jump, during landing "Restore Tracking" state avatar will be stuck in the ground with nothing playing for about 2 seconds SDK Version Date: 2020.05.06.12.14 (2020.07.31.17.18)

This is due to use of enumValueIndex in VRCSDK\Dependencies\VRChat\Editor\Components3\VRCAvatarDescriptorEditor3AnimLayerGui.cs The net result of this is, the layers are off by 1 between Inspector and Debug. And if you reset to default, your layers will be offset: The immediate cause is the VRCAvatarDescriptor.AnimLayerType enum value for SpecialIK was removed. The order remained the same, and the values remained the same, but anything uses the "enum index" will break, including the VRCSDK3 VRCAvatarDescriptor Inspector.