At first glance, it looks like a typo. "Blendh"? Shouldn't it be "BlendShape"? But make no mistake—this parameter is one of the most powerful (and misunderstood) tools for high-fidelity facial expression management.
If you’ve ever dipped your toes into VRChat avatar creation—specifically custom visemes or eye tracking—you’ve likely stumbled upon a peculiar term in the Unity Animator parameters list: vrcfaceblendh . vrcfaceblendh
Happy avatar building! 🧙♂️✨
So next time you're wiring up a custom blush, eyebrow raise, or exaggerated laugh—don't hardcode the BlendShape. Have you run into a weird issue where your vrcfaceblendh isn't responding? Double-check the parameter is in the Expressions Parameters list AND that the animation clip has the correct Skinned Mesh Renderer selected. 90% of the time, it’s one of those two. At first glance, it looks like a typo
The "h" in vrcfaceblendh ? That stands for (or historically, "head")—it's designed for face BlendShapes on a humanoid rig. Why Use vrcfaceblendh Instead of Direct BlendShape Control? You might ask: Can't I just animate the BlendShape by its original name (e.g., smile_left )? But make no mistake—this parameter is one of
While VRChat provides built-in parameters for visemes ( vrc_viseme_* ) and eye tracking ( vrc_eyelid_* ), vrcfaceblendh is part of the custom expression pipeline. It allows you to drive specific BlendShapes directly from an animation or a gesture.