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

Following up https://feedback.vrchat.com/sdk-bug-reports/p/freeze-to-world-on-constraints-will-always-bake-offsets-if-there-are-0-sources A parent constraint with "Freeze to world" enabled before the object containing it is on is turned off will not properly snap back when "Freeze to world" is disabled if it happens on the same frame that the object is turned back on, if "Freeze to world" is re-enabled a frame later. Repro: Two objects, X (i.e. the avatar's armature) and Y (droppable) Parent constraint on object Y has a single source to X, zeroed. A toggle is linked to two animations: * False = Object Y is turned off (2 keyframes, both are the same, animation duration is 0.017). * True = Object Y is turned on, "Freeze to world" is disabled on keyframe 0, enabled on keyframe 1 (animation duration is also 0.017) Assumption would be that because the parent constraint "freeze to world" is turned off, it would make object Y snap back to object X. This works in the editor , but does NOT work in game. A further observation was then made - adding a 3rd keyframe ("keyframe 2", animation duration 0.033) that is a copy of "keyframe 1" (object on, freeze on) made it work in game, but removing "keyframe 1" (so the animation duration is simply longer) did not solve it, it appears that for whatever reason the duplicated keyframe is necessary for the expected unfreeze/freeze snap to work in game.

what is fame

Make a stereo audio file with very obvious differences between the Left and Right channel Assign it to an AudioSource component Enter play mode (with ClientSim) You hear both channels Add a VRCSpatialAudioSource component to the same gameobject Enter play mode You hear only the left channel Do a Build & Test In the actual client, you hear both channels

Performing multi-platform builds with overrides set have several issues: They can fail if an avatar that's part of the overrides is disabled - block the build or re-enable targets temporarily. They can fail if the override does not pass upload limits for the target platforms (i.e. custom shaders on android) - the stats breakdown should display breakdown per platform (separate tabs/foldout), taking avatar override into account. There's apparently a way to cause an infinite upload loop (not sure how, but this was reported by someone who set the overrides incorrectly) Platform swaps occasionally fail (mostly commonly when it's the first time on a project)

On most PC shaders, when Audio Link is set to control the emission, the emission is set to off when Audio Link is not in a world. for Toon Standard, the emission is set to full when audio link is not in a world. The emission should be overridden to off when audio link is not present in a world and audio link has been set to use the emission mask. This could also be an option in the shader, like a check box, so as to not break current logic that already gets around this issue.

In the attached video, I try to to set Primary Style as Object and Secondary Style as Furry for a new Avatar Dynamics Robot Avatar PC sample avatar upload in a new project with nothing but SDK - Avatars 3.10.5, but after the upload finishes both styles end up being Not Specified instead of the chosen information. Editing primary and secondary styles from the SDK works for existing uploads, but for new uploads. Affected SDK versions tested: 3.9.0 (minimum for new uploads), 3.10.3, 3.10.4, 3.10.5 (latest). Affects all avatars, and all combinations of primary/secondary styles (e.g., Human/Anime, Anime/Human, Object/Furry). I've run into this issue for some six months now, every week. Behavior in SDK 3.9.0 today is slightly different, but still buggy: In the SDK it shows the Primary Style is set to the chosen Secondary Style, and the Secondary Style as Not Specified, but after checking the VRChat Home website or tabbing in/out of Builder tab it goes back to Not Specified like in SDK 3.10.5.

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

VRChat SDK Version: 3.5.2 Description of the bug: The VRAM that all of the various textures and materials use does not coincide with the VRAM Usage shown in the VRChat SDK (This has been checked with Thry's Avatar VRAM Calculator) Steps to reproduce: Create an avatar Bind a Material with various textures Observe results with Thry's Avatar VRAM Calculator and VRChat SDK I've attached a screenshot showing the difference between the calculated VRAM and the VRAM shown by the SDK

It has been this way for a long time, that PlayerLocal colliders are effectively turned off when the player is in a station. World builders could normally work around this, but with avatar chairs, now this behavior breaks many worlds where a player riding another player will have issues with not locally enabling intended effects because they arrived in the area in a station. (This behavior is unexpected and that's why I'm putting this in bugs, not feature requests.)