World/Udon Bugs & Feature Requests

Post about current World or Udon bugs feature requests. One item per post!
Non-constructive and off-topic posts will be moved or deleted.
[JP/EN] Request to feature our world in "Recommended for Beginners" / 「初めてにおすすめ!」へのワールド掲載のお願い
[English] Hello VRChat Team, I am writing to request the inclusion of our world in the Japanese "Recommended for Beginners" (初めてにおすすめ!) section. This world is a portal hub themed around traveling the world. It features a social lounge where players can chat with others, as well as a search system to find worlds categorized by country or specific situations. To ensure accessibility for a wide range of players, the world supports 4 languages (Japanese, English, Chinese, and Korean) and is cross-platform compatible with PC, Android, and iOS. If our world is selected, we plan to continue updating it regularly so that more users can enjoy virtual traveling in VR. Thank you very much for your time and consideration. World Details: Simple World Travel Portal Hub https://vrchat.com/home/world/wrld_2bfa68dc-dcc0-402a-9372-4cade61560b5 [日本語] VRChat運営チーム様 日本語版の「初めてにおすすめ!」に下記ワールドを掲載していただければと思い、ご連絡いたしました。 今回掲載をお願いしたいワールドは、世界旅行をテーマにしたポータルHUBとなっております。人と交流できるラウンジのほか、国ごとやシチュエーションに合わせてワールドを検索できる機能を備えています。 また、より多くのユーザーに楽しんでいただけるよう、日本語・英語・中国語・韓国語の4言語に対応しており、PC・Android・iOSの3プラットフォームすべてに対応しております。 ぜひ掲載いただけましたら、VRで旅行を楽しめるワールドとして今後も継続的にアップデートを行っていく予定ですので、ご検討いただけますと幸いです。 ワールド詳細: Simple World Travel Portal Hub https://vrchat.com/home/world/wrld_2bfa68dc-dcc0-402a-9372-4cade61560b5
0
·
Feature Requests
[JP/EN] Group instance joining for placed World Portals / ワールドポータル進入時の複数人同一インスタンス遷移機能
[English] Hello VRChat Team, I would like to request a feature that allows multiple players who enter a placed World Portal within a short timeframe to be sent to the same instance together. Currently, when a creator places a World Portal in a world and multiple players enter it simultaneously, each player is sent to a separate, random instance. In my Portal Hub world, I have placed multiple portals so players can easily explore different worlds. However, because players get split up upon entering, they are forced to manually open an instance beforehand every time they want to travel together, which creates a very inconvenient user experience. To make world-hopping with friends much smoother, I would greatly appreciate it if you could implement a system where players entering a placed portal around the same time are automatically grouped into the same instance. Thank you very much for your time and consideration. [日本語] VRChat運営チーム様 ワールド内に設置されたワールドポータルに複数人が短時間のうちに入った際、全員が同じインスタンスへ遷移できる機能の実装をリクエストいたします。 現在、ワールド内に設置したポータルへ複数人で同時に入ると、それぞれが別々のインスタンスへ飛ばされてしまいます。 私は現在ポータルHUBのワールドを制作しており、ユーザーが気軽に様々なワールドへ移動できるよう複数のポータルを設置しています。しかし、現状の仕様ではポータルに入った瞬間にフレンドと離れ離れになってしまうため、一緒に移動するには毎回手動でインスタンスを立て直す手間が発生し、ユーザー体験を大きく損ねています。 ポータルHUBなどからフレンドとそのままスムーズに遊びに行けるよう、一定時間内に同じポータルへ入ったプレイヤーが同一のインスタンスへ遷移する仕様へと改善していただけますと幸いです。 お忙しいところ恐縮ですが、ご検討のほどよろしくお願いいたします。
0
·
Feature Requests
Expose Graphics.SetRandomWriteTarget
Note: This request is an excerpt of this document which contains some additional context and suggestions for a implementation. With the introduction of VRCGraphics.Blit and asynchronous readback feature, we are closer than ever before to having compute-shader-like capabilities in VRChat. However, we are still missing a critical component: Random writes! Random writes are the ability to write to any location in a block of memory, represented as an unordered access view (UAV) - in our case, these UAVs concretely are just RenderTextures. Random writes are hugely useful for making compute-shader-like code performant, and for many of the things that people tend to use real compute shaders for, they are downright required. This is due in part to the fact that they enable the use of atomic operations (example), which open up the doors to a bunch of algorithms that are infeasible or very tricky to implement without. We could get very close to approximating compute shaders today with the addition of one single piece of API: Graphics.SetRandomWriteTarget . With this API, you can do random writes in fragment shaders, which brings them much closer to compute shaders (see the initial link for example code). Here are some examples of possible use cases: Persistent data storage in a shader without jank. No need for GrabPass abuse, Custom Render Textures, or Camera loops. Just bind a RenderTexture and you are good to go. Communication between shaders without jank. Simply bind your render texture, and any fragment shader can now access it with both read and write access. Custom realtime GI systems. I implemented a system that places and integrates light probes dynamically based on camera depth using this piece of API. Better fluid simulations. In general, pretty much any kind of shader-based simulation can benefit from this. Either by being made simpler to implement, faster, or becoming feasible in the first place. Potentially speedup for AudioLink's DFT algorithm? Fast reduce-style operations such as summing or maxing over a domain. GPU based sorting.
2
·
Feature Requests
Load More
→