[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
tracked
BluWizard
There is an AWFUL refresh loop happening in the Avatar Descriptor if inspecting your Avatar in Editor Mode or 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.
My suspicions believe this has gone unnoticed since most users utilize non-destructive tools like VRCFury or NDMF to add the Parameter Behaviors and Face Tracking instructions at upload time. Either way, if this scenario is caused normally, it is a severe performance issue that should be addressed.
Log In

StormRel
updated the status to
tracked
BluWizard
See comments replying to this one for some benchmarks I've made. For reference, "Your saved layout" is with all sections expanded.
I benchmarked viewing it in Editor Mode and Play Mode.
BluWizard
### Play Mode
- Unity 2022.3.22f1, VRChat SDK avatars 3.10.6, Play Mode, inspector AvatarDescriptorEditor3 (VRC.SDK3A.Editor)
- Avatar "VRC Mayu Oyama Blu PC": 322 transforms, Face Tracking on (Use All Tracking Keys on), 1 face tracking mesh(es), 2 blendshape set(s), 38 parameter behavior(s), LipSync mode "Viseme Blend Shape Face Tracking"
- SerializedObject.Update() on this descriptor: 0.14 ms per call (OnInspectorGUI calls it every pass, OnSceneGUI on every Scene view event while the avatar is selected)
| Inspector layout | Mean ms/frame | Median | p95 | Max | Editor frame interval (mean) | vs baseline |
|---|---:|---:|---:|---:|---:|---:|
| Baseline: every section collapsed | 0.56 | 0.56 | 0.63 | 0.68 | 6.40 ms | ×1.0 |
| Your saved layout | 147.3 | 147.3 | 153.2 | 155.1 | 161.2 ms | ×261.0 |
| All sections open except Face Tracking (Colliders left closed) | 6.83 | 6.81 | 7.31 | 7.43 | 15.3 ms | ×12.1 |
| Face Tracking open, both sub-sections collapsed | 2.37 | 2.33 | 2.60 | 2.72 | 8.84 ms | ×4.2 |
| Face Tracking + Blendshapes Sets | 3.48 | 3.39 | 3.89 | 4.97 | 10.1 ms | ×6.2 |
| Face Tracking + Parameter Behaviors | 4.70 | 4.66 | 5.12 | 7.04 | 10.5 ms | ×8.3 |
| Face Tracking + both sub-sections | 5.58 | 5.57 | 6.00 | 6.69 | 11.0 ms | ×9.9 |
| Face Tracking + both, one hierarchy change per frame | 6.05 | 6.05 | 6.34 | 6.94 | 11.5 ms | ×10.7 |
ms/frame = one Layout + one Repaint pass of the descriptor's OnInspectorGUI, 90 frames per row after 5 warm-up frames. Editor frame interval = time between repaints of the benchmark window, i.e. one full editor loop (includes the Game/Scene views in Play Mode). The hierarchy-change row bumps FaceTrackingEditorContext.HierarchyRevision and calls Invalidate() once per frame, which is what the SDK's own hierarchyChanged listener does.
BluWizard
### Editor Mode
- Unity 2022.3.22f1, VRChat SDK avatars 3.10.6, Edit Mode, inspector AvatarDescriptorEditor3 (VRC.SDK3A.Editor)
- Avatar "VRCF Test Copy for VRC Mayu Oyama Blu PC": 322 transforms, Face Tracking on (Use All Tracking Keys on), 1 face tracking mesh(es), 2 blendshape set(s), 38 parameter behavior(s), LipSync mode "Viseme Blend Shape Face Tracking"
- SerializedObject.Update() on this descriptor: 0.13 ms per call (OnInspectorGUI calls it every pass, OnSceneGUI on every Scene view event while the avatar is selected)
| Inspector layout | Mean ms/frame | Median | p95 | Max | Editor frame interval (mean) | vs baseline |
|---|---:|---:|---:|---:|---:|---:|
| Baseline: every section collapsed | 0.57 | 0.55 | 0.76 | 0.80 | 10.3 ms | ×1.0 |
| Your saved layout | 146.6 | 145.8 | 152.5 | 155.5 | 237.8 ms | ×255.5 |
| All sections open except Face Tracking (Colliders left closed) | 6.56 | 6.55 | 6.98 | 7.59 | 17.2 ms | ×11.4 |
| Face Tracking open, both sub-sections collapsed | 2.28 | 2.27 | 2.48 | 2.56 | 12.0 ms | ×4.0 |
| Face Tracking + Blendshapes Sets | 3.49 | 3.47 | 4.04 | 4.31 | 13.4 ms | ×6.1 |
| Face Tracking + Parameter Behaviors | 4.83 | 4.83 | 5.26 | 5.38 | 15.2 ms | ×8.4 |
| Face Tracking + both sub-sections | 5.82 | 5.84 | 6.34 | 6.55 | 15.7 ms | ×10.1 |
| Face Tracking + both, one hierarchy change per frame | 6.17 | 6.18 | 6.49 | 6.66 | 16.0 ms | ×10.7 |
ms/frame = one Layout + one Repaint pass of the descriptor's OnInspectorGUI, 90 frames per row after 5 warm-up frames. Editor frame interval = time between repaints of the benchmark window, i.e. one full editor loop (includes the Game/Scene views in Play Mode). The hierarchy-change row bumps FaceTrackingEditorContext.HierarchyRevision and calls Invalidate() once per frame, which is what the SDK's own hierarchyChanged listener does.