Avatar Bugs & Feature Requests

Post about current Avatar bugs and Avatar Feature Requests. One item per post!
Non-constructive and off-topic posts will be moved or deleted.
SDK, local SDK test avatar and uploaded avatar report different material slots count when renderers have more material slots than sub-meshes
Please see the attached screenshots to explain the issue. I have an avatar which is reported as 4 materials in the local SDK test build and in the SDK, but as 5 material slots when uploaded. This occurs when a skinned mesh renderer has more material slots than sub-meshes. Avatar setup explained Armature Body (skinned mesh renderer): 2 materials ( Salt_Face , Salt_Face_Effect ) Hair (skinned mesh renderer): 2 materials ( Salt_Hair , Salt_Hair_FakeShadow ); 1 sub-mesh Hair_Base (skinned mesh renderer): 1 materials ( Salt_Hair ) Steps to reproduce This is how I did this: I got the Salt_v1.01 avatar by komado from BOOTH ( https://komado.booth.pm/items/8962830 ). I created a new VRChat SDK 3.10.6 project with d4rkAvatarOptimizer v4.7.2 and other avatar dependencies added from ALCOM. I added the Salt prefab to the scene. I deleted anything but Armature , Base , Hair , Hair_Base gameobjects. Hair will have two materials ( Salt_Hair , Salt_Hair_FakeShadow ; 1 submesh), Hair_Base has one material shared ( Salt_Hair ) shared with Hair gameobject. (Optional, not required) I added d4rkAvatarOptimizer component to the avatar (as a gameobject or on the avatar root), basic/standard optimizations with "Delete Unused GameObjects" checked. Build & Test. Build & Publish (upload). Compare the avatar performance details of the uploaded avatar and the SDK test avatar in the VRChat client (Build 1939 ). Expected result SDK & local SDK test avatar should report 5 material slots in the VRChat client. The uploaded avatar should report 5 material slots too. Actual result SDK & local SDK test avatar both report 4 material slots; missing one material slot . The uploaded avatar reports 5 material slots. Additional information d4rkAvatarOptimizer is not required to reproduce this bug. It should be reproducible with VRChat SDK 3.10.6 and the current live branch VRChat 2026.4.1 (Build 1939 ) client alone. I have confirmed the issue is not with the material shaders used. The default Salt avatar base FBX does not setup a 2nd material slot on the Hair renderer by default, this extra material slot was added to the prefab by the creator of the base for a lilToon fake shadow. Related d4rkAvatarOptimizer v4.6.0 change: https://github.com/d4rkc0d3r/d4rkAvatarOptimizer/pull/194 Related d4rkAvatarOptimizer changelog: https://github.com/d4rkc0d3r/d4rkAvatarOptimizer/blob/main/CHANGELOG.md#v460 I can provide private avatar IDs for minimal repro avatar versions on request, if specified which version(s). VRChat SDK - Avatars 3.10.6. d4rkAvatarOptimizer versions 4.5.4 , 4.6.0 and 4.7.2 (latest). The latter two d4rkAvatarOptimizer versions share the same behavior. VRChat 2026.4.1 Build 1939 on Windows.
2
·
Bug Reports
Graphics.Blit Scripts for avatars
(Edit: Added "for avatars" to the post title. VRCGraphics.Blit is available for worlds, but not avatars.) The Shader Community's Request for Graphics.Blit What is Graphics.Blit? Graphics.Blit allows you to copy a source texture into a destination render texture using a shader. Being able to do this allows for shaders to write to render textures in a manner that does not require cameras ---- Why do we want Graphics.Blit? Currently shader creators are using cameras and render textures to emulate what Graphics.Blit does. Cameras were not made for this purpose and have a relatively high amount of overhead. On top of this, in order to effectively mimic Graphics.Blit we need two cameras to achieve the same effect. This doesn’t mean Graphics.Blit replaces cameras though, it allows for most use cases to run much quicker. ---- What uses this camera workaround currently? GPU particles . Anyone who's experimented with GPU particles knows how much faster these particles run compared to Unity's built in particle system. GPU particles in their current form can run a million particles in 1.43ms on the GPU. That's amazing already, but because we have to use cameras, ~0.7ms of CPU time(camera0 and camera1) is spent on updating the cameras. Graphics.Blit can bring the CPU time from ~0.7ms to ~0.07ms. GPU particles are not the only shader which will perform better using Graphics.Blit. Any shader which has uses a 2 camera and render texture setup will be faster using Graphics.Blit. Other use potential cases for Graphics.Blit * GPU dynamic bones * Cheap Gaussian blur * Fluid Simulation * Grass/Hair Simulation * Procedurally generating Data * Virtual Keyboard for mutes * AI for Shader pets following you around * Simple games and puzzles. Pong, Flappy bird, and the beginnings of Doom have been done with cameras already * Worlds with snow dynamic, rain puddles, and water ripples ---- Why should time be spent on Graphics.Blit when only shader creators will be using it? Even though this is going to mostly only effect shader creators, everyone benefits from this change. GPU particles have been released to the public for a while and has been the only way for VRChat users to get millions of particle without completely destroying FPS. Graphics.Blit would increase the room for innovation. ---- What would a Graphics.Blit component from the VRC SDK look like? We would like to see two scripts added to the SDK, a Blit Controller, and a Blit Component. The Blit Controller should be a component which can be added to game objects on avatars and worlds. The Blit Controller should also have one input, an array of Blit Components. The purpose of this controller is to handle the order in which each blit is executed. In order for a shader to store stateful information, there need to be two render textures and two blits. The order in which these two blits are run is important, and this controller handle that. The Blit Controller component should run Graphics.Blit for every Blit Component in the array, in order. The Blit Component should hold two inputs, a source texture and a destination texture. Where is the material at? Well in order to allow shaders to be animated in VRC we think that using the shared material from the mesh renderer on the game object would be ideal. The blit component should have a RunBlit function which takes the mesh renderer’s shared material and runs Graphics.Blit with the source,destination, and shared material. Also the RunBlit function should pass a couple extra bits of information to the shader. Namely the game object’s localToWorldMatrix, worldToLocalMatrix, and position. We think this is important because with Graphics.Blit you get no outside information. Some of the existing camera effect require position information. We have included a GitHub link which contains a mock implementation of what we think would be the best way to implement this for the use cases we have. It is under the MIT licence so feel free to use anything from our implementation. We want to make this as easy as possible on development time. Our mock implementation: https://github.com/Merlin-san/Blit-Component We aren't sure if components update on both PlayerLocal and Player for the local player, but updating more than once per frame should be avoided if that's the case. ---- Safety System Currently the render texture/camera work around that we use requires that you are friends with another user in order for that user to see the render texture. This was implemented before the safety system. If Graphics.Blit is implemented, render textures should be either apart of the safety system under "shaders", or its own category under "render textures" The shader community, Toocanzs, Merlin, Elixir, Xiexe, Blake447, Okano, snail, Tykesha, .Captain., Claw, Quantum, Nulliel, Naelstrof, Wakamu, 1001, Nave, Neitri, SCRN, Silent
57
Load More
→