SDK Bug & Feature Requests

I tried to upload world on Linux . But, it's failing with the message "Last built VRChat scene could not be found. Please Test/Compile Full Scene (slow)". "Last Build" and "Build & Publish for Windows" button does not work with this message, but "Build & Test" can work and I can local test it.

TextMeshPro has missing exposure: ForceMeshUpdate , UpdateGeomerty , transform . They are exposed in TextMeshProUGUI. (note: renderer on 'TextMeshProUGUI' is not implemented on original)

There are 2 checkboxes in the "Lower Body" section of the VRC Avatar Descriptor and they say "Use Auto-Footsteps for 3 and 4 point tracking" and "Force Locomotion animations for 6 point tracking". But now, VRChat has some other tracking point states like 11 point and 5 point. So I think it should be change the description to correspond to all supports tracking points.

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.

Create an expression menu Create sub menu with toggle for parameter which doesn't exist create menu item in main expression menu and link submenu change menu item type from submenu to toggle Current behaviour: VRChat SDK shows "VRCExpressionMenu uses a parameter that is not defined. Parameter: <your parameter name>" and blocks upload Expected behaviour: No warning/error in SDK window SDK: 3.7.1

If the Aim Vector and Up Vector are modified from their default values, the results may differ between Unity Aim Constraint and VRC Aim Constraint. Note: This occurs when the World Up Type is set to None, but similar issues may arise with other types as well. This issue also occurs with automatic conversion and affects avatars that use Unity constraints uploaded in the past.

I've never seen the Shader variants take this long before. I find this very odd. Is this intentional for Avatars, or could it be a weird side-effect of adding Bakery support? If so, should the Standard Lite shader be stripped of unused features at Upload? For reference, only 1 Material is being used on the Avatar I published. Settings used are attached as well for reference.

Just clicking on an avatar in the scene causes the scene to be marked as modified. In most cases this is just annoying as it prevents you from telling if the scene is saved or not. However it causes a big issue if you are like me and use prefabs to save variants; because the prefab attempts to auto save changes and thus will get stuck in an infinite flickery loop. I have found that collapsing the descriptor allows it behave normally. Perhaps caused by one of the gizmos or something? This didn't used to always happen, but has seemingly become increasingly common with each update.

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

Version 3.7.1 Reproduction steps 1) Create this hierarchy: └ GO1 └ GO2 (this GameObject has the VRCObjectSync component, and is disabled) 2) "Build & Test" to generate new IDs. 3) Remove the VRCObjectSync component from GO2 4) Add the VRCObjectSync component on the GO1 GameObject 5) The hierarchy should now look like this : └ GO1 (this GameObject has the VRCObjectSync component) └ GO2 (This GameObject is still disabled) 6) "Build & Test" again => An error appears in the logs, Failed to assign network IDs, 1 errors encountered! Regenerating all network IDs fixes that issue.