Feature Requests

## Problem Coordinating identical camera angles between multiple users is slow and imprecise. Creators, photographers, streamers, and event staff currently align by hand or exchange coordinates, which breaks framing and continuity. ## Proposal Provide a command to place my camera at the exact position, rotation, and FOV of another user’s active camera. ## Suggested UX User Quick Menu → Select User → Camera → Match Camera -Position Options: - Include rotation ✔︎/✖︎ - Include FOV ✔︎/✖︎ - One-time snap or follow mode (continuous sync until toggled off) Rules and Permissions Target must have an active, shareable camera. Consent toggle on the target side: “Allow others to match my camera.” Respect privacy/visibility settings and world permissions. World creators can disable this feature per world. ## Why This Matters Faster multi-camera setup for events and shoots. Consistent framing across users for recordings and streams. Reduces coordination overhead and misaligned shots.

If there are buttons or chairs next to you while calibrating full body, you will trigger them. Please disable them, so we dont hop onto chairs or activate things unintentionally.

・Request When creating a group + instance within a group, enable settings to allow specific roles to join in advance. We would like only users with specific roles to be able to join until a designated time, after which all users can join. ・Reason During events, there are times when we wish to gather beforehand. Until now, we have often gathered in a separate instance, but moving instances resets the placement of drawings, objects, etc. If gathering and going live could occur within the same instance, this would be highly beneficial for various events—inviting guests, preparing corporate representatives, and more. ・Examples At music events, performers often gather beforehand for sound checks. This feature would prove invaluable in such scenarios. At exhibition events, corporate representatives sometimes wish to observe actual user traffic. If they could participate beforehand and observe people actually entering and enjoying the space, it would likely increase corporate satisfaction. For networking events, staff may require time for meetings. Allocating staff meeting time within the hosted instance would facilitate smoother event operations and enhance user satisfaction. Overall, I felt it would be beneficial as it would make it easier for influential guests, such as streamers, to participate, thereby increasing VRChat's exposure. Translated with DeepL.com (free version)

Thank you for your continued work on the development and maintenance of VRChat. Currently, VRCStringDownloader, VRCImageDownloader, and VideoPlayer all enforce a 5-second delay between requests. I assume this restriction exists primarily as a security measure — to prevent worlds from transmitting data externally without user consent — and I fully understand the reasoning behind that design. However, this restriction currently applies globally across all domains, and that behavior is causing significant usability issues in practice. For example, if an asset in a world includes components that use these downloaders, they all share the same cooldown timer. As a result, even content that should load immediately upon joining the world may be delayed for several seconds — or even minutes — depending on how many downloader requests are queued. In extreme cases, if just one asset tries to load 30 images at once, the 5-second global cooldown means those requests could take up to two and a half minutes to complete. This delay cannot be avoided by world creators, since the restriction applies globally and affects all content equally. To resolve this, I suggest keeping the 5-second restriction but applying it only per domain. If requests are sent to different domains, there should be no need to throttle them, since doing so would not increase the risk of data exfiltration. This change would maintain the intended security benefits while greatly improving usability and load performance. I would greatly appreciate your consideration of this improvement.

I can see the number of friends in an instance but not who's there exactly. (Other methods to check on that require extra steps and/or change of the view - like Wing->Friends->Filter->Location or Social->Friend Locations)

GitLab Pages is the same as GitHub pages, except you can keep a pages site's source private without paying. On GitHub, you can only have a GitHub Pages site and keep the source repo private if you pay for pro. On GitLab, you can have a private repo while keeping the pages site associated with it public Same as GitHub, GitLab pages do not support any server side code, and only host static files. This means it is not possible to get any identifying information from it.

Had 2 options when selecting to vote kick. Reason 1 - Nuisance Reason 2 - AFK Nuisance reason will be a bad strike on safety system. AFK reason will not effect the status of the player. Simply allows to kick someone who has either gone extended AFK or Sleep.

iOS devices are very capable, and the current 100 MB download size doesn't make sense for the capabilities of the platform. It should be at least 150 MB.

One of the problems in VRChat right now is how hard it is to get in touch with your friends when you’re not in the same world. As a VR social platform, it needs more ways to communicate seamlessly inside the game. Right now, due to the lack of a messaging system, people use invites as a workaround, which is very inconvenient. Users who play from a desktop can switch into Discord, but for VR users (especially standalone quest users), this is generally a poor experience, which is dragging them out of immersion. It would be way more convenient if there were an in-game direct chat feature that would be cross-platform between pc, PCVR, Quest, mobile, and on the website. Given the example of the popular direct messaging apps, you don't need to have your users' data, messages, etc., stored on your servers. It can be stored client-side on the user's devices. (Examples: WhatsApp, Viber) Why is this important? First of all, this is both convenient and immersive for players. This is useful when your friends are in private instances. This will help people stay in touch on the platform(especially with web integration). This would be a good way for people to communicate when they don't want to share their other socials due to privacy concerns. Idea for how the messaging system will operate: VRChat doesn’t need voice calls or video chats. Simple, reliable text messaging that works between worlds. There can be a tab in the main menu with existing chats or a user selection where you can start a new chat. In my opinion, we can limit chat to friends only to eliminate spam. (Or make it customisable as Friends/Friends+/Everyone) You can also use users' custom emojis/stickers in this chat system, which will make chats even more fun and interactive. Also, this is a great feature to be able to have Group chat (as in vrchat groups), chat with the group admin, or group chat as a separate feature to add your friends in there. This feature is crucial and expected for social platforms and will be a GREAT addition to VRChat.

I and I'm sure many other people use VRCFaceTracking to power their face tracking. When using Selfie Expression, these two systems combine and end up morphing the face tracking in undesirable ways. For example, with my Lasyusha edit, when smiling, there ends up being a gap between my teeth when both are enabled. Left is with selfie expression enabled, right is disabled. It would still be nice to use Selfie Expression to move your upper body + arms + hands, but without the added face tracking it provides. A toggle to turn off the face tracking that comes with Selfie Expression would solve this issue. Please, and thank you. 🙏