Bug Reports

In larger events, its not uncommon for people to pull out something like the bubbler and start using that during certain times. Currently it seems there's no limit on the number of new, global audio sources spawned by this (i.e. 80 people with bubblers == 80 new audio sources, minimum 160 audio sources on top of avatar audio & world audio). This causes audio issues like stuttering, albeit I'm unclear if its VRChat, Unity, or AVPro at cause (hard to reproduce, sorry!). A specific failure case is a large music event with 80 people in a small area, lots of people pull out bubblers, and then the music stream stutters due to this. This issue was immediately resolved by disabling items As a practical matter (and also looking to the future) nobody would ever want to hear this many item audio sources at once. Its overwhelming & provides little value after say 5x of the same type, and is likely to cause audio issues if unchecked. Additionally, although a moot point if the above is addressed, setting Items volume to 0 I suspect does exactly that and lowers the audio sources volume to 0, which does not _disable_ them from Unity's perspective. For all audio source sliders, disabling the audio sources entirely would be safer if volume == 0

Dear devs of vrchat, As an PROUD Indian man, I find it profoundly disheartening that my mother tongue, Hindi, has been spelt incorrectly in its native Devanagari script in the "choose language" sub-menu. While I can understand that the limited abilities of the Anglo-Saxon mind are not suitable to grasp the intricacies of the vastly superior Indo-Aryanic alphasyllabary, human faculty for pattern recognition and the discernment of shapes emerges during the earliest stages of cognitive development, thereby eliminating any justification for such an egregious and inexcusable error. I demand that you fix this error with the correct spelling (हिन्दी or हिंदी) immediately. attached are the screenshots of this bug. >:(

Reopening https://feedback.vrchat.com/bug-reports/p/local-players-dont-cast-shadows-caused-by-lights-in-avatars-on-cameras Expected behavior Objects comprising local players cast shadows in cameras similar to a player's view. Actual behavior Objects comprising local players do not cast shadows on cameras. "Cameras" means both photo camera and Camera components in avatars. Description / How to reproduce 1. Open test world I prepared a world for testing culling behavior: https://vrchat.com/home/world/wrld_8d64c603-280f-4dd9-811e-d1db875676ad This world contains spheres for each layers. (see also: https://feedback.vrchat.com/bug-reports/p/culling-mask-for-lights-in-avatars-modified-unexpectedly ) 2. Switch to the test avatar Switch to the test avatar that has a light with shadow. 3. Check casted shadow In the first-person view, the sphere in PlayerLocal layer is casting shadow. In the camera view, the sphere in MirrorReflection layer should cast shadow but actually not. It is tested with world object for easy observation, but meshes in the local avatar behaves similarly. Environment VRChat build 1392

Changing custom shield levels to toggle User Icons are not resulting in the user icon for friends and non-friends to be blurred. The expected result, would be the user icon would be blurred upon changing settings. EDIT: User icons will update upon reloading the instance, but unblurring user icons will stay blurred until rejoining,

The number of animation layers heavily affects performance due to unnecessary inverse kinematic calculations. Even blank animation layers with zero weight in the FX layer can trigger this behavior. The offender is seen in the profiler as Animators.IKAndTwistBoneJob. It runs as many times as the currently loaded animation controller with the largest number of layers. Although the individual run time is small, they very quickly add up. Slower CPUs seem to be more adversely affected by this. The time taken by these extraneous calculations quickly grows larger than all normal animator activity. This behavior only happens on animators that have a unity avatar/armature. When that is removed, this behavior goes away and the number of layers ceases to be a significant cause of lag. Most FX layers do not have any interaction with the armature, so it is likely that this behavior can be fixed for almost all FX layers. However from debugging the unity editor in visual studio, it appears the this happens in a native unity function named Animator::UpdateAvatars. It is likely that in most if not all cases, these calculations are completely wasted on FX layers and provide no benefit at all while consuming significant amounts of main thread time. Somehow these calculations need to be only run for layers that require them. Additionally providing a way to get parameters in sub animators would allow logic to be moved out of the main animator completely sidestepping this problem. They would not have a unity avatar associated with them, so this problem would not occur. It would also allow completely disabling animators when not in use. Please attempt to find a way to prevent this behavior or consider convincing your Unity contacts to implement a fix. This seems to be one of the largest contributors to animator lag. I have a full write-up with more profiler images and further explanations. https://docs.google.com/document/d/1SpG7O30O0Cb5tQCEgRro8BixO0lRkrlV2o9Cbq-rzJU

When the camera is used in selfie mode, the captured image is saved with the left and right sides reversed. (When the camera is pointed at you by changing the lens orientation in the upper left corner) Normally, the avatar in the attached image has a yellow left eye, but it is inverted and has a right eye.

UPDATE: Please read the comments I've left below on this post to get more information and or updates! UPDATE #2: Video attached -> https://www.youtube.com/watch?v=XsZ-ticOUUo Launch VRChat. Use a tool like RTSS to monitor frametime and VRAM usage. Open the Tracking & IK settings. Toggle Selfie Expression on and off repeatedly. (Make sure to wait for Selfie Expression to fully load in first, it takes a second or two every time it's turned back on.) Observe RAM and VRAM usage gradually increase each time you toggle it, instead of returning to normal. VRAM & RAM usage gets even worse if you do the following. Reproduction steps: Set selfie expression quality to Best Quality (higher quality will make the memory increase more noticeable). Then enable Selfie Expression, wait until it loads in fully, then turn it off, then turn it on again repeatedly. As you repeat this part, VRAM usage goes up by a moderate amount each time, but does not go down. When VRAM steadies or does not increase, Turn Selfie Expression off, then walk around for a minute or two or stay at the same screen. Change Selfie Expression to any quality, and then repeat step 2. What I saw: VRAM usage will keep going up and up until maxed out, then will fallback to RAM but doing steps 2, 3 and 4 repeatedly enough will cause RAM to be maxed out alongside VRAM. Higher-resolution webcams result in much larger memory increases per toggle (each frame/buffer/texture is bigger), so VRAM fills far faster at 1080p/1440p/4K and using higher Selfie Expression quality amplifies this effect. Workaround: Re-joining the instance, joining a different instance or restarting VRChat fixes it and usage returns to normal level.

Currently mobile clients should be able to show very poor avatars up to 4 by changing Avatar Display Setting (a.k.a. "show avatar"). However clients can't show them by the usual operation. It's an inconsistent way with Quest. Reproduction steps: Join to an instance. Select a player who is using a very poor avatar (imposter). Change Avatar Display Setting to show the avatar, but it's reverted to the default. <- Issue You can show the avatar by using double-tap in the step 3. Once avatar display settings has been successfully changed, you can properly change the setting with single tap until you leave the instance. Environments: Android: 2025.3.2 (Build 1695) iOS: 2025.3.1 (Build 1681) Japanese summary: スマホ版でVery PoorのアバターをShow Avatarしようとしても設定を戻されてしまい表示できない不具合。 設定変更のボタンをシングルタップでなくダブルタップすると表示でき、インスタンスを抜けるまでは正しく設定変更することができる。

in unity 2022, the "Z Bias" setting was added to the MSVO effect in the post processing stack v2 (vr compatible ambient occlusion), which fixes much of the flickering of AO in vrchat, but currently the setting does not end up working in game likely due to miss-matching version of package in game. many creators use this effect in larger worlds for better shading as lightmapped AO is not possible in many cases, please update the package, it would reduce a lot of visual artifacts in vrchat worlds.

Title is explanatory; when opening a new instance, and you input a name that fails (I used emojis, which always fail), any time that you use any valid re-name that is supposed to work, will fail.