Open Beta

Attempting to join a preloaded world still occasionally sends me back to my homeworld! The world join will work on a 2nd attempt most of the time now but it still has happened to me a few times since updating. Log attached as requested.

When you attempt to preload a world, it'll preload as normal, but when it reaches the end of preloading, the banner never shows the preload as complete.

Please provide changelog with technical words when it's hard to describe with normal words. In SDK 3.8.2-beta.1, there's one fix described as "Added a validation error that prevents a humanoid avatar from being uploaded if it has a nested armature." and Nested Armature is described as "the root of the armature is not a direct child of the GameObject containing the avatar's animator." However, this is misrepresented or partially incorrect depending on the interpretation of "armature". There's no "armature" in the unity world (as far as I know and searched) but a few similar or related concepts. When I see the description, I came up with several hierarchy structures like: 1) Having independent FBX model with bone skinning inside an avatar. (If made with blender, typically contains GameObject named "Armature") 2) Having same FBX model as avatar root with removing no objects from root model hierarchy. (If the avatar is made with blender, typically contains GameObject named "Armature") 3) Moving the bone hierarchy (if the avatar is made with blender, typically contains GameObject named "Armature") to the child of new GameObject in the avatar. And I tested them and only last one is detected as "Nested Armature" This should means the error is shown if the avatar's root's Animator component's avatarRoot is not same as avatar's root. However, the description of the changelog, it's hard to know 1 and 2 are not the case. Therefore, could you add the technical description when it's hard to describe without them in addition to current description, for advanced avatar developers.

Open an instance of https://vrchat.com/home/world/wrld_778e1f0e-7209-406a-ab45-e97cdd5aa267/info Look at the spot in the screenshot. There is a mystery collider, but only on open beta. If you click this, you sit sideways, and cannot leave the station without respawning. Is this related to the REFERENCE CUBE? I'm not sure. This occurs even if I start vrchat without touching the inventory menu, so... if so that's going to be a bit disruptive to testing open beta. Output log: https://www.dropbox.com/scl/fi/81kbq65109buvuo53mpzf/output_log_2025-06-12_19-30-28.zip?rlkey=yvdv03vm5g6ccj53bek00c6wy&st=5bmm7nze&dl=0

Udons that are inactive at the time of world loading will not be synchronized when they become active I first looked at the state immediately after Join. build the world by deactivating the Udon with one int type Udonsync variable the owner (playerID = 1) activates the synchronization object and counts the variable +1 nothing happens under non-owner player2 (playerID = 2) player2 activates the synchronization object and then the owner sets the count of the variable to 2. the value is synchronized for the first time to the synchronization object of player 2 and the count is set to 2. Then we examined the state of the object once it was activated. the synchronization object of player 2 is deactivated. the owner sets the variable count +1 twice. nothing happens under player 2. when player 2 activates the synchronization object, the synchronization events during the period of inactivity are executed consecutively and the count goes to 3 and then to 4. Finally, the state of the later-joiner is examined. In player 3's client, nothing happens immediately after Join because the Udon object is inactive. nothing happens when player 3 activates the object. when the owner sets the count of a variable to 5, the value of 5 is suddenly synced to player 3. If the Udon is active at the time of loading the world, the later-joiner will also be synchronized with the latest values immediately after the join. The owner does not need to do anything at this time. Translated with www.DeepL.com/Translator (free version) Test code: using System; using UdonSharp; using UnityEngine; using VRC.SDKBase; using VRC.Udon; using TMPro; using VRC.Udon.Common; public class LaterJoinerTest : UdonSharpBehaviour { [SerializeField] TextMeshProUGUI log; [UdonSynced, FieldChangeCallback(nameof(TestValue))] int _testValue = 0; public int TestValue { get => _testValue; set { log.text += DateTime.Now.ToLongTimeString() + " OnValueChanged: new value = " + value.ToString() + ", old value = " + _testValue.ToString() + "\n"; _testValue = value; } } void Start() { log.text += DateTime.Now.ToLongTimeString() + " Start: playerID = " + Networking.LocalPlayer.playerId.ToString() + " value = " + TestValue.ToString() + "\n"; } private void OnEnable() { log.text += DateTime.Now.ToLongTimeString() + " OnEnable: value = " + TestValue.ToString() + "\n"; } private void OnDisable() { log.text += DateTime.Now.ToLongTimeString() + " OnDisable: value = " + TestValue.ToString() + "\n"; } public override void OnPreSerialization() { log.text += DateTime.Now.ToLongTimeString() + " OnPreSerializaton: value = " + TestValue.ToString() + "\n"; } public override void OnPostSerialization(SerializationResult result) { log.text += DateTime.Now.ToLongTimeString() + " OnPostSerializaton: value = " + TestValue.ToString() + "\n"; } public override void OnDeserialization() { log.text += DateTime.Now.ToLongTimeString() + " OnDeserializaton: value = " + TestValue.ToString() + "\n"; } public override void OnOwnershipTransferred(VRCPlayerApi player) { log.text += DateTime.Now.ToLongTimeString() + " OnOwnershipTransferred: playerID = " + player.playerId.ToString() + " value = " + TestValue.ToString() + "\n"; } public override void OnPlayerJoined(VRCPlayerApi player) { log.text += DateTime.Now.ToLongTimeString() + " OnPlayerJoined: playerID = " + player.playerId.ToString() + " value = " + TestValue.ToString() + "\n"; } public override void Interact() { if (!Networking.IsOwner(this.gameObject)) { Networking.SetOwner(Networking.LocalPlayer, this.gameObject); } TestValue++; RequestSerialization(); log.text += DateTime.Now.ToLongTimeString() + " Interact & RequestSerialization: value = " + TestValue.ToString() + "\n"; } }

[Open Beta Users Unable to Enter Specific World] We have confirmed an issue where players using the Open Beta version are unable to enter certain worlds. The error message displayed is: “You are traveling too much. Please wait and try again later. (Code: 429)” Here is the world where the issue is wrong: https://vrchat.com/home/world/wrld_bf457400-7f1f-44c8-ad77-1c1b43cad331/info — — — [Confirmed a bug where people in the open beta version couldn't enter a specific world] We've confirmed a bug where open beta players weren't able to enter some worlds. The error statement is “The world is moving too fast. Press the time to try again (code 429)”. Here is the world where the problem is happening. https://vrchat.com/home/world/wrld_bf457400-7f1f-44c8-ad77-1c1b43cad331/info

3.7.7-beta.1 introduced new property, Force Kinematic On Remote on VRCObjectSync . But the release note doesn't mention this change. Note: The revised doc properly contains it ( https://vrc-beta-docs.netlify.app/worlds/components/vrc_objectsync/#properties ) It would be helpful if you describe why this property was added or when we should turn it on.

-World that has been uploaded to vrchat for a while (Sky high apartment) -On live everything works fine -In beta almost all the custom scripts break with the following error inside vrchat debuger: "[UdonBehaviour] An exception ocurred during Udon execution, this UdonBehaviour will be halted" -On unity's console while using this launch parameters on steam "-enable-udon-debug-logging" shows more than 230 errors, all of them include "Object reference not set to an instance of an object" -Checking the objects manually on unity shows that all references are properly set, scripts work both in live vrchat version and on unity editor using client sim so it looks like the beta is somehow missing all the references.

The report button is missing for stickers.

## Description If you go to a high ping instance you can place duplicated items if you are fast enough, because the item takes a bit to spawn. ## Reproduction Go to an instance with high ping (tested on 280 ping, EU->JP). Place item, quickly place another one before the first one spawns. Attached a video.