Add USD Specializes

Specializes is the quiet cousin of references, and even people who use USD daily sometimes struggle to explain it. A specialize arc says: "this prim is a specialized version of that prim - same shape and defaults, but I'm going to override specific pieces." It's the least-used of USD's four composition arcs (reference, payload, sublayer, specialize), and you can absolutely do real work without it. But it exists because references come with a catch: when you reference another prim, you're usually getting a copy-like relationship where override semantics get fiddly. Specializes is designed for "make me a modified version of that thing, and keep it a version of that thing."

Realistically, this is the node you reach for when you're building a component library - a base mesh defined once, specialized into a dozen variants that each tweak a couple of attributes. The base prim stays authoritative; each specialist only stores its deltas. If you're wondering "do I need this?" the honest answer is probably not yet.

How it works

One line of USD API: prim.GetSpecializes().AddSpecialize(Sdf.Path(specializes_prim_path)). That stamps a specializes arc on the prim pointing at the target. When the stage resolves, the specialized prim inherits everything from the target and then layers its own opinions on top.

Two inputs, no mode dropdowns to fiddle with:

• prim_path - the specialist (default /Root/Mesh). Wildcards work, and a missing prim is created as an Xform.
• specializes_prim_path - the prim it inherits from (default /_spec_Mesh). Note this is an arbitrary path - the node doesn't create the target for you, so if nothing lives at that path, the specialize arc points at empty space and your prim effectively has no base.

Output is a USD stage with the arc added.

Install & how to sanity-check it

Pack install, same as every node here: ComfyUI Manager → "ComfyUI-OpenUSD", or

cd ComfyUI/custom_nodes
git clone https://github.com/cjhosken/ComfyUI-OpenUSD

then restart. Dependencies are the pack standard: usd-core==26.5, numpy==2.5.0, trimesh - the usd-core wheel is the big one, first install takes a minute.

The debugging gotcha is that specializes failures are silent by design. A specialize arc pointing at a prim that doesn't exist isn't an error - the stage just resolves the specialist with no inherited base, and it looks like "my node did nothing." To check your work, point a USD Viewer at the stage and confirm the target prim actually exists in the tree before you attach the arc. And one more honest note: this node has basically no community discussion anywhere - it's one of those USD features that makes sense on paper and appears in production pipelines, but if your workflow is "generate a mesh and render it," the reference and sublayer nodes are the ones you'll actually use.