TL;DR: meshController is a C++ plug-in for Autodesk Maya that adds surface pinning, mesh-driven controls, and VP2 viewport tooling for character and facial rigging.
What shipped, and what it targets
meshController is a free C++ plug-in for Autodesk Maya that focuses on surface pinning, mesh surface binding, and VP2 viewport controls for production facial and character rigs. It comes with six node types and five commands, plus an example Maya scene file with a face rig and textures. Pricing is simple: free in the sources.
The core idea borrows from the DreamWorks Animation Premo approach: controls that sit on the character surface instead of floating curve shapes. For artists, that means you interact directly with mesh-based controls that feel visually welded to the character, while still behaving like standard Maya controls for selection and manipulation.
If you live in the rigging trenches, the important part is not the concept. It is whether the nodes solve daily problems cleanly, evaluate fast, and fail predictably when you do something dumb at 3 a.m.
The plug-in in plain technical terms
The documentation calls meshController a “production-grade” toolset for Maya 2023 and later on Windows, with parallel evaluation via oneTBB and viewport interaction using Qt. The compiled plug-in registers as meshController.mll and loads through Maya Plug-in Manager or via a loadPlugin call.
First, Surface Pin. The surfacePin node binds rig controls to a deforming mesh so they track position, orientation, and twist. The workflow binds at a chosen pose, stores bind data, and then reads deformed mesh positions at runtime. surfacePinBind handles binding and supports undo and redo. A key feature is a localInverseMatrix input intended to solve double transforms inline when the pin drives offset controls in a facial hierarchy. The docs also state the node preserves the current transform offset at bind time so controls keep their authored pose.
There is also surfaceUVPin, a UV space variant. Pins store UV coordinates so they can survive topology changes as long as the UV layout stays stable. That is particularly relevant to facial rig work, where meshes evolve mid-show while UVs sometimes remain the one stable thing everyone agrees not to touch.
Second, vertexWrap. This is a lightweight deformer designed to snap split or matching topology meshes to a driver mesh via one-to-one vertex mapping. The docs describe it as avoiding proximity search at evaluation time. It computes a mapping at bind time, then directly copies driver vertex positions to the driven meshes at eval time. The intended use case is lots of small control shapes that must stick to a deforming face.
Sprinkled on top are viewport tools. The docs list shapeControl as a VP2 custom locator with mesh or curve display and hover highlighting. They also list meshControlOverlay, which draws an overlay and hover marker, and meshControlMode, an interactive placement mode that uses Qt mouse move hit testing and viewport overlay feedback. The docs include a comparison table explaining when to prefer shapeControl versus meshControlMode, including a warning to avoid large numbers of live shape controls and to use the overlay path for big sets.
Somewhere around here you will want to resist the urge to replace every curve controller with a mesh. The sources themselves recommend using these controls selectively for main controls rather than replacing everything. But where is the fun in that.
Requirements, downloads, and what you actually get
The download page lists meshController v1.0.0 for Windows and Maya 2023 or later. It also lists a Linux version as “not available yet”. It recommends an NVIDIA GPU for GPU override.
For installation, meshController loads through the plug-in manager or by loading the plug-in by name. Once loaded, all nodes and commands become available immediately.
Licensing, pricing, and the boring bits
meshController is free to download, with documentation and an example scene. They do not specify a commercial license in the sources provided here.
Versioning in the sources: the docs label meshController v1.0 and Maya 2023+, and the download page lists meshController v1.0.0.
If you want to test it properly, build a small facial sandbox scene, swap a couple of core controls to mesh-based shapes, and watch evaluation and selection behavior under your usual shot workflows. Do not start by rewiring the whole face. That is how you end up with a sufrace pin node you love and a manpiulators bug you cannot explain to production.
