SDK Bug & Feature Requests

In the new SDK 3.7.6, it's now possible to build a world on Linux, but it is not possible to launch a local test with proton. Pls add proton support, similarly to: https://github.com/BefuddledLabs/LinuxVRChatSDKPatch

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.

〇 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.

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.

Create an Excellent avatar (Robot). Add 3 particle systems, each with 2147483647 max particles and 2147483647 max lights using one shared point light prefab. Add 3 point lights. Check the SDK builder for alerts to review. Expected result: Show a Very Poor performance alert in the SDK builder about 2147483647 lights. Actual result: No alert, the lights counter has overflowed into negative integers (-2147483648 lights), "Excellent". Additional info: No effect on the avatar's stats itself if the avatar is published to VRChat. Having only 2 point lights reports 2147483647 lights in the SDK (screenshot 2), as intended.

Similar to the VRChat Keyboard, it would show both lasers from each hand on any VRC Ui Shapes with a setting enabled on it. This would be handy for any in-world ui that may require both hand lasers to be readily visible like a control panel or custom world keyboard.

Exposing ParticleSystem .Play() in the same way VRCPlayAudio exposed AudioSource .Play() , we could finally do away with the jank-ness of buffer particles and wasting extra particle systems in the performance ranking.

Getting lots of these errors in the unity console. Here are some simple steps to reproduce the errors. Create new unity project in 2019.4.31f1 import latest VRC SDK for worlds (VRCSDK3-WORLD-2021.11.24.16.19_Public) open Udon Example Scene select any object in the hierarchy create a new udon behavior component open the udon graph add a variable for an UdonBehavior[] add a reference to the new variable in the graph add the array get graph node TypeResolverException: Type referenced by 'VRCUdonUdonBehaviourArray' could not be resolved. VRC.Udon.UAssembly.Assembler.UAssemblyAssembler.CreateUninitializedDataVariable (System.String dataVariableName, System.String typeString) (at <b45aa2c5f8b540baba60e42ec85f5c1c>:0) VRC.Udon.UAssembly.Assembler.UAssemblyAssembler.VisitDataDeclarationStmt (VRC.Udon.UAssembly.Parser.Stmt+DataDeclaration stmt) (at <b45aa2c5f8b540baba60e42ec85f5c1c>:0) VRC.Udon.UAssembly.Parser.Stmt+DataDeclaration.Accept (VRC.Udon.UAssembly.Parser.Stmt+IVisitor visitor) (at <b45aa2c5f8b540baba60e42ec85f5c1c>:0) VRC.Udon.UAssembly.Assembler.UAssemblyAssembler.VisitBlockStmt (VRC.Udon.UAssembly.Parser.Stmt+Block stmt) (at <b45aa2c5f8b540baba60e42ec85f5c1c>:0) VRC.Udon.UAssembly.Parser.Stmt+Block.Accept (VRC.Udon.UAssembly.Parser.Stmt+IVisitor visitor) (at <b45aa2c5f8b540baba60e42ec85f5c1c>:0) VRC.Udon.UAssembly.Assembler.UAssemblyAssembler.Process (VRC.Udon.UAssembly.Parser.Stmt statement) (at <b45aa2c5f8b540baba60e42ec85f5c1c>:0) VRC.Udon.UAssembly.Assembler.UAssemblyAssembler.Assemble (System.String assembly) (at <b45aa2c5f8b540baba60e42ec85f5c1c>:0) VRC.Udon.EditorBindings.UdonEditorInterface.Assemble (System.String assembly) (at <1963e50294534d109b013282bf0faf6c>:0) VRC.Udon.Editor.UdonEditorManager.Assemble (System.String assembly) (at Assets/Udon/Editor/UdonEditorManager.cs:347) VRC.Udon.Editor.ProgramSources.UdonAssemblyProgramAsset.AssembleProgram () (at Assets/Udon/Editor/ProgramSources/UdonAssemblyProgram/UdonAssemblyProgramAsset.cs:82) UnityEngine.Debug:LogException(Exception) VRC.Udon.Editor.ProgramSources.UdonAssemblyProgramAsset:AssembleProgram() (at Assets/Udon/Editor/ProgramSources/UdonAssemblyProgram/UdonAssemblyProgramAsset.cs:90) VRC.Udon.Editor.ProgramSources.UdonAssemblyProgramAsset:RefreshProgramImpl() (at Assets/Udon/Editor/ProgramSources/UdonAssemblyProgram/UdonAssemblyProgramAsset.cs:36) VRC.Udon.Editor.ProgramSources.UdonGraphProgram.UdonGraphProgramAsset:RefreshProgramImpl() (at Assets/Udon/Editor/ProgramSources/UdonGraphProgram/UdonGraphProgramAsset.cs:62) VRC.Udon.Editor.ProgramSources.UdonProgramAsset:RefreshProgram() (at Assets/Udon/Editor/ProgramSources/UdonProgram/UdonProgramAsset.cs:106) VRC.Udon.Editor.ProgramSources.UdonProgramAsset:RunEditorUpdate(UdonBehaviour, Boolean&) (at Assets/Udon/Editor/ProgramSources/UdonProgram/UdonProgramAsset.cs:82) VRC.Udon.UdonBehaviour:RunEditorUpdate(Boolean&) (at Assets/Udon/UdonBehaviour.cs:200) VRC.Udon.Editor.UdonBehaviourEditor:OnInspectorGUI() (at Assets/Udon/Editor/UdonBehaviourEditor.cs:164) UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr) NullReferenceException: Object reference not set to an instance of an object VRC.Udon.Editor.ProgramSources.UdonProgramAsset.DrawInteractionArea (VRC.Udon.UdonBehaviour udonBehaviour) (at Assets/Udon/Editor/ProgramSources/UdonProgram/UdonProgramAsset.cs:122) VRC.Udon.Editor.ProgramSources.UdonGraphProgram.UdonGraphProgramAsset.DrawProgramSourceGUI (VRC.Udon.UdonBehaviour udonBehaviour, System.Boolean& dirty) (at Assets/Udon/Editor/ProgramSources/UdonGraphProgram/UdonGraphProgramAsset.cs:48) VRC.Udon.Editor.ProgramSources.UdonProgramAsset.RunEditorUpdate (VRC.Udon.UdonBehaviour udonBehaviour, System.Boolean& dirty) (at Assets/Udon/Editor/ProgramSources/UdonProgram/UdonProgramAsset.cs:85) VRC.Udon.UdonBehaviour.RunEditorUpdate (System.Boolean& dirty) (at Assets/Udon/UdonBehaviour.cs:200) VRC.Udon.Editor.UdonBehaviourEditor.OnInspectorGUI () (at Assets/Udon/Editor/UdonBehaviourEditor.cs:164) UnityEditor.UIElements.InspectorElement+<>c__DisplayClass58_0.<CreateIMGUIInspectorFromEditor>b__0 () (at <a259d3c004024353a2c217da97495055>:0) UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

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.