SDK Bug & Feature Requests

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.

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.

Many NullReferenceException happens during the import process. You will fail to do even a simple "loop back test". Repro steps Create a scene having a VRCSceneDescriptor and an UdonBehavior at the minimum. Open Network ID Import and Export Utility https://creators.vrchat.com/worlds/udon/networking/network-id-utility/#network-id-import-and-export-utility Press Regenerate Scene IDs and confirm the dialog Press Export and save it to a file Press Clear Scene IDs and confirm the dialog Press Import and select the file you have just saved. The utility shows the object(s). Press Accept All or Select Then, the Console shows NullReferenceException errors Environment Tested with SDK 3.7.0 Worlds. This seems to happen from 3.5.2 Log The head part of the exception: NullReferenceException: Object reference not set to an instance of an object VRCNetworkIDUtility.<DetectConflicts>g__DoTypesMatch|28_6 (VRCNetworkIDUtility+NetworkObjectRef scene, VRCNetworkIDUtility+NetworkObjectRef loaded) (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/VRCNetworkIDUtility.cs:550) VRCNetworkIDUtility.DetectConflicts (System.Collections.Generic.Dictionary`2[TKey,TValue] loadedRefs, System.Collections.Generic.List`1[T] conflictList) (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/VRCNetworkIDUtility.cs:520) VRCNetworkIDUtility.OnGUI () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/VRCNetworkIDUtility.cs:297) Note The NullReferenceException happens when accessing NetworkObjectRef.typeNames . Some implementation of INetworkIDContainer has the issue, maybe, UdonBehavior . INetworkIDContainer.NetworkIDCollection is typed List<NetworkIDPair> Some element of it has the null as NetworkIDPair.SerializedTypeNames

When testing udon networking with RequestSerialization, networking events such as OnPre/OnPost Serialization are never called. This makes patterns such as the below one difficult, which are useful in helping avoid bug-prone netcode. public override void OnPostSerialization(SerializationResult result) => _ApplyNetwork(); public override void OnDeserialization(DeserializationResult result) => _ApplyNetwork(); private void _ApplyNetwork() { // Perform tasks here } I will attach a shim I made that patches over this issue, though it doesn't correctly handle all cases that VRChat performs, and the OnDeserialization behavior here can actually clobber data - so an official implementation should probably either do nothing if not owned, or run OnPreSerialization() first in this case. It's a bit of a hack, but it helps with some testing. It also doesn't do anything for continuous sync, this is just a minimal shim I made for my own use. Shim: https://gist.github.com/TapGhoul/c8a8b59c495f546187517d964b953b75

Changing the Udon Sync method of a script on a base prefab (e.g. modifying a prefab from the Project window specifically) does not trigger a save back to the prefab like any other changes typically would. The main reason this is an issue is that it makes it impossible to mass change the Udon sync method of many prefabs at the same time. SDK 3.7.2b3

SDK Version 3.7.1 In the import settings for a Mesh or Skinned Mesh asset (e.g. FBX) primarily built from four-sided polygons, enabling the 'Keep Quads' import option will significantly reduce the Triangle count in the SDK Builder panel, affecting the avatar's Performance Rank in the SDK's eyes. With Keep Quads enabled, a Very Poor avatar with >70k tris can be counted as a Medium avatar with <70k tris by the SDK, despite the actual GPU triangle rendering cost being the same for both. Additionally, enabling this option separates the quads and tris into separate material slots, on a per-material basis: meaning one, or more, extra draw calls per mesh. Users may inadvertently think they are optimising their avatar by doing this, when in reality the GPU load remains unchanged, but CPU load is increased.