Bug Reports

For Deaf users, the chatbox is a primary communication method. Typing text is equivalent to voice chat for hearing users. When typing at a normal conversational speed, the chatbox frequently triggers spam detection and applies a timeout. This occurs during regular back-and-forth conversation, not intentional spam. As a result, Deaf users are temporarily prevented from communicating at all, because our primary communication tool becomes unavailable. This creates an accessibility barrier where none should exist. This is not an improvement, but a big step backward in accessibility for Deaf players. I do not use TTS, so chatbox access is essential. Please excuse my English, as British Sign Language (BSL) is my first language.

Go to the Fishing world. Fish for a few hours (5-6) Sell all the fish. Rejoin (Not sure if important that I'm the last one in the instance) The "Transmitting Important Data. Please wait a moment while VRChat trasmits your saved data." popup took an hour and a half last time. So far it took twice around 5 minutes. Once it took 15 minutes and another time it took an hour and a half.

Following up on this completed Canny and developer update from last month , the issue isn't fully resolved. Group members with the "Create Members-Only Group Instances" permission do not see the ability to make group public instances in the VRChat client, but they can still make group public instances and invite themselves by manually crafting a public instance link in the browser. Current mitigation until VRChat resolves the issue: Don't allow group members to open Group instances. Enabling Group+ instance creation does not allow the exploit. The last exploit was left open for over a year. I hope this one won't see the same treatment. I'd really like to allow our group members to create their own group instances without the risk of having unauthorized public instances opened. Thank you to our community member Joakorex for bringing this to our attention. <3

Summary Since around February 28, 2026, connecting through Cloudflare WARP (VPN mode) prevents logging in or properly using VRChat across all platforms — the website, Unity SDK, and the VRChat client app. This is problem, because VRChat's own help pages explicitly state that Cloudflare WARP is allowed: > "As a last resort for connection issues, try using a VPN. Cloudflare's WARP is allowed , but some other VPNs may be blocked." — VRChat keeps crashing or has issues launching properly > "Try using Cloudflare's WARP tool"— Troubleshooting Connection Issues with VRChat Symptoms (all with WARP enabled) 1. VRChat Website ( vrchat.com ) Login appears to succeed momentarily, then immediately redirects back to the login page. This loops indefinitely. (recording attatched to this post) 2. VRChat SDK (Unity Editor) Login fails with the following errors: (screenshot attatched to this post) - Unauthorized, try logging out and in again - "Missing Credentials" - NullReferenceException at VRCSdkControlPanelAvatarBuilder.cs:1491 Stack trace points to VRCApi.cs:288 in MakeRequestWithResponse 3. VRChat Client App (PC) Login itself succeeds. Immediately placed in the Error World. Cannot navigate to any other world — always sent back to Error World. VRChat is effectively unusable. All three services work normally when WARP is disabled. WARP was working fine with VRChat until approximately February 26, 2026. This timing coincides with the API and Social/Friends List maintenance on Feb 26–27 (per https://status.vrchat.com ). Why This Matters: Many Users Need WARP Many users, including myself, rely on Cloudflare WARP because without it, VRChat times out when loading other players' avatars , making multiplayer sessions impossible. The symptoms without WARP: Avatar loading for other players stalls completely → other players' movement/voice freezes → timeout → "VRChat is not responding" Occurs reliably with 10+ players in an instance; does not occur when alone Own avatar loading and world loading are unaffected This is a well-documented, long-standing issue reported by many users (see Related Reports below) The current situation means VRChat is completely unusable either way: WARP off → avatar loading timeouts in any populated instance WARP on → cannot log in / stuck in Error World Environment OS: Windows 11 Home CPU: 13th Gen Intel Core i7-13700F GPU: NVIDIA GeForce RTX 4070 RAM: 32GB ISP: Katch Network (Japan) Connection: Wi-Fi VRChat Build: Build ID 22116304 VRChat SDK: 3.10.0 Unity: 2022.3.6f1 Cloudflare WARP: 2026.1.150.0 (VPN mode) Attachments Video: Website login loop (to be attached) Screenshot: Unity SDK "Missing Credentials" error (to be attached) Related Reports WARP/VPN connection issues (same or similar problem): "World is incompatible with current platform" when using VPN and Cloudflare Warp Connection issues through Cloudflare's WARP Avatar loading timeout (the reason WARP is needed): Connection timed out or VRChat stopped responding error (too often) Recent increase in timeouts, disconnected, and not responding messages Frequent disconnections Connection Issues to VRChat (Possible Routing Problem to Photon Server) VRChat connection interrupted while downloading Avatars/Worlds Update: Output log analysis I compared output_log.txt captured with WARP ON vs WARP OFF. With WARP ON, every API call after login is rejected with 401 "Missing Credentials". The log reveals the reason: "authToken doesn't correspond with an active session" — and the source IP address (Cloudflare WARP IPv6) changes between requests. This may mean VRChat's API is binding sessions to IP addresses, but WARP rotates its exit IP on every request, so the server treats each subsequent call as an invalid session. This session-IP validation likely became stricter with the Feb 26–27 maintenance, as the same setup worked fine before that date. I have submitted a support request with full output log and details on VRChat Help Desk.

I switched the instance. Not sure how i triggered it. It didn't went away with selecting more accessories or rejoining an instance. it only went away after switching avatar.

My chat messages seem to either not load for minutes or i get timed out after 2-3 messages which makes communicating as a non-mic user kinda difficult. The problem only became apparent after the update

When Steam Audio was pushed to Live from Beta, (but not during beta,) many avatar sounds like those used in horror roleplay communities became much quieter or much louder, even dangerously so. Many of us adjusted our volume levels up and down to compensate, but I did way too much testing and found: Using default VRC_SpatialAudioSource settings, my test audio (with a lot of reverb and sudden attack) is overly compressed to nearly inaudible levels, sometimes as low as 20% - - This also caused creators to pump their volume up to compensate because we don't know what's really going on Using ANY of the advanced settings (near, volumetric radius, disabling spatialization, or using the audiosource volume curve) makes sounds play as as they do in Unity PLUS applying gain, making them LOUDER than they are outside of the game with the default Gain 10. - - Both Near and Volumetric Radius, separately, have volume at 100%+gain volume until you reach the end of their radius, then they sharply become very quiet or nearly inaudible until you reach the Far radius. - - This ends up allowing sounds that are dangerously loud, often unintentionally! I'm a bit crazy and wrote up a really detailed report here as I tested to understand what audio components were doing https://docs.google.com/document/d/14cukaZ_TlIyYHkErtD6E_z0QlCjDdVI58N1JkRAw_vI/edit?tab=t.0 ⚠️⚠️WARNING⚠️⚠️ the attached video is LOUD. I used earmuffs to visualize distance only. It shows 4 different audio sources with different settings on each: Default settings, which is Gain 10, Far 40, Near 0, Volumetric Radius 0, disabled Use Audiosource Volume Curve Default settings + Near 10 Default settings + Volumetric Radius 10 Default settings + Use AudioSource Volume Curve with 40 Max Distance on a Linear Rolloff Avatar for testing: (again, ⚠️ sounds are loud ) https://vrchat.com/home/avatar/avtr_f3133502-fdb8-4ea4-b612-6389767038a0

Enter the world linked below Or setup a world with interaction passthrough layers with one collider and one trigger. Attempt to interact with elements behind the trigger. Notice that Interaction Passthrough appears to work for the trigger as expected. Attempt to interact with elements behind the collider. Notice that Interaction Passthrough stops working despite both objects being on the same layer marked in the Interaction Passthrough mask. Creator docs and ClientSim appear to confirm that any GameObjects with colliders on layers marked in the Interaction Passthrough mask should be ignored by interactions regardless of the isTrigger state. The Client does not appear to match how ClientSim and the Docs show/describe the expected functionality, blocking interactions unless isTrigger is true. Test World: https://vrchat.com/home/world/wrld_af78331e-e8cd-49c5-a49c-0811851bae4c Attached are two videos showcasing the issue in live Client 1802 and it working as expected in ClientSim from SDK 3.10.1.

Ever since the chatbox "Send Text Automatically" live typing feature came out, I feel like I've been rated limited much more often just trying to chat normally. The chatbox stops working for maybe a minute, and the worst part is there's no indication that you've been rate limited, or when it's fine again.

When using the dolly camera system with streaming set to multi to run multiple paths at the same time, the zoom information and other camera parameters are not applied, even if they were programmed when placing the camera points. Only the first path that uses the main camera have the parameters applied on it. Others topic talks about the same issue for focus and exposure on VRCSender 2, 3, 4. https://feedback.vrchat.com/open-beta/p/dolly-1582-dolly-animated-focus-zoom-changes-freeze-when-camera-window-is-closed https://feedback.vrchat.com/bug-reports/p/1609-multi-stream-vrcsender2-3-4-cameras-do-not-have-bloom https://feedback.vrchat.com/open-beta/p/dolly-multistreaming-inconsistencies-between-cameras