[SDK 3.11.0-beta.1] Physbones flood play mode console with "Adding null Transform to TransformAccessArray will result in degraded performance." warnings
tracked
SenkyDragon
Adding null Transform to TransformAccessArray will result in degraded performance.
UnityEngine.Jobs.TransformAccessArray:Add (UnityEngine.Transform)
VRC.Dynamics.BoneBuffer:set_Length (int)
VRC.Dynamics.MemoryBuffer:Request (VRC.Dynamics.ChainId,int)
VRC.Dynamics.PhysBoneManager:AddChains ()
VRC.Dynamics.PhysBoneManager:ScheduleExecutionJob (Unity.Jobs.JobHandle)
VRC.Dynamics.VRCDynamicsScheduler:PreScheduleDynamics (bool)
VRC.SystemsPlayerLoop:OnAvatarDynamicsPreSchedule ()
Log In
Lupis Young
Issue also occurs with Constraints
Adding null Transform to TransformAccessArray will result in degraded performance.
UnityEngine.Jobs.TransformAccessArray:Add (UnityEngine.Transform)
VRC.Dynamics.VRCConstraintManager:RegisterConstraint (VRC.Dynamics.VRCConstraintBase)
VRC.Dynamics.VRCConstraintBase:Start ()

Dexvoid
updated the status to
tracked
These messages are from Unity 6, not from the VRChat SDK. https://issuetracker.unity.com/issues/19044/transformaccessarrayadd-behaves-differently-when-the-argument-is-null-and-the-argument-is-an-int
SenkyDragon
Dexvoid The warning is still triggered by the vrcsdk. It can be avoided by adding to the array where needed rather than resizing ahead of time, or by using a placeholder object when resizing (since the physbone logic replaces it all later anyways).
I don't believe the linked unity issue is actually related, because that's a report of unity itself triggering the warning from one of its own internal bone systems, and it was already patched in the U6 editor release we're using now.

Dexvoid
SenkyDragon Indeed, just clarifying that this is from changed behavior in the engine, not in the SDK. The issue is tracked now either way.
SenkyDragon
this is harmony patched in vrcfury 1.1487