SDK Bug & Feature Requests

The current script in SDK 3.10.4 ( com.vrchat.base\Editor\VRCSDK\PerceptualPostProcessor.cs ) has issues where it is not respecting the settings defined in the texture importer (including normal map configurations), resulting in broken mip-maps for textures which invert, configure, or otherwise modify the texture channels. Attempting to fix with debugging.

Something is wrong with the material inspector for the new mobile toon standard shader. The properties seem to stick if updated by anything other than the user clicking. And although they actually update, the visuals in the inspector display the old state. Repro: Set up a material with Mobile Toon Standard and give it some textures, change properties, etc. Go to the top right three dots: Reset. Material in scene resets, but inspector still displays the old state, as if nothing changed. This also affects other things that change the material properties, such as material variants. Properties will not update properly and the entire UI state gets very confusing. This is also affects 3.8.0, this is not a regression, just an overall issue with the new shader's inspector.

While normal map textures still show the preview as the normal lavender-ish color for normal maps, but the it seems like the generated mipmap levels are light-red, as visible in the lower project window texture preview icon. (screenshot attached) This causes everything in my world that uses a normal map to be excessively shiny/reflective, and lights bleed through walls and floors. As a workaround, I can individually switch all my normal map textures to Box instead of "Kaiser", but then the world upload linter then warns about these and pressures me to let it switch them back to (the broken) "Kaiser". I have had to disable DPID for my world for the time being.

〇 Environment OS: Windows 11 Pro 25H2 Build 26200.8457 Unity: 2022.3.22f1 VRCSDK: 3.10.3 〇 Summary When performing local world tests using Build & Test Your World or Test Your Last Build, launching multiple clients simultaneously may cause the second and subsequent clients to become stuck on a black screen. Launching clients with a delay between each instance can partially mitigate the issue. 〇 Steps to Reproduce Open the VRChat SDK in Unity. Run Build & Test Your World or Test Your Last Build. Launch multiple clients at the same time. The second and subsequent clients may remain stuck on a black screen and fail to proceed. 〇 Additional Reproduction Conditions Based on investigation, this issue appears to be indirectly related to log output. The issue occurs consistently under the following conditions: Disable debug log output for the client. Launch the first client. Launch the second and subsequent clients. The additional clients will consistently become stuck on a black screen. 〇 Possibly Related Issue A potentially related issue, also suspected to be caused by log output, was observed: When two clients are running in a local test and are in the same world, performing a rejoin from one client causes VRChat to crash. After this occurs, VRChat will continue to crash consistently when rejoining the same world, even when running only a single client. This issue can be resolved by deleting the log files in the following directory: %HOMEPATH%\AppData\LocalLow\VRChat\VRChat 〇 Suspected Cause It is likely that a deadlock or similar resource contention involving log files is occurring, causing clients to freeze or crash. 〇 Expected Behavior All clients should launch and enter the world normally when running multi-client local tests. Rejoining a world should not cause crashes regardless of log file state. 〇 Actual Behavior The second and subsequent clients may freeze on a black screen when launched simultaneously. Under certain conditions, rejoining a world causes VRChat to crash persistently until log files are deleted. 〇 Notes This issue significantly impacts local multi-client testing workflows and should be addressed with high priority.

This affects all versions from when Multi-Upload was added through the current 3.10.4 . If all three platforms are selected for multi-upload, the SDK will successfully upload each platform, but then it will continue in an infinite loop of uploading each platform over and over again forever. Uploading just Android and iOS seems to work fine.

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

Attampting to upload avatar without adding tags is bugged. It gives an error stating: "tags must be an array: null, tags must be a string: 'null'" The error wont be given if you add atleast 1 tag. Running VRChat SDK - Base and VRChat SDK - Avatars at version 3.10.4

The SDK "Review Any Alerts" window flags all textures using Box mipmap filtering. However, if you use the "Auto Fix" feature or manually change normal maps to 'Kaiser', it breaks the vector shading. This causes harsh, reflective artifact lines across the materials in the scene. Normal maps require Box filtering to calculate lighting correctly. The SDK alert should automatically exclude textures that are explicitly set to the "Normal map" Texture Type so creators don't accidentally ruin their shading.

When I try to use "Build & Test" with a number of clients above 1, one of the windows works fine, but all the others just sit on a black screen and won't even let me close them without doing End Task in the task manager. I also actually tried manually launching two instances myself, using the --profile=1 argument for the second one, and encountered the same problem, so this might not be specific to Build & Test.

Whenever I upload to both Platforms (PC and Android) it keeps switching between builds and uploads the avatar over and over (this was the newest version of the sdk that just came out)