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.

Physbones is really cool. In particular it has a performant set of tools that allow for avatar-avatar interaction. Please port the Physbones code so we can use it in Worlds too! It would make making many Worlds things far easier, like buttons and levers.

Suggestion: Option 1: In class VRCPlayerApi, create a bool method SetVisibility(bool) which defaults to true, for toggling the overall visibility of a particular player, which includes their avatar and nameplate and any chat box they may create. Option 2: Alternatively, create multiple toggles to control each element individually, such as SetAvatarVisibility() SetNamePlateVisibility() SetChatBoxVisibility() SetStickerVisibility() SetItemVisibility() etc. In my opinion the second option offer better granularity of control and allows a more creative use. Reason 1: Currently if we need to hide a remote player without changing their actual position, we need to exploit a desync station to achieve this effect. Surely that is not the intended use of a station and is in fact a bug. We should be allowed to modify a remote player's visibility with Udon, directly, without exploiting a bug. Meanwhile, world creators can transition to this method, thus allowing the station bug be fixed without affecting worlds that utilize it. Arguably this feature is a prerequisite of eventually fixing the station. Reason 2: We can already control the audibility of a player, via SetVoiceDistanceFar etc. Combining SetVisibility(false) with SetVoiceDistanceFar(0f) and SetAvatarAudioFarRadius(0f) you can make someone completely disappear. Or, alternatively, make someone invisible but can still be heard.

There are many camera settings that would be really nice to have access to after runtime. An interface could be provided for this via some proxy in the VRCGraphics class. (and maybe one for the hand camera as well!) Ideally this proxy would contain everything the normal Camera class has that doesn't pose a security risk. Some examples of very handy use cases for this: Change farclip dynamically to minimize perf overhead from unnecessarily drawing distant avatars/objects Safe access to culling masks for user-created layers to make a lot of common visibility tricks much easier Set depth texture to be generated without needing a shadow-casting dir light Get FOV to use for unique world mechanics Access to a lot of useful camera matrices like cameraToWorldMatrix, worldToCameraMatrix, projectionMatrix, etc... Access to stereo separation for more advanced world features ...and more I'm probably not thinking of!

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

VRC supports various languages itself, however world are only limited to one language for the world details. VRC should provide a way for world creators to have different world name/description depending to the user language settings which would provide a better accessibility and tell the player that the world support their language

The current SDK is able to track players' heads and hands, but not their legs. It'd be nice if they could, allowing for proper fullbody IK in worlds.

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.

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?

Currently, when a user enters the interaction range an interactive game object in a world, VRChat displays a blue halo around it. Udon can control this highlight with InputManager.EnableObjectHighlight , though it's unreliable and undocumented. It turns the highlight on and off, but the game object loses or regains its highlight if the user enters the interaction range. Worlds can work around this by calling EnableObjectHighlight every Update. Udon should be able to control an object's highlight state to a greater extent.