Open Beta

The “Teleport To” feature in Udon Graph is not working properly. The same program worked fine when I wrote it in Udon Sharp. I verified this in the world I created for this test. https://vrchat.com/home/world/wrld_e5a6efb2-24f4-4084-8c8d-9804f6cba181 Both the Udon Sharp version and the Udon Graph version are set up in the world, and each cube is programmed so that interacting with it triggers a sound effect and teleports the player.

Not sure on the reproduction steps, but I play with nameplates off and when I open my quick menu I see nameplates. I noticed one night a lot of nameplates in an instance were extremely huge, seemingly not rotating when I move around. Affected friends and non-friends. When I tried rejoining the same instance, even more people became affected by this behavior. No clue what causes it.

In a recent Open Beta it was announced that the VRC highlight now highlights Skinned mesh renderers. This functionality should be opt-in through the Pickup Component or auto assigned based on the renderer it is added to. Currently this changes how old pickups show and now add an overlay over invisible parts which may go against how the creator intended. If the option is to be set as the default, it would be nice to include an array within the pickup component where we can 'hide' renderers within the pickup child to be ignored by the hover highlight.

If you travel to the world "Sylvarium" on the Unity 6 build, very shortly after initialising, you'll start to experience catastrophic frame loss, making your experience basically a slide show. https://vrchat.com/home/world/wrld_204f0c4a-e0d2-46c9-a09f-4b19d7b5b628

The video output from AVPro players on both PC and Quest has historically needed to go through a gamma to linear conversion to look correct. This is something that has been handled at the shader level in video player prefabs - USharpVideo does an explicit pow(color, 2.2f) , ProTV uses GammaToLinearSpace(), etc. Since the open beta update that includes the new AVPro version, this seems to no longer be the case on Quest. Videos played through AVPro players on Quest will now look incorrect with that conversion applied. You can verify this by going to Video Player Showroom and playing a familiar video in the ProTV player. With default settings, the video will appear very dark with a crushed black level. I will reiterate that this issue is not specific to the ProTV player prefab but instead to AVPro-based players generally. It is certainly possible for world/prefab developers to detect Quest and skip performing this color space conversion. However, in its current state, this causes incorrect playback in basically every existing VRChat world using an AVPro-based player. All of these worlds would need to be updated to ensure correct playback if this current open beta gets shipped to live. Some player prefabs such as ProTV include a user-facing option to skip this conversion, however I would consider it a regression if suddenly every Quest user needs to enable this option. It also seems presently impossible to come up with a method by which users can have correct playback on both the current live version as well as the current open beta. I basically have to choose which one I want to break.

The "World Currently Unavailable" thumbnails when worlds have been deleted are red. Previous behaviour was it being grey.

Issue: With the new global collider option users can now mark a PhysBone collider as global to allow it to collide with other peoples PhysBones. This however has one problem, you can't have a global collider that can collide with other peoples PhysBones, while not having it collide with all of your PhysBones. For example Furry Avatars often have PhyBones in their toes, but maybe also want to be able to have a global collider on their foot. Currently those two would interfere with each other and there is no way to prevent that without making the collider local or disabling "Self" on the Phys Bone collision. (Doing so would also prevent hands etc from colliding.) Suggestion: Essentially, allow us to somehow have a global PhysBone collider that we can locally ignore. There are 2 ways I could see this being solved: Have a "Ignore Colliders" list on each PhysBone. If you have a global collider that you don't want it to collide with you can just drag it in there. Similar to PhysBones themself, have "Collide Self" and "Collide Others" toggles on PhysBone colliders when set to global, allowing you to decide if it should only be global for you, others or both. Current Workarounds: Currently you can just have "Allow Self" disabled on the PhysBone and live with you not being able to touch or grab them. If you want to add that back you could add your own finger colliders, etc. just for that PhysBone. Attachments: Here is a screenshot of the "Allow Self" and "Allow Others" settings on PhysBones that could also be implemented for colliders.

When moving the mouse between UI Themes and Backgrounds, the fading animation causes extreme flickering between the two hovered items. This can be dangerous for individuals affected with photosensitivity. Edit: This happens with any Background, not just the new Gradient one shown in the video.

Issue: On PhysBones you can set if it should collide with your own colliders, the colliders from others or both. The newly added global colliders don't respect that however. They will collide with PhysBones that have "Allow Self" disabled. Expected Behaviour: A manually added global PhysBone collider should be treated similarly to your default colliders. Disabling "Allow Self" on a PhysBone should also disable a local global PhysBone collider from colliding with it. Attachments: Here you can see the global collider still colliding with my toes even though I have "Allow Self" disabled. (The last screenshot is in Play Mode)

Block a User. View their Mutual Friends. Get blocked. View their Mutual Friends. This seems like a pretty big privacy oversight, as I doubt anyone would want blocked users looking up mutual friends to harass or co-opt into being intermediates. For context: Not even Discord allows this with it's mutual friends feature.