Open Beta

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)

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.

Lately, I've been noticing a delay between when a Warp Effect plays and when the remote user disappears. Usually the two events are synchronized within about half a second, but I've been seeing occasions where a remote user's warp effect plays, and then they disappear about 1–1.5 seconds later. I'm currently unsure if there's a difference between warp effects that play when travelling versus when the VRChat client is closed, but I did notice the issue with one user when their client unexpectedly closed.

The text for the <- Back button is missing from avatar lists in the AVM, and is incorrectly displaying the name of the avatar list.

Open VRChat Open Menu with Avatars wing panel open Filter is set to Show 'Favs 1', Sort By 'Recently Used' Change 'Show' to 'Recently Used' Close Menu, restart VRChat Open Menu again Filter has reverted to Show 'Favs 1' again.

This requests for the ability to make a public TweenEase variable to plug into VRCTween nodes. UdonGraph cannot make a variable of VRCTweenEase to expose as a inspector value. Having this would be useful for reusing a program and testing different ease types quickly. UdonSharp is able to do this already.

Using the new raycast component, set the Collision Mode to anything involving players. (Modes tested: 'Hit Players', 'Hit Worlds and Players', 'Hit Custom Layers - Everything', 'Hit Custom Layers - Player, LocalPlayer') Attempt to view the collision in-game. When attempting to collide with another player, the collision is only visible to the player the raycast is colliding with; no one else. All test were on Build 1818 on PC. Video of the issue: https://www.youtube.com/watch?v=KHjRiAfAuHc In the video, the Collision Mode was set to 'Hit Custom Layers - Everything'

I've recently uploaded a sticker and cannot see it placed while on open beta. I have removed and re-uploaded the sticker multiple times. Switching to live allows me to see the sticker. Live: https://youtu.be/UuNs0ka0V7Q Beta: https://youtu.be/GkoTIZyW-oM Sticker is attached and was drawn by Joakorex for the funnies.

Description: I am very excited about the addition of VRCTween in the new SDK update. However, I have noticed an issue: when trying to tween large integers using VRCTween.TweenInt , the values get rounded up or down to specific numbers, leading to inaccurate results. using System; using UdonSharp; using UnityEngine; using VRC.SDK3.Components; public class VRCTweenTest : UdonSharpBehaviour { [NonSerialized] public int _tweenedInt; public void PrintCurrentValue() { Debug.Log(_tweenedInt); } void Start() { VRCTween.TweenInt( 1, 15, 2, this, nameof(_tweenedInt), nameof(PrintCurrentValue), VRCTweenEase.Linear ).SetDelay(1); VRCTween.TweenInt( 100000001, 100000015, 2, this, nameof(_tweenedInt), nameof(PrintCurrentValue), VRCTweenEase.Linear ).SetDelay(4); VRCTween.TweenInt( 2000000001, 2000000015, 2, this, nameof(_tweenedInt), nameof(PrintCurrentValue), VRCTweenEase.Linear ).SetDelay(7); } } Expected Behavior: The script should output all intermediate integer values smoothly: * 1 through 15 * 100000001 through 100000015 * 2000000001 through 2000000015 Actual Behavior: When running the script, the console outputs the following: * The first tween correctly prints 1 through 15 . * The second tween only prints 100000000 , 100000008 , and 100000016 . * The third tween only prints 2000000000 . Cause Analysis: I suspect this happens because VRCTween.TweenInt is internally utilizing DOVirtual.Float or otherwise casting the values to float during interpolation. Since a 32-bit float has a 24-bit significand, it cannot precisely represent all 32-bit integer values (precision loss occurs for integers larger than 2^24, which is 16,777,216). Thank you for looking into this!

Open the full menu Go to VRC+ tab Select Overview Switch quickly: Overview --> Leaderboard --> Overview Switch to leaderboard again (Nothing will happen) After step 4 the UI is probably put in the leaderboard state while showing overview