SDK Bug & Feature Requests

VRC Light Volumes is a voxel based light probes replacement for VRChat. https://github.com/REDSIM/VRCLightVolumes Once it's introduced to avatar shaders, their appearance would be amazingly improve in appropriate worlds. Major shaders like lilToon and Poiyomi already support this system in the latest version. It would be great if Toon Standard also support this. Mobile users also can get benefits. Shader developers documentation: https://github.com/REDSIM/VRCLightVolumes/blob/main/Documentation/ForShaderDevelopers.md Japanese summary: Toon StandardでVRC Light Volumesをサポートしてほしいという要望。MobileプラットフォームでもVRC Light Volumesを利用できるようになる。

On a humanoid avatar, when the VRC Avatar Descriptor has an empty baseAnimationLayers list but customizeAnimationLayers is false, then in InitAnimLayer a NullReferenceException is thrown from element.FindPropertyRelative("type").enumValueIndex = (int)type; This is caused by EnforceAnimLayerSetup assuming there is at least one layer, and calling InitAnimLayer with index=1; list.InsertArrayElementAtIndex(1) then fails, and so the subsequent GetArrayElementAtIndex also returns null. This issue was encountered by a user of Vroid's Xavatar, and reported to me as a potential Modular Avatar bug (MA invokes this code to normalize animator layers, but this also happens just by opening the inspector normally). Stack traces: Retrieving array element that was out of bounds UnityEditor.SerializedProperty:InsertArrayElementAtIndex (int) AvatarDescriptorEditor3:InitAnimLayer (UnityEditor.SerializedProperty,VRC.SDK3.Avatars.Components.VRCAvatarDescriptor/AnimLayerType,bool,int) (at ./Packages/com.vrchat.avatars/Editor/VRCSDK/SDK3A/Components3/VRCAvatarDescriptorEditor3AnimLayerInit.cs:128) AvatarDescriptorEditor3:EnforceAnimLayerSetup (bool) (at ./Packages/com.vrchat.avatars/Editor/VRCSDK/SDK3A/Components3/VRCAvatarDescriptorEditor3AnimLayerInit.cs:166) AvatarDescriptorEditor3:OnEnable () (at ./Packages/com.vrchat.avatars/Editor/VRCSDK/SDK3A/Components3/VRCAvatarDescriptorEditor3.cs:41) Retrieving array element that was out of bounds UnityEditor.SerializedProperty:GetArrayElementAtIndex (int) AvatarDescriptorEditor3:InitAnimLayer (UnityEditor.SerializedProperty,VRC.SDK3.Avatars.Components.VRCAvatarDescriptor/AnimLayerType,bool,int) (at ./Packages/com.vrchat.avatars/Editor/VRCSDK/SDK3A/Components3/VRCAvatarDescriptorEditor3AnimLayerInit.cs:129) AvatarDescriptorEditor3:EnforceAnimLayerSetup (bool) (at ./Packages/com.vrchat.avatars/Editor/VRCSDK/SDK3A/Components3/VRCAvatarDescriptorEditor3AnimLayerInit.cs:166) AvatarDescriptorEditor3:OnEnable () (at ./Packages/com.vrchat.avatars/Editor/VRCSDK/SDK3A/Components3/VRCAvatarDescriptorEditor3.cs:41) NullReferenceException: Object reference not set to an instance of an object AvatarDescriptorEditor3.InitAnimLayer (UnityEditor.SerializedProperty list, VRC.SDK3.Avatars.Components.VRCAvatarDescriptor+AnimLayerType type, System.Boolean isDefault, System.Int32 index) (at ./Packages/com.vrchat.avatars/Editor/VRCSDK/SDK3A/Components3/VRCAvatarDescriptorEditor3AnimLayerInit.cs:131) AvatarDescriptorEditor3.EnforceAnimLayerSetup (System.Boolean isOnEnable) (at ./Packages/com.vrchat.avatars/Editor/VRCSDK/SDK3A/Components3/VRCAvatarDescriptorEditor3AnimLayerInit.cs:166) AvatarDescriptorEditor3.OnEnable () (at ./Packages/com.vrchat.avatars/Editor/VRCSDK/SDK3A/Components3/VRCAvatarDescriptorEditor3.cs:41)

The log generates an 'Force-enabling Fog' entry every time a change occours in the inspector. This seems to be introduced with the SDK 3.8.1.

