World/Udon Bugs & Feature Requests

After the 2024.4.1 patch, I've noticed that the VRCPlayerApi variable inside Udon scripts will automatically replace itself with another player (or the instance owner/local player) if the player it was set to leaves the world. I am unsure if this was an intended change, but I am fairly certain that worlds scripting that relied on knowing if the variable is equals to the player that left now no longer behave as intended after this patch since it always switches to players that are still present.

Additional Array methods were added in https://docs.vrchat.com/v2021.4.1/docs/vrchat-202114#changes-improvements-and-fixes-1 with the accompanying canny post marked as complete https://feedback.vrchat.com/vrchat-udon-closed-alpha-feedback/p/add-more-array-methods-to-all-array-types but Array.Sort was mysteriously left out. This would be EXTREMELY useful for quickly making a deterministic list of players using GetPlayers()'s VRCPlayerApi array by playerId (and then sorting the VRCPlayerApis by playerID with Array.Sort(keys, items)). Currently in Udon that array is out of order for different clients, and individual playerIds represent their join order, rather than an autofilled sequence from players leaving and joining. It would also be useful for sorting VRCPlayerApis by a world's game score for a scoreboard. Array.Sort is extremely useful because, even though we don't have access to custom data structures or IComparable implementations in Udon, we can still sort things using associated arrays of intrinsic data types. And before you do the same thing that you did with the previous post, please just whitelist everything you can. Not just Array methods. Stringbuilders. Native Unity components like LODGroups. Although a rumor, I heard that ReflectionProbe endpoints weren't included for a YEAR after Udon's release because there was a blacklist for anything with 'reflection' in the name. Please consider going back through the whitelist and enabled anything and everything possible.

Physics simulations in VRChat are limited in realism because creators can't modify most of the variables in physics settings. For example, I'm working on a mini golf map and my golf balls stick to walls at low speeds rather than bouncing off realistically. I've gotten the editor's simulation to look nearly 1:1 with real golf balls by changing the "Bounce Threshold" in the PhysicsManager to 0. However, these changes do not carry over when I'm testing the map in VRChat. I can maybe understand restricting the solver iterations to prevent lag, but even then it should be up to creators to optimize their worlds. If the physics settings can be made changeable it would be very appreciated!

Using ClientSim, when a player joins, OnAvatarEyeHeightChanged is invoked with the prevEyeHeightAsMeters parameter passed as the literal integer 0, causing a type mismatch since it is expected to be a float. Repro: Create an Udon Program that uses the OnAvatarEyeHeightChanged event. Use the prevEyeHeightAsMeters for any type-specific externs, like addition. Test the world using ClientSim and you will get an exception. This bug was introduced in 3.6.0 and I have gone ahead and created a simple PR addressing it: https://github.com/vrchat-community/ClientSim/pull/119

Right now OnInputMethodChanged only get called if well input method changed, but I think I would make sense to have it called once to let the world figure out the user input and switch any logic without having to manually do it with GetLastUsedInputMethod()

In a recent SDK update, the Scene Descriptor doesn't show the Network IDs list, making it quite difficult to manually tweak Network IDs. I believe this is unintentional as the Editor component for the Scene Descriptor still has code to build the inspector for the Network ID list. The problem is with the line propNetworkIDs = serializedObject.FindProperty(nameof(VRCSceneDescriptor.NetworkIDCollection)); because "NetworkIDCollection" is not the name of the serialized property for network IDs. The correct name is "NetworkIDs".

On the Quest platform, when clicking on a pre-filled VRCUrlInputField, the focus is set to the beginning of the URL. This behavior is inconsistent with the PC/PCVR version, where the focus is correctly set to the end of the string, allowing normal and more convenient typing behavior. Video of the issue: https://youtu.be/gSU8lyfVZMc Might be related to: https://feedback.vrchat.com/open-beta/p/1400-wrong-cursor-position-when-clicking-on-pre-filled-url-input-field

This would easily allow nicer looking dropdowns

TMPro.TextMeshPro and TMPro.TextMeshProUGUI both inherit from TMPRro.TMP_Text. Therefore, we can access both as common interface such as TMP_Text.text by using the TMPro.TMP_Text.

If an interactive UI canvas sets its Graphics Raycaster component's "Blocking Objects" to "ThreeD" or "All", users won't be able to interact with it. This is because of a change in Unity 2022.3.22f1.