Bug Reports

I run an event that fills up pretty quickly once we announce that guest doors are open. We open the the instance as a group instance with instance queue enabled. After we get all of the staff into the world for the event, we announce on discord and in group pings that the instance is now open for guests to join. Guests should be joining and starting up a queue at the announced time. What they can currently do is use the "Show Go Button on Load" setting to preload the world and reserve their spot in the instance. We can't tell what guests are doing this because they don't load into the world, we have no idea who hass connected early. They simply join the world with everyone else once the ping has gone out. You can test this easily with 2 other people. 1) Create a group instance with a queue for a world with 2 max slots. Just the two of us works well. 2) Have the instance owner join first and load into the world. 3) Have the person who will use the "Show Go Button on Load" join the instance, but not press the join world button. At this point, the person inside the instance does not see anyone else in the world. The person in the load screen has reserved their spot in the world. 4) Have a third person attempt to join the instance. They will either be placed in queue, or receive an error related to needing to join a queue but it will not place them in a queue. From the perspective of the person inside the instance, no one has joined. The third person cannot join the instance and MAY be able to queue. The second person that is waiting to join can join freely at any time. I do not know how long this instance slot reservation lasts, but it is causing significant issues with group instances with queues.

When Collision Mode was set to "Hit Players" or "Hit Worlds And Players," my own avatar was hit, but other players' avatars were not. When using "Hit World" or specifying "Pickup" in "Hit Custom Layers," the target was hit correctly. Do other players' avatars also need to be running SDK 3.10.3?

1 : Open the VRChat Menu. 2 : Go to the Marketplace/Store tab. 3 : Search for and select the Stellar Conduit portal. 4 : Wait for the 3D preview to load. 5 : Observe the FPS drop. 6 : Exit the store and try to show an avatar.

With the new VRC+ exclusive Shimmering Warp effect I noticed there was no option to archive it. I have Random selected and wanted to take out the new effect so it isnt part of the random selection. Current way to do this is by archiving a cosmetic, but with it missing im forced to have it in the random effects.

Once your friend count exceeds 2,000, it takes a very long time to load instances. I’ve been playing VRChat for nearly six years. I look forward to visiting various public instances every day. However, since my friend count increased, I’ve started experiencing a wait time of about 3 to 5 minutes every time I move to a new instance before it loads. I suspect that the system reloads the entire friend list every time the instance list is displayed, so I’d appreciate it if there were a better way to resolve this. Alternatively, I think a feature that allows users to bulk-manage friends they haven’t seen in years or have only met once could help prevent friend counts from growing excessive Translated with DeepL.com (free version)

Now that Scalers are possible through OSC (essentially using the same system that Scaling worlds use), this is a bug that's been bugging me ever since the scaling world features came out. Whenever you scale past 20 meters, it is exceptionally noticeable. 1) Go to any World scaler (Jet-Dog's Prefab world is a good place to look at it. Otherwise Little Big Town) 2) Scale up to 100 meters 3) Check your Personal Mirror (or camera), move your head around and watch your eyes go cross-eyed. What is happening (As I understand it): Avatars have a fake-gaze target that the eyes will point at when no face tracking is available. When you scale to larger and larger sizes, that Fake-gaze position gets closer and closer to the avatar. The distance to that fake gaze target stays the same distance, but the avatar itself is larger. Meaning that the fake-gaze target does not scale along with an avatar. To put what's happening into words for example: At 2 Meters -> Fake gaze target is 4 meters away (Not sure if this is the actual number but it's just for example's sake) At 5 meters -> Fake gaze target is 4 meters away At 10 meters -> Fake gaze target is 4 meters away (unnoticeable) - This is equivalent to something being about 80 centimeters away At 20 meters -> Fake gaze target is 4 meters away (Barely unnoticeable) - this is equivalent to something being 40 centimeters away from your face At 50+ meters -> Fake gaze target is 4 meters away (VERY noticable) - this is equivalent to something 20 centimeters away from your face up to looking at your nose and being crosseyed. Very annoying and long-standing bug, I wish it were fixed. (Cannot confirm or deny if this happens on Quest, I only play on an Index and see it on PC)

