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

Please allow users to select another parameter as the value to set for a given parameter. This will simplify the process of designing systems that synchronize multiple parameter values. For example, this feature would enable variable assignment—such as setting ParamB as the value for ParamA—to make ParamA and ParamB have the same value.

Having to work on 2 different animator layers is becoming a bit of a chore, for example, if i want to switch the material of an avatar, i need to have 2 different animations, 1 for PC and another for Mobile (Assuming PC uses a non VRC Shader which is 99% likely) Multiply this for the number of materials, make this more annoying by having atlases and different skin mesh renderers, and it becomes spaghetti very quickly The “isMobile” parameter would be a boolean that is False when the avatar loads the PC Version, and is True when it loads a mobile version. Allows people to work on a single animator layer for both platforms

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

The contact system is limited to 60 updates per second, in scenarios over 60 fps, the contacts will maintain information from a prior frame, for systems expecting an update every frame, this leads to incorrect assumptions, which can break logic in unexpected ways. This can be prevented by adding a parameter to indicate whether contacts have updated this frame (i.e. ContactUpdate ), this would allow us to short-circuit every contact-based transition to only evaluate when we know contacts have up-to-date values, avoiding these problems. An inverse of the parameter (i.e. ContactUpdateSkipped) can currently be implemented by using a Proximity contact and setting it's value to non-0 every frame, on frames that the contact receives an update, the value will be overridden back to 0, adding the parameter as a boolean in the controller means that contacts have updated when the parameter is false (can undo the inverse behavior by adding an overlapping sender, but that adds another runtime component).

Add a animation parameter that allows users to adjust their floor position. This feature would be useful for offsetting toggles related to various footwear options, such as heels or bare feet, and could also enable more creative solutions. Without this parameter, users may experience issues like clipping or floating above the floor when toggling these parts. I first considered this functionality a long time ago, wondering, "Why isn't this possible?" Recently, I was reminded of it when a creator on Booth aimed to develop content for a broader audience, including not only full-body tracking (FBT) users but also half-body and desktop users. They expressed frustration at having to resort to less-than-ideal solutions due to the lack of this functionality. I'm open to discussing alternative solutions beyond just an animation parameter. Perhaps a component similar to a VRC parameter driver, or another approach, might be more suitable for this purpose. I’m interested in exploring different options that could effectively address the need for adjusting floor positions in various contexts. I’m not sure if any Asians will read this, but regardless, I’ll post the first paragraph in each language. ChatGPT 사용자가 바닥 위치를 조정할 수 있는 파라미터를 추가하세요. 이 기능은 힐이나 맨발 같은 다양한 신발 옵션과 관련된 토글을 조정하는 데 유용하며, 더 창의적인 해결책을 제공할 수도 있습니다. 이 파라미터가 없으면, 사용자는 이러한 부품을 토글할 때 클리핑이나 바닥 위에 떠 있는 문제를 겪을 수 있습니다. ユーザーが床の位置を調整できるパラメータを追加してください。この機能は、ヒールや裸足などのさまざまな靴のオプションに関連するトグルを補正するのに役立ち、より創造的な解決策も可能にします。このパラメータがないと、ユーザーはこれらのパーツをトグルする際にクリッピングや床から浮く問題が発生する可能性があります。 添加一个允许用户调整地板位置的参数。这个功能对于调整与各种鞋类选项（如高跟鞋或赤脚）相关的切换非常有用，并且还可以启用更具创意的解决方案。如果没有这个参数，用户在切换这些部件时可能会遇到如穿模或浮在地面上等问题。

Similar to other VRCTween extension methods, this would fill in the GameObject value of the VRCTween.DelayedSetActive(GameObject target, ...) value. Used like such: gameObject.DelayedSetActive(false, 3.0f);

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

Similar to the VRChat Keyboard, it would show both lasers from each hand on any VRC Ui Shapes with a setting enabled on it. This would be handy for any in-world ui that may require both hand lasers to be readily visible like a control panel or custom world keyboard.

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.