World/Udon Bugs & Feature Requests

Ever since I went ahead to update my world with the latest update in mind (SDK 3.9.1-beta.1], anyone trying to join it will receive an "Unusual Client Behavior" and be kicked out of the world immediately. I tried to delete any changes done in the world in the hope to pinpoint the problem but the problem still occurred and even after downgrading to SDK 3.9.0 it still gives the error. If it helps to solve the issue, I noticed that messing with my PlayerObject pool (despite the fact I have not touched it once for the update) and removing then adding back some object prevented the error from showing up. Alas when I decided to arrange it after I noticed some script were broken with the newer PlayerObject setup in the world that fixed the error, the error showed up again, even when I used the backup scene I saved that worked before, that one ALSO DIDN'T WORK. This is the world currently being affected by this issue : https://vrchat.com/home/world/wrld_37abea33-f34c-4706-8e6b-2f69e414fc5d/info I have tried everything to see if the problem came from my world but the problem feels way too random for it to be the case.

What I'm going to describe is a very niche bug, that won't bother a lot of people, but it's been preventing me from porting some cool worlds like "Thad Recursive Room" to Quest, because it relies on some render tricks with multiple cameras. If you have a camera without a render target, it will render on screen. And if you set the "depth" parameter greater than 0, it will render after the main camera, effectivly acting like an overlay camera. So far, everything works. But doing that with more than 1 camera does not work. So if you use a second camera with an even higher depth value, it's content won't show up on the screen as long as the first overlay camera is still on (That is, if the content of the second overlay camera is actually performing a z test). But it gets stranger from here: if I open and close the menu a few times and also click on some of the menu tabs like the world menu. Every now and then it causes a glitch that will make the content of the second overlay camera sort of appear from there on out. What I can see then, is that when I move my head, it moves away an invisible shape that was blocking the content of the second overlay camera. And that shape fits perfectly the object it is supposed to render. It is as if the z values of the second overlay camera are already written to the depth buffer before the actual rendering of the second overlay camera begins and then the z test fails against its own values. But after the menu glitch, the occluding depth image seems to be frozen in place and I can partly move it out of the way by changing my view. Also: one time I tried something similar with cameras rendering before the main camera (depth parameter is set to a negative value, and main camera is set to clear nothing). Results were similar, and after I managed to get something visible with the menu glitch, it appeared as if the cameras that render earlier than the main camera were very pixelated, which was also surprising. I've been also experimenting with manually calling render() on multiple cameras that are supposed to render on screen during several render related events (for example in OnPostRender of the first overlay camera), but no luck getting their content to show in any way.

Issue: Currently it's not possible to react to a players voice at all. We don't know when someone is talking or how loud they are for example. This limits us from making games where someone needs to be quiet to hide from an enemy for example. For security reasons it makes sense that we can't just listen to a player voice, which is why I think only giving limited access to it would be fine. Suggestion: Add an isTalking bool to the VRC Player API which is true when voice is detected and false when not. Add a loudness float to the VRC Player API which is a value between 0 and 1 depending on how loud a player is. (Basically how the current Voice parameter works on Avatars) Add a viseme integer to the VRC Player API which would indicate what viseme is currently used. (Basically how the current Viseme parameter works on Avatars) These would allow world creators to integrate player voice into game play while also not just directly giving them access to player voices for security.

It would be useful if we could get Terrain methods in Udon. Specifically, methods and properties in https://docs.unity3d.com/ScriptReference/TerrainData.html and https://docs.unity3d.com/ScriptReference/DetailPrototype.html .

Allow world creators the ability to moderate their OWN worlds and issue their OWN bans. I'm tired of seeing crashers and exploiters in my worlds and kicking them is nothing. I want the ability to ban certain individuals from my worlds. There is absolutely no harm in doing this. Who is it going to hurt? The exploiters and cheaters. What if world creators abuse it and ban people from THEIR OWN worlds? Well it's their fault their world fails to gather a population. What else will this do? Allow world creators to suit the needs of their wanted audience. it will also help take the stress off of the actually game moderators. Thank you, Lucifer MStar - Creator of 30+ worlds including church of marriages. P.S. Communicate more with your community on what you are doing about these crashers and exploiters and maybe the heat and stress will die down. Honestly this is the most annoying thing communication.

ClientSim gathers the "PlayerPersistenceObjects" in ClientSimPlayer.cs before ClientSim removes objects that are tagged EditorOnly. This breaks the ClientSim initialization process, resulting in "_stackedCameraReady" never being set to true. This results in the menu's "ToggleMenu" function failing to close the menu, causing the user being unable to test their scene under this scenario.

Fairly simple request. Half of what makes Contacts what they are is currently missing. We can only contact from Avatar to World to trigger something in the World. What we need is the ability to send parameters from World to Avatar to trigger effects on the Avatar. An example of this would be a weather system. You stand inside a contact for rain and it will send a inRain parameter to the Avatar which then can implement something in their animator layer to do something with this, such as enabling shader effects to look rained upon or wet. This could be used for many effects, sandy in the desert, muddy in swamp, wet in rain/water, damaged/bloody in games with health and so on. Allowing communication from the World to an Avatar would open up endlessly more ways to interact with the World in a variety of ways.

Get what instance type you are in. Public, Friends, Friends+, Invite+, Invite Single node can return string Multiple nodes for each type can return bool

Please let us access the position of the name plate, to let us add world-specific UI icons to it. Currently, we can estimate the position of the name plate from the player's position. @bobystar discovered that: > it may have something to do with the avatar's main bounding box (all bone sizes are 1m): I've attached bobystar's screenshot. So a workaround might be to access the player's avatar bounding box - if we have access to that 🤔

Today, the most popular use case of the IVRCImageDownload is to share some picture with friends in VRChat. However, there is one big annoying behavior in IVRCImageDownload for this use case. That's 2048x2048 texture size limit. Therefore, I hope VRChat to have the feature that automatically scale the texture size down to 2048x2048. As described before, it's common to use IVRCImageDownload for sharing pictures with friends. There are several assets specifically designed for this use case such as Image Pad and ImageTablet . However, the 2048x2048 size limit is an annoying for this use case because today picture is likely to exceed this limit. For example, my iPhone 12 mini with default settings will take picture with 4032x3024 pixels and other modern smartphones also take high resolution image by default. In VRChat, I feel it’s common to choose take pictures in QHD, 4K, or 8K but none fits 2048x2048 limit. (FHD and HD fits 2048x2048 though we want to take high-quality pictures.) The texture downloaded with IVRCImageDownload become uncompressed RG, RGB or RGBA texture on the VRAM so It take huge VRAM. Therefore, I think it's reasonable to limit texture size on the VRAM. However, I think it's possible to resize texture down to 2048 off the main thread before loading to to the VRAM. That’s why I request VRChat to have the feature that automatically scale the texture size down to 2048x2048. 日本語要約 IVRCImageDownloadという Image Pad や ImageTablet のような画像を共有するためのアセットで使われている機能に対する要望です。 前述のタブレットではVRChatの制限により2048x2048より大きい画像を指定した場合にはエラーになりますが、エラーにする代わりに 2048x2048 以下に自動的にリサイズするオプションを追加してほしいという要求になります。 (技術的理由により2048x2048より大きい画像をそのまま表示するのは厳しいです) このオプションがあれば、Discordなどに上げた画像を共有するときにエラーが出て使えないという面倒事を減らせるようになります。