VRChat using absurd amount of RAM, more likely on longer sessions (around 2-4 hours). I haven't played around with it too much to figure out things that could be causing it, but I have noticed that the longer the play session, the more likely it is to happen. Ends up using all of my available RAM, causing freezing and stuttering which can only be solved by restarting VRChat. Does not reset on world/instance rejoin, or going to a new world. I have noticed that RAM usage will be stable, then at some point, it just starts to pile on more and more. ONLY happens on VRChat, every other VR application and non-VR application doesn't do this. Don't know if the results are different on Desktop. This has been happening for a while now and I first started noticing it with the release of the Lunar New Year items update. Maybe could be something that happened there?

The Video Player has accumulated quite a few small bugs and inconveniences over time. If technically possible, I would greatly appreciate it if these issues could be addressed. --- Black Flickering Issue with AVPro Player This problem started occurring shortly after the switch to Unity2022. The latest versions of iwaSync and YamaPlayer include their own workarounds, but older versions of iwaSync/YamaPlayer (when using AVPro) as well as players without custom fixes such as TopazChat Player still suffer from black flickering. --- Video Stuttering During RTSP Playback in Specific Conditions Especially in crowded instances on lower-spec PCs, When streaming RTSP at 60fps while VRChat is running at around 20fps, the video becomes noticeably choppy. Although switching the RTSP stream to 30fps currently avoids the issue, many users set OBS to 60fps because the TopazChat Player distribution page states that 60fps minimizes audio delay. --- Request to Move Video Player Processing to a Separate Thread Especially in crowded instances on lower-spec PCs, video playback often freezes for a moment due to various other processes. With RTSP streams, these interruptions cause playback delay to accumulate. The main causes include: Loading process when someone joins or when an avatar is changed Photo capture processing Display/hide toggling when culling is enabled Loading of stage effects on world VRChat's current CPU processing relies heavily on specific thread performance. On modern CPUs, specific thread often maxes out at 100% usage while the remaining threads (including E-cores and CCD1) stay underutilized. Separating the Video Player's processing into its own unrelated thread could potentially resolve these stuttering and lag issues. It may also allow better utilization of currently idle CPU cores.

To be more precise: once you see an avatar in an instance and load in its assetbundle, the limits set with Maximum Download Size and Maximum Uncompressed Size won't apply to it for some reason as long as that assetbundle is in memory. STR Open VRC Set your Maximum Download Size and/or Maximum Uncompressed Size to something tiny like 0-10MB join an instance with other people, observe their impostors select a person with an impostor, force-show them, and see their full avatar disable the force show (set avatar display back to the shield) what should've happened: the avatar should reload and show the impostor again what happens: the avatar 'reloads' (becomes a blue diamond thing for a sec), but loads back in fully visible This isn't strictly related to force-showing people, it also happens if you lower your settings while in an instance with people that you can already see - no matter how you set these settings, they're gonna keep being visible. You'd need to hide everyone, or they all would have to change to different avatars, for over a minute to get rid of their assetbundles to see the proper impostors after un-hiding/them switching back. hiding avatars by performance rank works fine. noticed it first earlier today on build 1836, and now confirmed it still happens on 1837.

Opening Action menu and going in Looks part, i noticed there is no 'Disable Look' option. So i am forced to add extra slot for setup without anything on it. That is just extra slot wasted. Should add button (just after Back button) so your avatar will normal again without anything on it. This can be confusing for new players why they cannot reset / remove it. It's weird they are forced to make new one without accessories on it. Also good reason because the picture is very small to find one without accessoires on it. A text button is quicker read too, less frustration. I made mine as example and you can see it's very small picture to find one without... bruh. Can you see which one has nothing on it? Please add it. Much easier!