SDK Bug & Feature Requests

An occlusion strength of 0 should look identical to a material without an occlusion map but in this case it looks identical to an avatar with a pure black occlusion map this is because in the shader the occlusion map is multiplied by the occlusion strength when instead it should be lerp(1.0, occlusion_map, occlusion_strength) the issue can be seen in the first attached gif as well as the comparisons with no occlusion map and a pure black occlusion map the second attached gif shows how this should look by using the unity built in standard shader

Been running into an interesting bug relating to vrc constraints. I will be using this avatar as an example: avtr_c32b6dbf-e8f8-46a4-a338-4828d68e307e It uses VRC Constraints for twist bones in many places. For some reason the lower arm twist bones start to drift out of alignment over time in some circumstances. They have only one axis (Y) frozen, but somehow they slowly drift more and more along the other two axis. Once the bug starts, they seem to very very slowly "orbit" around their pivot over time. The furthest I've seen them go is completely backwards (wrist pointing towards elbows), though usually the effect starts quite subtle. The constraint still appears to function otherwise perfectly, the weight slider even offsets it towards the resting position (though with the bugged rotation it is still in the wrong place). The strangest part is that it only seems to affect these two constraints on the lower arms, despite there being many more very similar constraints all over the avatar. I suspect it has something to do with gimbal lock and floating point precision. Resetting the avatar or doing anything that reloads the avatar fixes it instantly, until the next time it occurs. Repro: Wear this avatar avtr_c32b6dbf-e8f8-46a4-a338-4828d68e307e Go to this world wrld_66431182-f46c-45c9-9c8e-ba7f47c10177 Sit in any chair on the vehicle. Wiggle / move around in chair, like your having a convo, or practically anything to move the avatar After a bit, check to see if the lower arm joints no longer line up at the elbow. If arms not separated, continue step 4.

A guess someone suggestion to this problem is a "Rounding Error". This issue seems to cause the position to update despite there being no reason for it too! This causes issues where prefabs don't play nice and it acts like it doesn't apply. This is due to the position constantly changing when it shouldn't.

Discovered that on SDK 3.7.0, VRC Parent and Position Constraint cause the object to move away from the source if the object size is 0, which can be fixed as long as the object size is not 0 (can be 0.0001). This problem show up on VRC because it automatically convert Unity Constraint into VRC Contraint which causes player Nameplate/Nametag to be really high up.

Burst compile warnings like below consistently appear after script compiliation. It happens even in completely new project (i.e. no other VPM package is installed). Unity Verison: 2022.3.22f1 SDK Version: Base 3.7.0 + Avatar 3.7.0 -------- Full log message: Compilation was requested for method UnityEngine.Jobs.IJobParallelForTransformExtensions+TransformParallelForLoopStruct 1[[VRC.Dynamics.WriteTransformJob, VRC.Dynamics, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]], UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null::Execute(VRC.Dynamics.WriteTransformJob&, VRC.Dynamics, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null|System.IntPtr, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089|System.IntPtr, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089|Unity.Jobs.LowLevel.Unsafe.JobRanges&, UnityEngine.CoreModule, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null|System.Int32, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089)` but it is not a known Burst entry point. This may be because the [BurstCompile] method is defined in a generic class, and the generic class is not instantiated with concrete types anywhere in your code.

In UnityEditor, VRCConstraint component inspectors have "Activate" and "Zero" buttons, which calculate rest value and offset value internally. When it comes to adding them from C# script, we have to calculate offset value manually since the "Activate" method is not public in API. The calculation process is not obvious and a bit complicated, so providing existing implementation may be helpful. Is it possible to expose the procedure as a public method like “ActivateAndPreserveOffset”?

According to the documentation for Pickup events: https://creators.vrchat.com/worlds/udon/graph/event-nodes/ “Fired when this object is held and the Use button is pressed. Fires on button down. Requires 'Auto Hold' on Desktop.“ However, for some reason at this time Auto Hold is required for OnPickupUseDown to fire in VR at all. This makes no sense, as this bool does nothing to the behavior of interacting with a pickup in VR. Please fix this! Workaround: InputUse with a couple manual pickup checks seems to work fine.

Nondestructive tools such as Modular Avatar and VRCFury create parameters and merge expressions menu assets dynamically at build time. As a result, it's often necessary to edit VRC Expressions Menu assets when no avatar in the scene has the associated parameters defined. This was possible in prior versions of VRCSDK, but in 3.7.0 the error in the screenshot is shown and changing the value of the control isn't possible without using the debug inspector. (Previously there was a warning, but it was still possible to change the value)

The parameter usage bar at the top of the expression parameters asset says ###/256 Synced Bytes. Finally, 2048 bits for our avatars! (If only)

The network IDs assigned on the VRCWorld component by the network ID tool are lost when reopening the project if that VRCWorld component is a prefab. The VRCWorld component is a prefab Running VRChats network ID tool assigns different IDs Saving the scene The new IDs can be observed on the VRCWorld component Close and open the project The network IDs on the VRCWorld component are now reverted to the state before running the network ID tool This issue only occurs if the VRCWorld is a prefab. Here is a video demonstrating this issue using the 3.4.0-creator-economy.5 SDK when building for Android with Unity 2019 https://drive.google.com/file/d/1UzULBLYrfEsJJV11sZdr-jd4RSV_nsir/view?usp=drive_link