Avatar Bugs & Feature Requests

Currently, the shader type called Hidden that can be specified as a fallback shader is introduced on the following page as: > Hidden // (this will hide the mesh from view if the shader is blocked, useful for things like raymarching effects.) > https://creators.vrchat.com/avatars/shader-fallback-system/ However, if a mesh using this shader has an animation that sets the _Color alpha parameter to 1 , the mesh that should have been hidden by the fallback shader becomes visible. My guess is that this happens because the Hidden fallback shader is actually reusing an existing shader (such as Unlit/Color ) and simply sets the color alpha to 0 in order to hide the mesh. When an animation overrides the alpha value, the mesh ends up being rendered. As a solution, I would suggest either providing a dedicated Hidden shader, or adding a special “hidden” flag to the existing shaders so that polygons are not rendered at all.

My avatar has perfect fullbody without any issues in SDK2, but in SDK3 my viewpoint and head will shift backward to align with my hips for whatever reason, causing the spine to bend backward awkwardly and it ruins the tracking. Maybe this is related to hip flipping but I had to do that because previously there was a slight tilt to the side in my hips and that was the only way to fix it. EDIT: The same exact problem occurs regardless of whether or not the hip is flipped, and I already undid the fix and tried following the tracking guide. There is also another problem with fullbody: avatars will actually move their head and torso to be able to reach when the avatars arms are shorter than the user's real arms. Reaching forward for example will make the avatar lunge forward and bend over, as opposed to the previous behavior where the arms extended as far as possible. The new viewpoint system is likely the culprit for everything and it also causes all default animations to look really awful. Here are 2 examples, one without calibration and one with:

Ever since somewhere around 1711 physbone colliders sometimes fail to work until the physbone is toggled off and back on. Toggling the collider does not fix it. It affects randomly locally to the viewer. It is not dependent on whether you are the wearer or not. This is most obvious on floor colliders for tails, but can break other avatar systems that depend on physbone colliders.

Avatars using Final IK's Execution order have their VRIK locomotion settings changed. The two settings that seem affected are the Step Threshold and Step Speed. In the attached gif is the difference between the builds. Multiplying the step threshold by two and dividing the step speed by two restores the VRIK closer to its original status in game, but then it is incorrect in the editor. Deleting the Execution order also makes the VRIK act as it does in the live build, but in this set up the Execution order is vital for the avatar to work correctly.

On a Avatar's body Skinned Mesh Renderer, if you set the "Cast Shadows" option to "Shadows Only", the mesh will only be invisible to Remote players, Cameras and Mirrors, while always being visible to the Local player. This makes creating effects that can only be seen in shadow harder to do as the person who wears the avatar will always be able to see the mesh when we want it to be invisible.

When the following conditions are met, a PB placed under an object with a Constraint setting will not follow the Constraint’s movement, regardless of whether it is Local or Remote. (Contacts follow correctly without any issues.) An animation within the Animator manipulates the Transform of the object that has the Constraint setting. (This applies even if it's in an isolated state.) The Constraint applied to the object is in an enabled state. Once the Constraint is disabled and the animation is able to move the object, the PB starts following to the correct position. (The avatar where this bug was discovered has a somewhat complex setup, so there may be other contributing factors.) The avatar ID where the issue occurs is as follows: avtr_d45ac5bc-cb20-4bce-8c03-bf45e81f0dec SDK: 3.8.0 BuildVersion: 1628 --------------------------------------------------------------------------------------------------------------------- [JP] [特定条件下でPBはConstraint設定されたObjectの動きに追従しません。] 以下の条件を満たすとき、Constraint設定されたObjectの配下に設定されたPBがLocal/Remote問わずConstraintの動きに追従しません。 (Contactは問題なく追従します。) ①Animatorの中にConstraint設定したObjectのTransformを操作するAnimationが含まれている。 (孤立したStateでも同様) ②Objectに設定されたConstraintが有効状態になっている。 Constraintが無効になりAnimationで動かせるようになると、PBは正しい位置へ追従するようになります。 (バグを発見したアバターは少々複雑な作りをしているため、他にも原因があるかもしれません。)

For the sake of simplicity I will be referring to VRChat's built-in eye-tracking when driven over OSC as with the avatars eyes tracking state as Tracked as "native". And I will be referring to animator-based eye tracking driven over OSC with the avatars eyes tracking state set to Animated as "vrcft". Recently, native eye tracking has stopped working on most avatars. Instead of getting eye tracking over OSC, the avatar's eyes will continue to show the simulated eye look. Some observations: Some avatars still work (this rules out most obvious issues with settings). All vrcft (animator-based) tracking continues to work as normal (only native is affected). Which avatars do and don't work appears to be consistent per avatar. Normally with an avatar that has vrcft support, you can switch back to native eye tracking by switching the eyes Tracking state from Animated back to Tracked, all the vrcft-capable avatars I have sampled they instead switch back to simulated eye look. All the avatars I have sampled that do still work seem to be very simple. Yes I have tried deleting my OSC config folder, no effect. Here are some avatars to examine: has vrcft, native doesn't work when vrcft is disabled: avtr_140553ca-38e5-4c7a-b777-7eb72425148e no vrcft, native doesn't work: avtr_c1429633-1bcd-47c6-bd05-30a927b6f11f no vrcft, native works fine: avtr_83323fde-b2ee-41e5-b3b7-817d7c26b62b w_2025.2.2-9dbb64c832 - Steam Branch: open-beta

When someone have parameter values modified using the 3.0 menu, if someone hides and shows the avatar, the values will reset to default. The parameters do not automatically sync when the avatar is unhidden, and only the parameters that were modified after unhiding the avatar will be synced https://drive.google.com/file/d/1LM9Y1NsrcA4jMGFX1nwLLTmn9rE0weBx/view?usp=sharing

Normally, avatars with an incomplete skeleton (such as mine with no fingers) animate fine when walking but retain walking animations when crouched or prone. When using the same avatar on the A3 beta, no animations are used and the model perpetually t-poses.

If you have a VRC Station on a 3.0 avatar, it can't be used. Holding right click and hovering over the collider shows that it's still there, but the interact highlight never appears.