World/Udon Bugs & Feature Requests

I noticed this bug when I tried to set a value that could not be represented as a float. Shader.SetGlobalInt() is cast to float internally, so Shader.SetGlobalInteger() needs to be used.

This can be an issue when using stations for vehicles with trigger zones. For example, i have a setup where i want audio to enable and disable based on the player location. This works fine with players, but to make it work with those vehicles i would need a second check for the vehicle.

When a networked custom event is sent with over 1kb of data to NetworkEventTarget.Self, the next networked custom event sent from that client does not send. Instead, the 1kb+ event is replayed, but to the new event target. For example if I send a 1.5kb event MyEvent on BehaviourA to NetworkEventTarget.Self, then send an event OtherEvent on BehaviourB to NetworkEventTarget.Owner (other player), instead, the owner of BehaviourB will receive MyEvent on BehaviourA with 1.5kb of data. Here is an example world where this can be seen: https://vrchat.com/home/world/wrld_451e102f-0087-4e14-a1c0-362a26a2594b

When a player leaves the instance or enters a station, OnPlayerTriggerExit does not fire for any trigger colliders that they were in. This will break any system trying to count the players in an area. It is known that Unity will not fire OnTriggerExit when either deleting the collider or disabling colliders, but you must move the collider out of the area. Example world: wrld_d3e81903-54d6-4562-a968-2223c368906e World has a blue trigger area and will display when a player enters or exits. There is also a chair in the area. Test case 1: Have two or more players in the room. Have one player enter the area Have that player leave the instance. Note that a player exit trigger message is never displayed. Expected result would be that OnPlayerTriggerExit fires, which would then display the message Test case 2: Have one player enter the blue area. Have that player sit in the chair. Notice that player exit area does not fire. Have the player exit the chair. Notice that player enter does fire and the count is now off by one. Expected result would be that on entering a station (which disables the player collider), Player trigger exit fires.

I'm currently making some custom mirrors with my own cameras using the eye position and rotation retrieved from the VRCCameraSettings. The mirrors work, but if I have the update loop in PostLateUpdate, the images are clearly lagging behind when I move my head in VR (on desktop it works fine). Using the rotation from the tracking data of the head does seem to have the same issue. I worked around it by updating the transform in OnPreCull instead, but isn't the intention of PostLateUpdate to have all tracking data up to date for the current frame?

This is problematic in a few situations, and this other issue makes it even worse: https://vrchat.canny.io/vrchat-udon-closed-alpha-bugs/p/playerapi-humanbodybones-do-not-have-a-consistent-rotation-every-avatar-is-diffe 1) It is, as far as I can tell, completely impossible to get the correct rotation of a remote user's head without syncing an object's position/rotation. 2) generic avatars will give you positions at 0,0,0 3) desktop users tracking data locally will give you hand positions out in front of the camera, in the position that the object would be if they were holding a pickup. This is a useful emulation and doesn't function for remote clients.

My world has a layered camera setup and requires for the reference (main) camera of the world to be set to render with Clear Flags set to Depth only and only render from players eyes up to 1000 meters in order to maximize performance. Secondary camera of the world is set to render only a low quality copy of the terrain and surrounding mountains in the horizon from 1000 meters all the way up to 4000 meters before the main camera of the world renders the scene. Despite the player's POV looking perfectly normal on desktop and in VR, the in-game camera, steadycam and personal mirror all break because they inherit all applicable properties of the reference camera and don't properly clear the render, resulting in unacceptable ghosting in the sky. I'm asking for the VRCSDK to include an option to set the camera properties of VRChat's in-game user cameras independently from the reference camera, e.g. fields for Clear Flags, Near Clip, Far Clip on the VRCSceneDescriptor so they can still keep functioning without the world author having to provide a completely custom camera solution from the ground up in order to mitigate this issue. If exposing the properties in the SDK is too big of an ask, at least ensure that the in-game cameras do not have their Clear Flags set to Depth Only or Don't Clear. Thank you. P.S. This issue could also be fixed by allowing the world to set the Clear Flags of the player's main camera during runtime with Udon, related post: https://feedback.vrchat.com/udon/p/give-us-an-interface-to-the-main-camera-via-the-vrcgraphics-class

This used to be not an issue before, but now if you have a Non-trigger Collider (set to a Unity or Custom layer, excluding the Walkthrough layer since it already does what it is supposed to do but that's beside the point) that is set to exclude the Player/PlayerLocal layer, the player will still "collide" with it and be able to "walk" on top of the collider's surface while slowly descending as if they were using a flying avatar. They'll still be able to go through the collider, but the problem here is that they can stand on top of the collider when they shouldn't be.

The method GetPlayersWithTag returns a List<> Please make it function the same way as GetPlayers() does

VRCSDK3-WORLD-2021.03.09.13.57_Public Unity 2018.4.20f1 When many Midi Events are received, references outside the buffer range will occur. Log IndexOutOfRangeException: Index was outside the bounds of the array. VRC.SDKBase.Midi.VRCPortMidiInput.Update () (at Assets/VRCSDK/SDK3/Runtime/Midi/VRCPortMidi.cs:71) VRC.SDK3.Midi.VRCMidiHandler.Update () (at <5d3e9f7f72234587a2c25e98f82b4f27>:0)