World/Udon Bugs & Feature Requests

It'd be helpful for world creators to know how many people are entering their world as well as how often users are coming back.

In addition to the inventory post that already exist, I want to be able to give players items to consume/spawn only usable in my world. For example, if I make a Minecraft-esque world every player would find a starter kit in their inventory with a shovel, axe, torch and pickaxe. When leaving the world the items would disappear. Or a flare gun players can use to find each other on super large worlds. Assuming persistence exists, a tick box would exist on the imaginary item component to either make it disappear on switching world or you keep it forever (Or until consumed?)

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.

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.

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!

If I want to pass a parameter to custom event receiver, even now, I could it by using public program variable and executing SetProgramVariable before SendCustomEvent. Comparing that, for example, OnCollisionEnter event uses implicitly defined variable "onCollisionEnterOther". I think it will be useful and user friendly if parameter passing can be written directly in sender side SendCustomEvent node and receiver side CustomEvent node as a kind of syntax sugar.

World developers seeking to create complex worlds that handle arrays could greatly improve their development process if they were able to use Generic Collections, especially List<T>. It would be even more helpful if we could also use C# LINQ operations. There are many common situations where Collections and LINQ combined can reduce large quantities of code to simple one-line or one-operation solutions.

At present, PhysBone is not supported in the World SDK, so Dynamic Bone must be used to implement physics-based animations. However, the version of Dynamic Bone used in VRChat is already quite outdated—likely version 1.2.1, whereas the latest available version is 1.3.4. The contents of the Dynamic Bone component included in the component whitelist have also changed, with new parameters such as "Roots" and "Blend Weight" being added. Naturally, these parameters that do not exist in the older version do not function in VRChat. On the Asset Store, only the latest version of Dynamic Bone can be downloaded. The discrepancy between the available version and the version used in VRChat could lead to confusion when setting up worlds, especially since the version of Dynamic Bone used in VRChat is not documented anywhere. To test with the same version as VRChat, we now have no choice but to transfer an older version of Dynamic Bone that was downloaded when that version was still available. If the World SDK plans to continue using Dynamic Bone in the future, I strongly urge that the version of Dynamic Bone used in VRChat be kept up to date. --- 現在のVRChatランタイムで使用されているDynamic Boneのバージョンは既にダウンロード不可能です。 現在、WorldSDKではPhysBoneがサポートされていないので、揺れものの実装にはDynamicBoneを使用する必要があります。しかし、VRChatのランタイムで使用されているDynamicBoneは既にかなり古く、おそらく1.2.1だと思われますが現在の最新バージョンは1.3.4です。コンポーネントホワイトリストに含まれている、DynamicBoneコンポーネントの内容も変化しており、例えばRootsというパラメーターやBlend Weightというパラメーターが新たに追加されています。これらの古いバージョンにないパラメーターは当然VRChat上では動作しません。 アセットストアではDynamic Boneは最新バージョンしかダウンロードすることができません。利用可能なバージョンと動作バージョンの違いはワールドをセットアップする上で混乱のもとになるでしょう。VRChat上でのDynamicBoneのバージョンがどこにも明記されていないからなおさらです。私たちが現状でVRChatと同じバージョンのDynamicBoneで検証するには、そのバージョンがリリースされていた当時にダウンロードしていた古いバージョンのDynamic Boneを移植する以外に方法がなくなりました。 今後もワールドSDKではDynamicBoneを使い続ける予定であるのであれば、せめてVRChatのDynamicBoneのバージョンを最新に保っていただきたいです。

It was announced on yesterday's developer update that Udon 2 had been scrapped for "Soba". Based on the information we have been given, they're making the equivalent to Udon 1.1. In the words of the VRChat team, specifically Fax: Soba will have comparable or worse performance than current UdonSharp at launch with "promised" improvements in the future. But as we know, VRChat is unreliable with promises, so I'm hesitant to believe that. Soba will lack generics support at launch (no List<T> or Dictionary<T>, among others) Soba will not have everything promised in Udon 2 This is extremely dissapointing for me, and many other VRChat creators. Udon 2 was supposed to be the superfast feature-rich improvement over current Udon To see that they have opted to make a custom VM which, based on the facts we have right now, will not achieve Udon 2's speeds or feature parity is a disappointment to the community and a testament to how easier > better in VRChat's eyes. The reasons for this change are also abysmal. They said that Udon 2 "would have distracted us from adding feature requests that the community had been asking for". This shows how deaf VRChat is around community feedback, since Udon 2 was one of the most exciting features for me and many other creators, plus, this wasn't an issue when you were waving your dick about making stickers, boops and other features nobody asked for. Alongside this, based on VRChat's technical reasoning, it appears that WebAssembly was scrapped because the new engineer(s) working on Soba didn't bother to debug Udon 2, it appears some benchmarks were done, issues were found, and they didn't bother to try and debug it, or just made up some excuse, instead opting for yet another sloppy custom VM. I apologise for my irritated language, but it is growing rather agitating that VRChat cannot competently deliver on a highly anticipated feature without taking years and having a 50/50 chance of scrapping it. Udon 2 was the better choice objectively, so I implore you to rethink this decision and bring back WebAssembly based Udon 2.

Now that web connectivity will likely require some form of consent from the user when using Udon, I think it's a reasonable request to ask for an actual unique user ID that we can use to identify users. This could be used to do things like enable a debug console in the world, or when web connectivity is back, save progress or settings in a world. Right now people are using display names as "unique" identifiers which isn't good and already has issues since it's a display name. One issue is https://vrchat.canny.io/vrchat-udon-closed-alpha-bugs/p/onplayerjoined-doesnt-get-full-displayname-for-steam-users Another issue is that "special" characters like "." get replaced in the display name with lookalikes which breaks string comparisons. Relying on display name to "uniquely" identify people will become more prevalent as time goes on and people make commonly used systems that depend on them. You should expose this sooner rather than later to avoid this issue. The potential for abuse is obviously possible, but there's no reason to kneecap the systems and introduce potential issues by leaving only display names visible. Right now I can reasonably target people with just their display names, it's just possible that there will be some more people with the same name that get targeted. Worlds abusing names to harass people is something that should be reported on a world basis.