SDK Bug & Feature Requests

Problem Opening VRCSDK Builder page or changing the selected avatar will revert pose (transform) to rest pose defined in the 'Avatar' asset of the root Animator component. Cause of the problem In the OnGUIAvatarCheck method of the VRCSdkControlPanelAvatarBuilder class, it will call Animator.Rebind method to check the situations you call "nested armature". However, Animator.Rebind function will write the default pose defined in the 'Avatar' asset so it will revert any pose changes made in the editor. This is annoying since this will disturb creating animation clips and testing them in the editor. Solution One solution is to use Animator.Rebind(bool writeDefaultPose) private method and pass false to writeDefaultPose parameter, instead of passing true to it, which is the default value. This method is not available as public API but it will keep available until Unity 6000.2.0b4 (the latest available C# reference version . Another solution is to collect the current pose before calling Animator.Rebind and restore it after the call but this takes more code.

After a successful build, adding a network-related component to a GameObject with another network-related component causes an error relating to network IDs when the next build. Repro steps Create a new scene and put the VRCSceneDescriptor Add a network-related component to a GameObject Build the world Add another network-related component to the GameObject in step 2 Build the world You'll see the dialog (see the 1st attached image) Preprocess Callback Failed The VRCSDK build was aborted because the IVRCSDKPreprocessSceneCallback 'AssignSceneNetworkIDs' reported a failure. The network-related components here are VRCObjectSync , VRCPickup , UdonBehavior etc. That needs a network ID. VRCPlayerObject of the ongoing Persistence open beta also causes this issue. Note 1 The console shows the errors after closing the dialog (2nd attached image) Failed to assign network IDs, 1 errors encountered! Try using the Network ID Utility to resolve them. Note 2 If you press the "Build & Reload" button on step 5, you'll see the "Build Succeeded!" message in the SDK tab. But the build has not succeeded. NetworkIDs in VRCSceneDescriptor has not been appropriately updated (in particular, the Serialized Type Names of the GameObject). This (showing false "succeeded") seems to be another defect. Note 3 If you press "Build and Upload", you'll see the "This file was already uploaded" error popup. And the SDK also shows "This file was already uploaded" as details. This message is incorrect since the building file is incomplete. This also seems to be another defect. Version Worlds 3.7.2

The last SDK version I was able to successfully test was 3.8.1. This one allows for lighting to bake successfully On latest SDK 3.8.2 (And 3.8.2-beta.1): 'Generate Lighting' with unity built in lighting menu -> Background task stuck "Waiting for shaders to compile" - The time to completion continuously rises and never moves past 5% I am using an AMD rx 5700xt, screenshot attached is from another user who has the same issue and is using NVidia.

Toon Standard (Outline) does not apply Scale Transform to the Outline Width Mask, I use this on my Avatar to reduce VRAM on an atlas'd texture and UV.

Issue A bug with the current SDK requires the GameObject which a VRC_Station is attached to, to be enabled on upload. As a result, stations are on by default if safety settings block user animations. This is BAD. Stations may be added by creators for special purposes, such as carrying other players, or animation-tied amusement. Having these on by default can create experiences where a player with stations receives UNWANTED interactions if animations are disabled. This is especially true for Quest/Mobile/Android, where animations are more likely to be disabled by default. This therefore poses a safety risk that is not mitigable by avatar creators. Potential Resolutions Add a "Disabled by Default" dropdown to the script with the options "Never"; "Always", which would disable the GameObject the VRC_Station is attached to on enable; and "Collider Only", which would disable only the provided box collider itself on enable. This would account of different creator preferences. — Whilst VRChat officially recommends disabling the collider only, the behavior of disabling the GameObject itself may be highly desirable in some case, and some popular station add-ons use this behavior. Giving developers the ability to choose between implementations allows for greater flexibility, and prevents breaking existing animations. Allow uploading with script disabled. — If the script can be disabled on upload, it won't matter anymore, as the station will be disabled when the avatar loads, making it opt-in via animation, not opt-out.

In the public world 'a-lin', photos taken using the player camera fail to display vegetation, trees, terrain, and similar environmental objects. These photos ignore objects rendered via VRCGraphics.DrawMeshInstanced. DrawMeshInstanced objects are ​​completely absent​​ from camera photos despite being visible during gameplay and in SteamVR (F12) screenshots. This bug ​​severely disrupts​​ the player photography experience. How can this be fixed?

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

My seat trigger colliders are inside of a physical hull collider. The hull is on a custom layer called PhysicCollider and I use the "Interact Passthrough" setting to make it transparent to interaction. Live I can interact with the seats. That was uploaded with SDK 3.5.0. But when I upload my world with SDK 3.6.0, the interaction isn't possible anymore. I have to crawl to reach the seat collider inside. I guess, that feature broke with the layer changes in SDK 3.6.0. The first two images shows live SDK 3.5.0 vs my testworld SDK 3.6.0.

The VPM UdonSharp Package is provided without any License information

It seems like the "Item" layer doesn't actually replace the "reserved3" layer: the "reserved3" layer actually moves on a different layer. This happens to brand new projects and to projects that got updated from 3.8.1 to 3.8.2 First image : My layers before the SDK update Second image : My layers after the SDK update, notice that layer 23 is now "reserved3"