Avatar Bugs & Feature Requests

Currently, you can have an avatar rated as “Good” at 70,000 polygons, but adding even a single triangle beyond that will instantly drop the rating to “Very Poor.” Obviously, this doesn’t make much sense and can actually discourage some people from optimizing their avatars. (Why bother optimizing other stats if the polycount alone tanks the rating the moment you go over?) I’d like to suggest increasing the polygon thresholds for Medium and Poor ratings, with a gradual step-up between each level. This would make a lot more sense and give creators more flexibility! I’d really love to see this system improved. The VRC team should ultimately decide on the final values through proper testing, but personally, I think a Poor rating could go up to around 120k, and Medium could sit around 90k. Of course, those numbers are just based on my experience, and I’m sure the team can come up with even better thresholds through data and testing.

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

I would llike to see the camera have a depth filter for taking pictures like this:

When using upper body camera tracking, if you use a mascot-type avatar with a large head, the face mirror target becomes too low and your stomach or neck will be reflected. I would like to stream camera tracking with a mascot-type avatar from my desktop, so please fix this!

Version 3.8.1 of the VRChat SDK will include the following feature: Per-platform overrides allow you to configure different versions of your cross-platform avatar for multiple platforms. When you build & publish your avatar to more than one platform, the SDK automatically uploads different versions of your avatar to each selected platform under the same avatar ID. Per-platform overrides make it easy to upload an optimized version of your avatar for Android and a fully featured version of your avatar for PC. https://vrc-beta-docs.netlify.app/releases/release-3-8-1/

I think it would be very beneficial to have a native VRC parameter "IsAgeVerified" such that I and other creators can lock certain functionality behind the age filter.

I would like to propose the addition of native parameter smoothing functionality within VRChat, directly supported by the VRChat client and SDK. Currently, creators must rely on animator-based feedback loop smoothing to mitigate the slow network update rate of float parameters, particularly for advanced use cases such as full face tracking. However, this approach introduces significant inefficiencies and complexity. Feedback-loop smoothing via animator logic results in extremely bloated and overly complex animators. This not only complicates the animation setup process, but also has measurable negative performance impacts. Based on my own testing and benchmarking, a single avatar using full facial tracking with feedback-loop smoothing can increase CPU frame times enough to cause a 5–10 FPS drop in CPU-limited environments, with mirrors disabled. It is 100% reproduceable especially with OSCmooth and Pawlygons facetracking templates. This is purely based on the smoothing logic only, not the actual facetracking logic. The performance degradation scales linearly with the number of face-tracked avatars present in a given instance. This makes the current approach unsustainable, especially as more users adopt advanced tracking setups. I propose that VRChat introduce native parameter smoothing functionality configurable directly through the VRChat Unity SDK. This could be implemented by expanding the existing animator parameter list interface in the SDK to include: A checkbox to enable native smoothing on a per-parameter basis. Two smoothing strength values, ranging from 0.0 to 1.0: Local Smoothing: Applied to the user's own view of their avatar (e.g., for responsive and accurate feedback). Remote Smoothing: Applied to how other users see the avatar (e.g., to compensate for low parameter update frequency over the network). This native implementation would eliminate the need for animator-driven smoothing workarounds, significantly reduce complexity, and greatly improve performance across all facetracked avatars moving forward, especially in CPU-constrained scenarios (me 99% of the time, same can be said for most people nowadays). Such a feature would improve performance by a very measurable amount once it becomes standardized over the current hacky avatar-based feedback-loop method. It would also have huge positive implications for Mobile/Quest as they are much more CPU restricted, yet don't have any facetracking/animator limitations at all. We need more tools to optimize animators, and this would be a great step forward, thank you.

This odd error was found while using VRCFury on an asset I was "expanding" on. In short. The asset had 8 duplicates, each with their own ID, in turn the parameters are the same, with the exception of the last bit being their respective IDs. Ex: PiShock/Equipped/10 If you create a Menu Option as a, say Radial, gave it a parameter that either Currently Exists but later removed, or, never existed. Then change that Menu Option to a Toggle and set a different parameter, which does exist. The old parameter resides in the Menu's file (when viewed in Notepad, my case of image being Notepad++). Though I cannot say this would effect VRChat's Avatar SDK on a Vanilla level, it is hard to trace back when third party tools, like VRCFury, report that /7 is in use on the /10's menu file, yet in Unity it's not visually seen. Switching the Toggle to Radial or 4 axis, will show the incorrect parameter, which you can just simply delete, set back to Toggle, and all is fine. Though there can be multiple solutions, something to help show the old parameter still resides in the Menu Option, or maybe when the Type is changed, remove the old? I'm not entirely sure the best method to resolve the odd lingering parameters in the Menu files. The only way I was able to find this, was opening the Menu file in Notepad, and Ctrl+F the /7. When I reported this in VRCFury's discord, I was informed this same issue came up for another user back on June 6th, when said user duplicated a clothing asset, changed menu types, and resulted in errors for parameters that "shouldn't exist" in their duplicated asset's menu files.

I'm encountering an issue where my Android-compatible VRChat avatar, created using VCC3. and SDK3.8.1*, is not visible to myself or other users when I access VRChat via my Quest. Conversely, avatars I've created with VCC3. and SDK3.7.* or VCC4. and SDK3.8.1 display correctly. This suggests that updating VCC may resolve the visibility issue for affected avatars. Below is a relevant log entry from a friend who experienced this error: Error - [Behaviour] Error downloading avatar MURIYARIYUKATA/Security: Error loading asset bundle from ****: HTTP/1.1 403 Forbidden

In the Tracking controller behavior could we get Eye Tracking, Eyelids and blinking separated so they can be individually changed from animation or tracking using animators. For example I would like it to be able to disable the blinking and the eyelid movements when using face blend-trees but keep eye tracking itself.