[3.10.6] Inspecting an avatar root in Play Mode with the Avatar Descriptor's Face Tracking foldout open with many instructions causes severe Editor lag
BluWizard
There is an AWFUL refresh loop happening in the Avatar Descriptor if inspecting your Avatar in Play Mode, specifically with Face Tracking section expanded with many mapping rows exposed (all ~102).
My Findings:
- FaceTrackingEditorContext.Tickincrements everyEditorApplication.update;, theParameterBehaviorandBlendshapesSetdrawers treat a new Tick as invalidation, so their per-element state and validation refresh on every editor frame.
- FaceTrackingBlendshapesSetDrawerdraws ALL ~102 mapping rows insaide a 280px scroll view with no visibility culling.
- Every EditorApplication.hierarchyChangedbumpsHierarchyRevision, causingCollectAmbiguousMeshPathsto runGetComponentsInChildren<Transform>(true)andCalculateTransformPathon EVERY transform of the Avatar on the next repaint.
- Cost scales with the number of Parameter Behaviors (in my testing, I had 38). Tools that add Parameter Behaviors in Play Mode like VRCFury or NDMF make this behavior much worse.
This is a severe performance issue that should be patched.
Log In