Avatar Bugs & Feature Requests

Affected private avatar: Robot （nested armatures） ( avtr_6cb82e04-86d1-4afe-9261-583b03496c06 ) by WubTheCaptain Create a minimal Excellent avatar (Robot) with 1 particle system, set its max particles to 2. Duplicate the minimal Excellent/Good avatar (Robot) and nest it under the avatar. Modify the particle system under the nested avatar to have a maximum of 2147483647 particles. Delete the animator component, VRC avatar descriptor and pipeline manager script from the duplicated avatar nested under the actual avatar. (Optionally, delete the armature and body meshes too.) Build & Test. Build & Publish as a private avatar. Check the avatar stats of the local SDK test avatar & uploaded avatar separately. Expected result: Red, Very Poor 2,147,483,647 particles in local SDK avatar, SDK performance rank estimation and after upload. Actual result: Local SDK test avatar and SDK performance ranking estimate reports Very Poor 2,147,483,647 particles. However, after Build & Publish the avatar shows Excellent, -2,147,483,648 particles. The avatar is simultaneously ranked both "Good" and "Very Poor" in the client. Remote and local users see this as a Good avatar on nameplate. Typically these avatars behave like unbounded number of particles (a crasher avatar) when particle limiter is disabled in client settings, even if the particle count is reported as negative. Additional info: Nested avatars/armatures must be used, because otherwise the particles will always be capped at maximum integer value (2,147,483,647). SDK 3.10.4, VRChat 2026.2.3p2 Build 1866 (unity-6). Affects both the main branch and unity-6 public beta branch.

I tryed to send "/avatar/change" osc message but it does not work. I also sended "/avatar/parameters/..." together and it works. osc.send({address: "/avatar/parameters/BustSize", args: [0.5]}); // works osc.send({address: "/avatar/change", args: ["avtr_0eb0aeff-5a47-4c01-86e7-943cfcc1e8b5"]}); // not working

VRCHeadChop components have no effect on any non-humanoid avatars. I tested multiple avatars and settings. The bug occurs with or without custom animator layers, so it's not an issue with animations overwriting anything. Given how important this component is to most non-humanoid avatars, this seems like an unintentional error. The workaround of including an entire humanoid-skeleton is poor for both optimization and user-friendliness.

SDK 3.10.1 The PhysBone Count in-game and on the website includes bones that should have been skipped by the Ignore Other Phys Bones toggle. For example; I make an avatar with a longer strand of hair. All hair is under one PhysBone component "Hair_PB", and the Long Strand (7 Bones) is targeted by its own PhysBone Component "Strand_PB". Hair_PB has Ignore Other Phys Bones turned ON so that the Long Strand is affected only by Strand_PB, and not Hair_PB. The SDK reports, let's say 28 PhysBone Transforms (Mobile Medium). The website and in-game stats report a Mobile Poor ranking due to having 35 PhysBone Transforms; the Long Strand must have been counted for both components. The SDK calculates this value properly; disabling Ignore Other Phys Bones on Hair_PB causes the SDK to report 35 PhysBone Transforms.

Please add a RenderType tag to the Toon Standard shader for avatars, so that shader replacement trickery in worlds can work properly. All you need to do is to add "RenderType" = "Opaque"

Tried uploading an avatar with the latest SDK version - it'd fail at the last second, claiming there's no thumbnail when there IS one set for sure (tried with multiple kinds + in-scene capture). But the avatar could be seen as uploaded on the VRC website, but not in game... and when the 'change to avatar' button was clicked, it'd claim there's no avatar there. I rolled my SDK back to 3.8.2 and it uploaded just fine.

If an avatar has an active Particle System and gets hidden by Avatar Culling on remote client, IsAnimatorEnabled constantly stays false for this remote client after showing that avatar again. On video demo I have a simple cube that is animated by IsAnimatorEnabled value. It's red if IsAnimatorEnabled == false and green if IsAnimatorEnabled == true .

When adding a VRC Contact Sender and changing the size of it, it limits at 20 which is not documented in https://creators.vrchat.com/avatars/avatar-dynamics/contacts page. But when you go into the negatives of the Radius for a Capsule shape it inverses and goes past these limits in the Unity editor.

To my knowledge, we have many constraints available to us via the default unity constraints. We can also use some extended scripting when it comes to Final IK. I’ve used much of this when making quadrupeds, characters with two heads, and extra arms. However, all of these systems are calculated in world space only. For Avatars, I am not aware of any way to work with these constraints in local space. This would be very helpful when trying to map the rotation of your arm or fingers to puppet something not directly connected to your arm or hand. Right now I’m thinking of controlling wings or ears with fingers. This level of puppeteering is significantly better than using the menus or gestures, but we don’t yet have good access to it. In my own experience, I specifically ran into this issue when trying to directly control the back legs of a quadruped with my real legs. When facing straight ahead, I could puppet them just fine, but once I curved the spine, the feet would remain pointed forwards. I can’t imagine that this functionality would be too difficult to create. Most other unity games just copy the rotation values from one object to another and they are done… but obviously there needs to be some safety nets in place for cycle checks and other errors that might happen. I did my best to try and find if a similar topic already posted, there may be one, but I couldn’t find it. This post is partly a “What work around are there?” As well as a plea to add this functionality to the SDK.

When no user-created animation controller is provided for the FX playable layer, animations on a user-created Gesture playable layer fail to animate properly in-game (though they work in-editor). Simply adding a completely empty animation controller to the FX playable layer slot fixes this issue. This suggests that the client-provided controller for the FX playable layer is interfering with the Gesture playable layer in some manner. The debug menu shows the layer in the correct state and with the correct layer weight, but it does not animate until an FX player layer is provided by the user rather than the client. I have created a sample project based on the current avatars SDK to showcase this issue. It includes two copies of a minimally configured avatar in the scene TestScene -- one labeled working, and one labeled as broken. The only difference between these two is the empty FX layer defined on the avatar descriptor for one but not the other. The animation in question is some very noticeable rapid ear movements. https://github.com/nnaaa-vr/VRCBugReport_GestureIdle