SDK Bug & Feature Requests

On vrCavatarDescriptor inspector, “LipSync Mode” dropdown is broken. Changing it on the inspector (Normal inspector view) never changes the actual value. After Building Avatar, or in Play Mode, the original value will be “restored”. Only doing that on Debug inspector view works well. This harmful behavior has been confirmed for over 4 years. https://feedback.vrchat.com/avatar-30/p/bug-lipsync-mode-does-not-save ---------------- (same content in Japanese) The dropdown behavior of the “LipSync Mode” dropdown in vrCavatarDescriptor is broken. Even if you manipulate this item on the inspector (in Normal mode), the actual value doesn't change, and it looks like the value before the change was “restored” after the avatar was built or in Play Mode. The actual value also changes only when directly changing this value in Debug mode, and it works as intended. Similar reports of this confusing behavior have been reported for over 4 years. https://feedback.vrchat.com/avatar-30/p/bug-lipsync-mode-does-not-save

For reference, this snippet of shader code is being blocked somehow by the SDK, no longer working in-game. However, in SDK 3.8.1, it works. // Glow in the dark Emission [HideInInspector] s_start_EmissionLightBased__mID__ ("Light Based--{reference_property:_EnableGITDEmission__mIDx__,persistent_expand:true,default_expand:false}", Float) = 0 [HideInInspector][ToggleUI]_EnableGITDEmission__mIDx__ ("Light Based", Float) = 0 [Enum(World, 0, Mesh, 1)] _GITDEWorldOrMesh__mIDx__ ("Lighting Type", Int) = 0 _GITDEMinEmissionMultiplier__mIDx__ ("Min Emission Multiplier", Range(0, 1)) = 1 _GITDEMaxEmissionMultiplier__mIDx__ ("Max Emission Multiplier", Range(0, 1)) = 0 _GITDEMinLight__mIDx__ ("Min Lighting", Range(0, 1)) = 0 _GITDEMaxLight__mIDx__ ("Max Lighting", Range(0, 1)) = 1 [HideInInspector] s_end_EmissionLightBased__mID__ ("", Float) = 0

For some reason when focusing on the SDK window, it will animate/override a material on my avatar, specifically the emission 0 strength. Doesn't happen on SDK 3.8.1 or lower!

