Bug Reports

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.

“Hidden” is expected to almost completely hide being a member of that group, but it actually reveals membership to friends who belong to the same group. This is inappropriate behavior for “Hidden,” so I feel it should be changed to behave as expected. If this is the intended specification, the label should rename to something more suitable.

This is tested with 13 4K PNG textures; normal compression (first image), normal compression + crunch compressed at 50% quality (second image). Contrary to popular belief avatar download size (as suggested in unity) is not significantly reduce for avatar uploads; VRChats LZ4/LZMA compression is already handling the heavy lifting of download size reduction so there is evidently severe diminishing returns to using crunch compression. From my understanding the LZ4/LZMA algorithm is exceptionally good at finding and removing redundancy. Adding Crunch compression on top provides diminishing returns because there's little additional redundancy for LZ4/LZMA to compress. Here is what needs to be addressed immediately: Uncompressed size being drastically reduced in avatar stats when fundamentally this is not what crunch compression does. This in turn is letting people bypass the 500mb uncompressed download size limit. This whole dilemma could be resolved by simply disabling crunch compression for avatar, especially since crunch compression will cause loading textures onto the GPU to be a bit slower for virtually no reason.

Open the store and go to the animated sticker "VRCat's Spring Vacation". You will see that it doesn't properly show the image in the preview images. It instead shows as the sprite sheet. It should probably just look like a still image of the first frame.

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

ProTV flickers slightly on the current beta and not release vrsion

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.

Tested on quest 2 with steam link and gestures locked, but possible to reproduce on other controllers too. For exampe, you can notice the index finger on the right hand is less spread out than left one

Groups disappearing or appearing at random moments, and friend's disappearing in the public group menu but then re-appearing when you load into other worlds and sometimes you aren't able to join the public world where your friend is at and at times when you do join, it glitches and says the friend is either not on or I just simple can't join.

hi my prints at 59/64 i can't take any print because i have friend she deleted her account or deactive it her name rukiharu can you delete those 5 hidden photos of her so i can take the 5 extra prints please