This was figured out after an hour and a half of debugging. Turns out, the ClientSim staiton helper script has a bug that results in broken editor behaviour. Here's a writeup of what went wrong and my quick fix of the issue - the ideal fix is probably to use a GUID instead, but hey. There's a TODO in the SDK on the line that broke. This reproduces in 3.8.0 too, as well as earlier versions. From my postmortem - this was a mysterious crash in AquaFloat, but the bug is not in AquaFloat's code, which is why it sent us on such a wild goose chase. Postmortem: The script was crashing in a GetComponent<Floater>() in OnTriggerExit. GetComponent against an UdonBehaviour works by getting all UdonBehaviour components and matching their internal ID/name/signature (due to it not being a real type at runtime - standard U# behaviour) This was triggering when an object with a VRC Station left its bounding box. The reason why this broke is due to a ClientSim fumble. On game start, if in the editor, ClientSim attaches an UdonBehaviour, and tries to attach a default station behaviour to that. The problem is, the way it does that is it looks for a given .asset under the Assets dir (specifically vrc example stuff) - but VRC no longer places those assets there (or some other script was removing it). This caused an empty UdonBehavior component to be added without an associated Udon VM instance. When the GetComponent lookup ran, it tried to hit the VM instance to get public vars, in order to get the signature. The VM instance was null as a result of this failed load, which caused GetComponent to fail, which crashed the calling script. My quick fix (quick after 1.5 hours lol) was to modify the ClientSim station helper and fix up the path. Hilariously, there's actually a TODO comment talking about finding the asset file "properly".

It would be great if there is transparent variant of Toon Standard shader for fallback and in-SDK shader. There are many usage of transparent in avatars like: - facial expressions like blushing, heart eyes, shocked face - sun glasses - Manga iconography - fake shadow of hair on the face - Clothings with thin fabric - Hairs, especially bangs transparent/translucent eyes and eyebrows - VRoid Avatars It would be great if we can express such situations with fallback shaders, and if there are such variants, we can make avatars with exactly same looking as fallback and non-fallback shaders. In addition it would be perfect if we can change render queue for transparent materials (including fallbacked ones). Images are provided by ku10by. Thanks a lot. Image 1: Manga iconography and bangs transparent/translucent eyes and eyebrows (Maya) Image 2&3: facial expressions, heart eyes, and transparent/translucent eyes and eyebrows (Moe) Image 4: fake shadow (Sephira) Image 5: vinyl / transparent skirt (Sapphy) Related Canny: Request for toon transparent fallback shaders from era of toonlit https://feedback.vrchat.com/feature-requests/p/add-the-transparent-toon-shader-to-the-fallback-system

Currently if you want to animate most of the features on the new Toon Standard shader any other material on the same mesh will also be animated. It would be amazing if you could have a feature like Poiyomi's rename feature where by renaming the specific component of that shader when animated it will only affect that specific material within the mesh. For example currently if I have an Eye material and a Skin Material on the same mesh and I wanted to have two different floats on my avatar, one for Eye hue, and one for Skin hue using this shader and I animate them accordingly it would not work. Both my Eye and Skin would animate together, and currently the only work around one would have for this is to separate anything that animates the same settings onto separate meshes. I would need an Eye mesh and a Body mesh instead of having them combined on the same mesh in order to have them not affect eachothers animations. https://gyazo.com/54fc87aa945f3821301077af006e7a7d (Visual Example)

In the Graph of 3.8.1 the custom events list will only display one.

I would like to be able to import my purchased avatars from the Avatar Marketplace, into my Unity projects after logging into the SDK. That way, I can privately upload any modifications to my purchased avatar, directly to my account.

The FOV returned at start reflects not the current setting in desktop. Steps to reproduce 1) Add a script with these lines somewhere in your world: private void Start() { Debug.Log($"Start FOV: {VRCCameraSettings.ScreenCamera.FieldOfView}"); } public override void OnVRCCameraSettingsChanged(VRCCameraSettings cam) { if (cam.CameraMode == VRCCameraMode.Screen) Debug.Log($"OnVRCCameraSettingsChanged FOV: {cam.FieldOfView}"); } 2) Set your FOV in the graphics settings to something different than 60° (e.g. 80°). 3) Join the world and check the log. You will see: Start FOV: 60 Expected behavior The log should show: Start FOV: 80 Or maybe addtionally later in case the user setting is not available at start: OnVRCCameraSettingsChanged FOV: 80

Create a new world. Have some data in it so it takes a moment. Prepare to upload. Choose a name etc, and pick an icon. Hit build & publish, and accept the dialog While it is building, delete or move the image After telling you the error, the SDK will not recover, and requires a unity restart to fix it. This occurs on SDK 3.8.1