In VRCSDK 3.8.1 and later several log invokations ( VRC.Core.Logger.Log() ) in internal SDK assemblies (e.g. VRCSDKBase-Editor.dll and VRCCore-Editor.dll ) as well as VRC.SDKBase.Editor.EnvConfig.cs do not define the log category anymore, resulting in excessive console logging with no real added value to the end user. In 3.7.5 and earlier SDKs with old logger, DebugLevel.All enum was passed as a parameter every time these messages would be logged, resulting in nothing being visible to the end user. From 3.7.6 up to 3.8.0 after SDK logger rewrite, "All" string was passed as a parameter due to the DebugLevel enum getting replaced by a generic category string parameter, still resulting in all messages being hidden. In previous versions of the SDK not a single log entry would appear in the editor's console unless something important was actually happening and the end user should be informed about it. In 3.8.1 many of the category parameters were mysteriously removed, resulting in 14 entries appearing in the console on every assembly reload (see attachments). The increased logging takes up third of the console window's footprint on every assembly reload and makes it very difficult to spot actually important log entries. Below I have listed the different messages originating from DLLs in the SDK with their stack traces. (The rest are primarily from VRC.Editor.EnvConfig:ConfigurePlayerSettings() located in the VRC.SDKBase.Editor assembly) Reloading Assemblies UnityEngine.Debug:Log (object,UnityEngine.Object) VRC.Core.Logger:Log (string,string,UnityEngine.Object) VRC.SDK3.Editor.EditorAssemblies:OnCompileScripts () No local config found at 'C:/Users/[REDACTED]/AppData/LocalLow/[REDACTED]/[REDACTED]\config.json' UnityEngine.Debug:Log (object,UnityEngine.Object) VRC.Core.Logger:Log (string,string,UnityEngine.Object) VRC.Core.LocalConfig:FetchConfig (System.Action,System.Action) VRC.Core.LocalConfig:.ctor (string,bool,bool) VRC.Core.ConfigManager:.cctor () VRC.Editor.EnvConfig:ConfigureSettings () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:125) VRC.Editor.EnvConfig:EditorUpdate () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:91) UnityEditor.EditorApplication:Internal_CallUpdateFunctions () No local config found at 'C:/Users/[REDACTED]/AppData/LocalLow/[REDACTED]/[REDACTED]\null' UnityEngine.Debug:Log (object,UnityEngine.Object) VRC.Core.Logger:Log (string,string,UnityEngine.Object) VRC.Core.LocalConfig:FetchConfig (System.Action,System.Action) VRC.Core.LocalConfig:.ctor (string,bool,bool) VRC.Core.ConfigManager:.cctor () VRC.Editor.EnvConfig:ConfigureSettings () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:125) VRC.Editor.EnvConfig:EditorUpdate () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:91) UnityEditor.EditorApplication:Internal_CallUpdateFunctions () FetchConfig UnityEngine.Debug:Log (object,UnityEngine.Object) VRC.Core.Logger:Log (string,string,UnityEngine.Object) VRC.Core.RemoteConfig:FetchConfig (System.Action,System.Action) VRC.Core.BaseConfig:Init (System.Action,System.Action,bool) VRC.Editor.EnvConfig:ConfigureSettings () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:128) VRC.Editor.EnvConfig:EditorUpdate () (at ./Packages/com.vrchat.base/Editor/VRCSDK/Dependencies/VRChat/EnvConfig.cs:91) UnityEditor.EditorApplication:Internal_CallUpdateFunctions () finshed fetching and set config UnityEngine.Debug:Log (object,UnityEngine.Object) VRC.Core.Logger:Log (string,string,UnityEngine.Object) VRC.Core.RemoteConfig/<>c__DisplayClass1_0:<FetchConfig>b__0 (VRC.Core.ApiContainer) VRC.Core.APIResponseHandler/<HandleResponse>d__5:MoveNext () Cysharp.Threading.Tasks.CompilerServices.AsyncUniTaskVoid`1<VRC.Core.APIResponseHandler/<HandleResponse>d__5>:Run () (at ./Packages/com.vrchat.base/Runtime/VRCSDK/Plugins/UniTask/Runtime/CompilerServices/StateMachineRunner.cs:104) Cysharp.Threading.Tasks.Internal.ContinuationQueue:RunCore () (at ./Packages/com.vrchat.base/Runtime/VRCSDK/Plugins/UniTask/Runtime/Internal/ContinuationQueue.cs:194) Cysharp.Threading.Tasks.Internal.ContinuationQueue:Update () (at ./Packages/com.vrchat.base/Runtime/VRCSDK/Plugins/UniTask/Runtime/Internal/ContinuationQueue.cs:159) Cysharp.Threading.Tasks.Internal.ContinuationQueue:Run () (at ./Packages/com.vrchat.base/Runtime/VRCSDK/Plugins/UniTask/Runtime/Internal/ContinuationQueue.cs:118)

VRC Object Sync by default is a continuously operating script that pings locations to all players even when objects are at rest or behind the player/occluded by the world. As a result, once the object pool reaches higher numbers, over 200, frame times are permanently hindered as the game waits for all these pings. I'd tested in my world the difference between VRChat's default Object Sync script and MMMaellon's Smart Object Sync on about 212 objects. Performance with default object sync raised frame times to 16.7-17ms. MMMAellon's Smart Object Sync brought framerates down to 2.4-3ms, an overall savings of around 4-5x performance improvement. And this is not on a slow PC - this is on a Ryzen 7 7800x3D with a Noctua NH-12s cooler, an RTX 4070, and 64 GB of RAM. You cannot simply add power to fix the problem. MMMaellon's script does a lot to improve performance, but the core function allows objects at rest to stop pinging unless exerted by an external force. They are also developing a newer version of the script that cuts bandwidth in half. As VRC adds more dynamic global objects through the inventory system, I fear this issue will only become more exasperated the longer global sync gets ignored. I highly recommend enabling higher performance syncing methods by default for newer worlds and enabling the older sync system only when absolutely necessary. As many maps feature QV pens, pool tables, grabbable pillows, coffee and drink prefabs, and other grabbable synced objects, this will have an immediate performance impact across the entire game, and it's something all creators need to be made aware. https://github.com/MMMaellon/SmartObjectSync

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.

SDK fully functional, but the alerts tab is completely empty, no info, no alerts visible. No change after reinstalling the SDK, restarting, switching versions... I'm forced to make a new project to acquire avatar info and alerts again. I've heard there was a similar bug about embedding the control panel into the Unity UI and opening another project that uses the SDK, both of which I've done and may be the cause for it. ( https://feedback.vrchat.com/sdk-bug-reports/p/376-alerts-section-stops-updating-if-you-put-the-vrcsdk-into-a-tabbed-panel-and )

Avatar Descriptor breaks changing LipSync mode when magic number (67.30657) as input for X rotation for Eye Look > Rotation States. Y and Z doesn't appear to break. Tested on several other eye states and was reproducible including on an older and different project.

Within a render callback such as OnWillRenderObject, it's useful to be able to check which camera is rendering. Unity has "Camera.current" for this, but it's not exposed to Udon. The new camera API is awesome, but without a property like that, I still can't make my UdonPortals prefab render correctly in the hand-held camera because there's no way to tell which camera is currently triggering OnWillRenderObject. I'd like a property to tell which camera is responsible for the render. A really simple implementation would be a new read-only property like: VRCCameraSettings.CurrentCameraType: An enum consisting of the values "ScreenCamera" or "PhotoCamera". However, I think this API could be extended further to be even more useful. In particular, if a Camera that was created by the world (and so is already accessible to Udon) is rendering, it would be great to be able to access the actual Camera object! Just like Unity's "Camera.current", but only limited to world-created Cameras. An API might look like this: VRCCameraSettings.CurrentCameraType: Enum consisting of the values "ScreenCamera", "PhotoCamera", "WorldCamera", or "Other". "WorldCamera" would be any camera created by the current world, i.e. a Camera that's accessible to Udon. "Other" would be anything else that isn't (yet!) accessible to Udon, e.g. avatar cameras or the screenshot camera. VRCCameraSettings.CurrentCamera: A reference to the current Camera object, just like Unity's Camera.current, except it's only set when CurrentCameraType is "WorldCamera". Otherwise, it's null.

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.