Bug Reports

VRChat intermittently crashes to desktop without an error dialog when joining a populated instance of Mafia Classic. World ID: wrld_80d828d2-ae5f-4fa5-aaaa-072b80096995 Other players have also reported crashes when entering this world, although their crash dumps have not been analyzed. REPRODUCTION Join a populated Mafia Classic instance. The world scene loads successfully. Player/avatar initialization begins. VRChat sometimes unexpectedly closes. Frequency: intermittent. Both empty and populated instances have also been entered successfully. EXPECTED The client completes initialization and enters the world. ACTUAL The client crashes to desktop without an error dialog. CRASH EVIDENCE I captured two crashes on October 18 and October 20, 2026. Offline analysis found the same complete 22-frame native call stack in both dumps: UnityPlayer.dll version: 6000.0.67.6863 Exception: 0xc0000005 Fault offset: 0xb11b2d Invalid read from address 0x58, with R13 = 0 Call chain enters UnityEngine.Animator::Update_Injected with zero delta time: Animator.Update(0). The final log messages in both cases concern remote avatar limb initialization. No Udon runtime exception was recorded during the failed entry. The specific Animator, avatar or world object responsible has NOT been identified. The last avatar mentioned in the log is not a confirmed cause. ENVIRONMENT VRChat 2026.3.3p2-1921-15c4a824b2-Release Windows 11, build 26200 Steam installation, Direct3D 11 NVIDIA GeForce RTX 3060 Ti, 8 GB VRAM 32 GB RAM Crash dump, full logs and detailed analysis were submitted privately through support ticket #745343. Could you investigate the native Animator.Update(0) crash path and advise what additional diagnostic information would help identify the trigger? World ID: wrld_80d828d2-ae5f-4fa5-aaaa-072b80096995 Other players have also reported crashes when entering this world, although their crash dumps have not been analyzed. REPRODUCTION Join a populated Mafia Classic instance. The world scene loads successfully. Player/avatar initialization begins. VRChat sometimes unexpectedly closes. Frequency: intermittent. Both empty and populated instances have also been entered successfully. EXPECTED The client completes initialization and enters the world. ACTUAL The client crashes to desktop without an error dialog. CRASH EVIDENCE I captured two crashes on October 18 and October 20, 2026. Offline analysis found the same complete 22-frame native call stack in both dumps: UnityPlayer.dll version: 6000.0.67.6863 Exception: 0xc0000005 Fault offset: 0xb11b2d Invalid read from address 0x58, with R13 = 0 Call chain enters UnityEngine.Animator::Update_Injected with zero delta time: Animator.Update(0). The final log messages in both cases concern remote avatar limb initialization. No Udon runtime exception was recorded during the failed entry. The specific Animator, avatar or world object responsible has NOT been identified. The last avatar mentioned in the log is not a confirmed cause. ENVIRONMENT VRChat 2026.3.3p2-1921-15c4a824b2-Release Windows 11, build 26200 Steam installation, Direct3D 11 NVIDIA GeForce RTX 3060 Ti, 8 GB VRAM 32 GB RAM Crash dump, full logs and detailed analysis were submitted privately through support ticket #745343. Could you investigate the native Animator.Update(0) crash path and advise what additional diagnostic information would help identify the trigger?

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).

Happened upon launch

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

When an OSCQuery notification appears for a new connection it re-uses the icon from the last notification you got instead of its own

The latest beta update seems to have silently added a new OSC endpoint /avatar/name that sends out the avatar's name. This breaks when the avatar's name has complex UTF-8 characters. The characters seem to get truncated to a single byte, which most OSC applications cannot correctly decode. Debug menu "Version & Info": S:Release_1626 V:2026.4.1 This is extremely easy to reproduce with any avatar that has a ! in its name, as that character gets transformed to U+01c3 on upload, which then gets truncated to a c3 byte when sent over OSC, which cannot be decoded as valid UTF-8 (or ascii) This is even more noticeable with avatars that contain Japanese character in their names.

When joining the spookality worlds that allow gift trains. It temporarily shows a box saying "Time starts counting now Nov1, 00:00 UTC." It shows up whether or not a gift train is running. I don't think this is expected.

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.

When using a custom Font Asset after the Unity 6 update, missing glyphs (such as Korean characters) no longer correctly utilise fallback fonts. Instead, they render as missing block characters. If the built-in default LiberationSans SDF is used, the fallback mechanism works as intended. I have tested multiple fallback configurations, none of which resolved the issue: • Linking LiberationSans SDF explicitly as a fallback inside the custom Font Asset. • Linking it in the TextMeshPro Project Settings. • Leaving all fallback fields empty to let VRChat's system handle the fallback behaviour. Attached Files: • Image 1 & 2: Expected behaviour before the Unity 6 update (English and Korean glyphs rendering properly). • Image 3: Current broken behaviour after the update (All non-ASCII text converted into blocks).

As title says