SDK Bug & Feature Requests

Right now, rim lighting applies everywhere based on view angle, which makes light bleed into weird spots on Quest avatars like inside hair crevices, clothing folds, and mouth cavities. A simple grayscale mask slot (or channel selector) to multiply against the rim intensity would fix the glow artifacts and make Quest fallbacks look way cleaner and closer to PC toon setups (like Poiyomi/lilToon).

Please add a warning with Auto Fix button if Post-process Layer component attached to Reference camera has Anti-aliasing set to anything except None. Right now SDK only warns if TAA is selected but not FXAA or SMAA. Any of these methods produce blurry visuals in worlds and making distant text unreadable while in VR and SDK should discourage people from using them (or maybe even block uploads). They also does not play well with built-in MSAA that provides much higher quality image.

In the new SDK 3.7.6, it's now possible to build a world on Linux, but it is not possible to launch a local test with proton. Pls add proton support, similarly to: https://github.com/BefuddledLabs/LinuxVRChatSDKPatch

As a content creator, selecting colors for customizing avatars is a common use of the radial slider on avatars. However radials are not the best use of a color selector as they have no real preview and often need multiple radials to control one color. It would be nice if we could have an actual color picker widget type for expression menus.

Hello! First, thank you for all your hard work developing so many fun and useful features. My feedback today is a feature request regarding the SetVoiceGain() function for controlling player voice in Udon. As it stands, the function only accepts values in the 0 to 24 range, meaning it can only be used to boost a player's voice, making it louder. https://creators.vrchat.com/worlds/udon/players/player-audio/ I'm trying to create a specific area in a world where players inside the area would hear the voices of players outside more quietly, as if they were in a soundproof room. However, with the current implementation, my only option is to mute them completely by setting their Voice Far property to 0; I can't simply reduce their volume. It seems that if it's possible to boost the gain, it should also be technically possible to do the reverse (attenuation). I would be very grateful if you could consider adding support for negative values to this function. Thank you for your continued hard work on the platform. Best regards. ==== Original Text ==== こんにちは。毎度楽しい機能の開発ありがとうございます。 本題ですが、Udonではプレイヤーの音声を操作するための関数がいくつか用意されているかと思いますが、その中のSetVoiceGain()についての要望です。 現在は0~24の範囲の値のみ受け付けるようになっていて、プレイヤーの声が大きく聞こえるようにのみ出来る仕様になっているかと思われます。 https://creators.vrchat.com/worlds/udon/players/player-audio/ 私はワールド内に特定のエリアを作成し、そのエリア内にいるとエリア外のプレイヤーの声が小さく聞こえる部屋を作ろうと考えていますが、今のSetVoiceGain()だとプレイヤーボイスのFarを0に変更してミュートすることしか出来ません。 音量のブーストが可能であれば、その逆も可能だと思われるので、もしよろしければ機能を追加して頂けますと幸いです。 いつも運営ありがとうございます。よろしくお願い致します。

A VRC_Pickup.Pickup() method would be nice. We have VRC_Pickup.Drop() which forces a pickup to be dropped. Pickup() would be a counterpart to this, forcing a grab. There's cool stuff you could do with this, I'm imagining better two-handed manipulation of pickups, and surely there is a lot of other inventory-related stuff you could do. Currently a common design for player inventory items is to spawn/teleport them to be floating in front of your face. Even if spawned at waist level or something, these items get in the way of clicking on other stuff, especially in desktop or mobile. It would be nice if udon could just put it in your hand, already grabbed, especially for non-vr players. How I imagine it could work: Call VRC_PIckup.Pickup(pickuphand) to basically emulate grabbing the item with that hand. If the hand's already grabbing something, this does nothing. Even though the grab input isn't actually in the down position, their hand is holding the pickup, until the grab input is actually pressed (which is then ignored because you're already grabbing) and then released (dropping it like normal). It might seem a little weird to have an object suddenly held in your hand without the input pressed, but still I think it's really worth having.

Currently, only shader texture properties explicitly labelled '_MatCap' (case-sensitive) will automatically fall back. Removing this case-sensitivity will allow far more avatars to fall back automatically, notably those using Poiyomi shaders. For the record we are going to get this fixed for Poiyomi shaders at some point going forward, but there's nothing we can do about avatars already out in the wild.

The laser pointer that is used in world UI or to point at an interact/pickup currently does not have a native way of checking where that is nor what VR hand is showing the laser. This requests for a function or event to get the hand and Ray (to be used with a Physics Raycast) that references where the laser pointer is and a way to request for the Ray in the off-hand. This would be extremely helpful in creating pointer based controls (like click drag) for 2D color pickers, showing both lasers for an in-world keyboard, custom interactions, drawing on a 2D canvas, etc. I made an Udon prefab that's able to estimate these pointers but it would be nice if this was a native SDK feature: https://bobystarvrc.booth.pm/items/5007241

Please provide fallback shaders with VRCSDK and API to get them from material. There are multiple possible use cases like: To create avatar with exactly same look with and without Fallback - Currently, since we don't have fallback shaders, we cannot create avatar consistently looks same with and without fallback. To create Editor Extensions that shows the fallback-ed version of the avatar. - There are some editors exists but their implementation might can be different. - There is no documentation that explains the exact algorithm for parsing VRCFallback tag so we don't know which shader will be applied for wired VRCFallbackTag like ToonCutoutUnlit . To retrieve list of properties used in each fallback shader. - I want to get (current) list of properties supported in each fallback shader to remove unused properties from the material. - There are list of properties copied to fallback material on creator docs, but some fallback shader may not use some properties on the list (like Toon does not use most properties but _MainTex ).

Post Processing has a big performance penalty when it present in the world and even disabling all Post-Process Volume components does not restore performance fully. To gain maximum performance boost it's nessesarry do disable Post-Process Layer component attached to player camera. Please add Udon hook that will allow world creators to toggle Post-Process Layer component so people can completely disable Post Processing in the worlds with in-world toggle buttons to gain as maximum performance as possible. Added performance test results captured with SteamVR Advanced Frame Timings window. World without Post-Process Layer. Button in world does nothing https://vrchat.com/home/world/wrld_89d9698e-a8ab-4112-bf38-dfdb04fd9e87/info World with Post-Process Layer and Post-Process Volume. Button toggles Post-Process Volume object. https://vrchat.com/home/world/wrld_9c0d4344-0fc4-40f0-af3a-dadc81974fe7/info