Bug Reports

When tabbed out of VRChat (Irregardless of how it was done, tab, windows key, etc.) the cursor will remain active on screen at all times. If this is a intended feature, it would be greatly displeasing for streaming type content. This only started with the new UI update, so I'd assume it has something to do with the new HUD elements (Specifically on Desktop).

In the latest SDK Update 3.10.5 whenever any physbones get toggled off and on again in play mode they do not disable and instead have the settings you have set applied again over the Physbones over and over again each time they are toggled off and on. It doesn't happen in game thankfully but in unity when trying to test Phys bone settings, enabling and disabling the Physbones or their bones no longer works correctly. Downgrading to 3.10.4 fixes the issue so I've been staying on that version for now but I'm worried about this bug staying in the sdk especially when I will eventually have to update for the face tracking update. To reproduce and see it obviously just have a physbone chain with some gravity and gravity falloff on it and in play mode toggle to the physbone script off and on again a few times and you'll see the gravity getting multiplied each time its toggled off and on might have to have reset when disabled turned off and animated physbones turned on aswell

As title says

After the update last night, it looks like most MMD worlds—and I’m assuming other worlds that use special station setups—are currently broken. From what I’ve been told, the issue seems to be that the local animation is breaking while the world animation continues to work. What I’m seeing in-game: Avatars start moving normally with the animation from the station. After a couple of seconds, they stop and just stand still. I’ve also noticed that if someone toggles something on their avatar while the dance animation is playing, it can cause the animation to break as well. So far, this appears to be related to the latest VRChat update rather than an issue with the MMD setup itself. Multiple worlds affected - here are two examples https://vrchat.com/home/world/wrld_3dfd4b3b-175f-438f-8d4d-ac553bea0dce/info https://vrchat.com/home/world/wrld_2120ec29-10ba-4ef7-8912-52f1edc5199d/info

Description What I expected is to join is a group public server but instead it sent me to my home world instead of sending me to the group public same goes with invites Reproduction Steps I’m not sure really but please fix it soon its annoying so if you see this at least look into it I’m sure other IOS users have experienced it already. Details Category: World Frequency: Always --- platform: iOSMobile (platform: iOS - Mobile, store: TestFlight, headset: None) rawPlatform: IPhonePlayer clientVersion: 2026.3.20201 unityVersion: 2022.3.22f2-DWR In-Client Report

Reproduction. Open Vrchat while using hand tracking. Open quick menu. Description. Right hand not interacting with the quick menu while using hand tracking. Can't interact with people's bubbles either, with just the right hand. Video Attached. Category: Menu/UI Frequency: Always Side note* This is not game breaking, but I'm sure it's not intended. And a bit annoying as someone who uses hand tracking every day.

After last night’s update (1919), using the triggers to interact with anything (UI, world objects, etc.) on Steam Frame Standalone requires an excessively hard pull of the trigger. This was not the case before the most recent update and makes doing literally anything much harder. To make matters worse, going to controller settings in the in-game menu simply displays a screen that you’re using an unrecognized controller with no options to fix it. This issue only applies to the standalone build of VRChat on Frame. Frame controller trigger sensitivity remains consistent with prior builds when streaming from a PC.

OnPlayerTriggerEnter, OnPlayerTriggerExit and OnPlayerTriggerStay DO NOT FIRE when the player is in a station. This breaks events, manual culling, zone switching, and thousands of other map features across the entire game, when a player simply gets in a chair. I had to give up on a zone culling system because a map had vehicles and was not about to implement a custom Trigger Enter event solution (I did but it only supported axis aligned cubes) This was bug reported in 2021 and it's still not fixed!!! It's 2026 guys let my maps work correctly please!!!

On the Steam Frame standalone build of VRChat, the menu setting for snap turning does not save upon restarting the app. Smooth turning makes me incredibly nauseous and having to re-enable snap turning every single time I launch VRChat is extraordinarily irritating.

