SDK Bug & Feature Requests

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

Unity supports the four most common module file formats on audio sources, namely Impulse Tracker (.it), Scream Tracker (.s3m), Extended Module File Format (.xm), and the original Module File Format (.mod). VRChat supports only the Extended Module File Format (.xm) in worlds only, anything else fails security checks or removes the tracker module audio because the formats may have security ramifications. A note about Tracker Module audio file (in)compatibility in avatars/worlds was promised to be looked at by euan in August 2025, but hasn't been implemented yet in Creator documentation a year later yet. I thought of a request to extended this documentation to the SDK builder alerts. I also tested in VRChat SDK - Avatars 3.10.5 and found that an audio source with a .xm file on an avatar does not show any build alerts in the SDK builder that this is unsupported and that the tracker module audio will be removed. Can a builder alert be added to the VRChat SDK when an unsupported module tracker file extension is found on an audio source, please? Related: https://feedback.vrchat.com/bug-reports/p/tracker-modules-audio-files-mod-it-xm-s3m-triggers-security-checks

There's many usecases for this; One obvious one would be using a synced variable to drive the speed (multiplier) of an animation. This could be done by copying said synced variable through the parameter driver, setting a local variable, and multiplying it with the desired amount. Add can only do so much

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).

With the SDK 3.10.2 update, the Avatar Expressions Menu editor received the following UX change: When targeting a Boolean parameter, the Value attribute is now hidden and is always treated as enabled, since that's the only valid option for a Boolean (true when activated, false when deactivated). While I understand the reasoning behind this change, it removed a useful workflow that was previously possible. Before this update, it was possible to create two menu controls targeting the same Boolean parameter: one with Value = True and another with Value = False. This allowed both controls to toggle the same parameter while only the control matching the current state would appear visually active. For example: Badge toggle (Value = True) Nameplate toggle (Value = False) When the Boolean is true, only the Badge toggle appears active. When it's false, only the Nameplate toggle appears active. This made it possible to represent two mutually exclusive states using a single Boolean while providing clear visual feedback in the Expressions Menu. Since the Value field is now hidden and always forced to true, this behavior is no longer possible. I'd like to see the Value option restored for Boolean parameters, even if it's tucked behind an advanced setting or warning. While the current behavior is simpler for most users, the previous implementation enabled legitimate use cases that are no longer possible.

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.

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に変更してミュートすることしか出来ません。 音量のブーストが可能であれば、その逆も可能だと思われるので、もしよろしければ機能を追加して頂けますと幸いです。 いつも運営ありがとうございます。よろしくお願い致します。

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