SDK Bug & Feature Requests

When opening the VRChat SDK panel and navigating to the Builder tab, the VRC Per Platform Override component is automatically added to the root object of the avatar, even though I haven't done anything. Is this intended behavior? I have previously uploaded avatars using multi-platform settings (Android, iOS), but not with this avatar. So I suspect this automatic addition might be unintended.

The PhysBones document ( https://creators.vrchat.com/avatars/avatar-dynamics/physbones/ ) doesn't contain the following information that VRChat 2025.1.3 and SDK 3.8.0 introduced. Execute in deterministic order Maximum dependency depth is 8 ignoreOtherPhysBones option The attached image is a capture of https://creators.vrchat.com/releases/release-3-8-0/

This new version seems really emjoy hanging in Scheduler.Tick. Maybe I got too many avatars?

VRCSDK Version: 3.8.0 If, after build hooks run, the maximum physbone dependency depth is exceeded, the SDK fails the build with a generic "Avatar validation failed" with no further details. It's not currently possible for third-party tools to expose this error, because the detailed error list is passed only to the private VRCSdkControlPanelAvatarBuilder.HandleBuildError (from CheckAvatarForValidationIssues), which proceeds to discard the detailed list of errors. Please provide either a built-in way to display errors that are created as part of postprocessing, or at least an API by which third-party tools can surface these without needing to hook your private APIs with Harmony.

After updating to the latest sdk 3.8.0 I've been getting a new error on two physbone scripts "Cyclic dependency found for component VRCPhysbone" It looks like the error is because the two physbones can interact with each other via coliders placed on each bone. Physbone A can collide with Phsybone B Physbone B can collide with Phsybone A As far as I know the components behave as expected so I am not sure why there is an error warning against it nor does the error provide too much info on how to keep the functionality and remove the error.

Within a render callback such as OnWillRenderObject, it's useful to be able to check which camera is rendering. Unity has "Camera.current" for this, but it's not exposed to Udon. The new camera API is awesome, but without a property like that, I still can't make my UdonPortals prefab render correctly in the hand-held camera because there's no way to tell which camera is currently triggering OnWillRenderObject. I'd like a property to tell which camera is responsible for the render. A really simple implementation would be a new read-only property like: VRCCameraSettings.CurrentCameraType: An enum consisting of the values "ScreenCamera" or "PhotoCamera". However, I think this API could be extended further to be even more useful. In particular, if a Camera that was created by the world (and so is already accessible to Udon) is rendering, it would be great to be able to access the actual Camera object! Just like Unity's "Camera.current", but only limited to world-created Cameras. An API might look like this: VRCCameraSettings.CurrentCameraType: Enum consisting of the values "ScreenCamera", "PhotoCamera", "WorldCamera", or "Other". "WorldCamera" would be any camera created by the current world, i.e. a Camera that's accessible to Udon. "Other" would be anything else that isn't (yet!) accessible to Udon, e.g. avatar cameras or the screenshot camera. VRCCameraSettings.CurrentCamera: A reference to the current Camera object, just like Unity's Camera.current, except it's only set when CurrentCameraType is "WorldCamera". Otherwise, it's null.

Any script on a pickup that attempts to address ObjectSync will crash with the following error; An exception occurred during EXTERN to 'VRCSDK3ComponentsVRCObjectSync.__SetKinematic__SystemBoolean__SystemVoid'. Parameter Addresses: 0x00000030, 0x0000002B Object reference not set to an instance of an object If you want to replicate; Make a pickup. Give it a script that will do something to ObjectSync on pickupusedown (Eg; Set Kinematic). In ClientSim, it will crash becxause it can't find the Objectsync/rigidbody. In-game, however, it will work fine.

Summary: VRChat's own VPM packages are getting distributed with missing licence information. A change request for the documentation about VPM License files. According to UPM docs ( https://docs.unity3d.com/Manual/upm-manifestPkg.html ) Licence: > Identifier for an OSS license using the SPDX identifier format, or a string such as “Refer to LICENSE.md file”. > Note: If you omit this property in your package manifest, your package must contain a LICENSE.md file. LicenceUrl: > Custom location for this package’s license information, specified as a URL. For example: > "licensesUrl": " https://example.com/licensing.html " > Note: If the Package Manager can’t reach the URL location (for example, if there is a network issue), it does the following: > - If the package is installed, it opens a file browser displaying the LICENSE.md file in the package cache. > - If the package isn’t installed, the Package Manager displays a warning that offline license information isn’t available. According to VPM docs ( https://vcc.docs.vrchat.com/vpm/packages/ ) > We also highly recommend listing the license of your package in the package manifest. Unity requires this field if you do not have LICENSE file in your project, but we recommend specifying it even if you do have a LICENSE file. This field might be displayed in the VCC interface in the future. The license should use the SPDX format. None of the above is done by VRChat itself. Instead VRChat distributes a licence.txt file inside vpm packages with an URL to the license. Moving (or copying if there is a need for the LICENSE.txt) the licensesUrl from inside Licence.txt to the LicensesUrl key inside package.json seems to be the needed change. VPM (uses LICENSE) and UPM (uses LICENSE.md ) using different license filenames. Is this an oversight? Why did this got changed? Can we have some more clearification about it?

The latest VRChat SDK does not show an error when attempting to upload an avatar with more than 8 Physbone components to Android, and allows you to build, while stripping all Physbone components on the avatar. The SDK should be providing an error message and disallowing building and uploading, but no longer does in this case.

Unity Version: 2022.3.22f1 SDK Version: Base 3.8.0, Worlds 3.8.0 Following the documentation on the VRChat website , I have disabled Auto compile on modify , yet any time I save an UdonSharp script, Unity will refresh and recompile. I'd like to disable auto compile and just have the option to compile manually, but the options in the Project Settings menu seem to have no effect.