## Summary On an AMD Radeon RX 6650 XT, with VRChat's Anti-Aliasing set to x2 (MSAA), using a world mirror causes props that display a RenderTexture (screens / video players / custom-shader props) to render corrupted: a black center with multi-colored (red / yellow / blue / green) flickering bands around the edges. The corruption persists after leaving the mirror, and clears only when the player looks away from the affected prop and back. VRChat's in-game camera captures the same props CORRECTLY while the main view is corrupted. Setting Anti-Aliasing to Off completely resolves the issue. ## Environment VRChat Build: 2026.3.3-1919-27c41b24d2-Release Unity Version: 6000.0.67f1-DWR Graphics API: Direct3D 11.0 [level 11.1] GPU: AMD Radeon RX 6650 XT (RDNA2 / Navi 23), 8 GB VRAM Driver: AMD Software Adrenalin Edition 26.9.2, driver 32.0.21045.11001 (2026-09-25) OS: Windows 11 Pro, build 26200 Display: 1920x1080 @ 180 Hz World where reproduced: wrld_0f204305-922c-4548-9008-12d4ac2d1da6 VRChat Graphics Settings: Quality = Low, Anti-Aliasing = x2 (reproduces) / Off (fixed) Launch options: none relevant (issue reproduces without any launch options) ## Steps to Reproduce Set Settings -> Graphics -> Anti-Aliasing to x2 (MSAA). Join a world that contains a mirror (VRC_MirrorReflection) and at least one prop that displays a RenderTexture (e.g. a screen or video player). Open / look into the mirror and observe the scene through it. Exit the mirror view and look at the RenderTexture-based prop. ## Actual Result The prop renders with a solid black center and multi-colored (red / yellow / blue / green) flickering bands around its edges. The colors shift as the camera rotates. The corruption persists even when no longer looking through the mirror. Looking away from the prop until it leaves the view, then looking back at it, restores correct rendering. VRChat's in-game camera renders the same prop CORRECTLY while the main view is corrupted. ## Expected Result Props should continue to render normally after using a mirror. ## Workaround Set Settings -> Graphics -> Anti-Aliasing to Off . With MSAA disabled the corruption no longer reproduces. Reducing the mirror resolution or avoiding the mirror also prevents it. ## Log Evidence Warning - 'R8_SRGB' is not supported. RenderTexture::GetTemporary fallbacks to R8G8B8A8_SRGB format on this platform. Use 'SystemInfo.IsFormatSupported' C# API to check format support. at VRC.SDKBase.VRC_MirrorReflection.RenderMirror (UnityEngine.RenderTexture targetTexture, UnityEngine.Vector3 camPosition, UnityEngine.Quaternion camRotation, UnityEngine.Matrix4x4 camProjectionMatrix) at VRC.SDKBase.VRC_MirrorReflection.RenderMirrorCameras ( UnityEngine.Camera currentCamera, VRC.SDKBase.VRC_MirrorReflection+ActiveRenderModes visibility) at UnityEngine.Experimental.Rendering.ScriptableRuntimeReflectionSystemWrapper .Internal_ScriptableRuntimeReflectionSystemWrapper_TickRealtimeProbes (System.Boolean& result) ## Hypothesis RenderTexture::GetTemporary is Unity's pooled temporary render texture. The mirror and RenderTexture-based props draw from the same pool. On this AMD configuration R8_SRGB is reported as unsupported and Unity falls back to R8G8B8A8_SRGB . Combined with the extra MSAA resolve pass performed by the mirror's render texture, the pooled RT appears to be handed back with a mismatched format / stale binding state, so props that sample a RenderTexture receive scrambled channels (black center + rainbow banding). The in-game camera being unaffected indicates per-camera render state pollution rather than asset or shader compilation corruption. Disabling MSAA removes the resolve pass and the issue. ## Attachments Two screenshots taken 2026-10-04 08:48 (local time) while the bug was active on the same prop.