Open Beta

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.

Due to the fact that companions have colliders on Item/UI/Pickup this can cause Raycasts and some other physics calls to unexpectedly fail due to it returning null or be blocked by them because they are on the same layers as items (Item, UI layers). Companions also appear on the Pickup layer during repositioning which can also cause the same issues. The layers of the colliders can be viewed in this world (place the item inside the blue box in front of spawn and the ui canvas will display a list of colliders) https://vrchat.com/home/world/wrld_a5d2da68-573f-46b6-956a-235222a0d31b/info

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.

Currently you are able to spawn multiple "Companion" type Items however in 1863 you are now limited to one Companion once all the previous "Companion" type Items get converted into proper "Companions".

The current logo has no spacing between VR and Chat

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.

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!

Only tested in desktop spawn cube from action menu click reposition whilst repositioning ui is up, if you open action menu and click "remove" you get stuck

Steps to reproduce: Open instance on the Main Menu Click "Send Instance Announcement" and add a message World page UI overlaps "Send Instance Announcement" UI This only happens on the first click of the "Send Instance Announcement" on the MM, if cancelled and pressed again it does not happen.

Multiple strings now use the improper name of "Props" The new collapsible section on the Inventory Items tab Instance settings tooltip when turning Items on/off Instance setting notification popup when turning Items on/off Placing items etc