Object Set Show Name

About as simple as this pack gets: Object Set Show Name sets object.show_name, the boolean that toggles the small floating text label Blender draws above an object in the viewport showing its name. It's one of a handful of ObjectSet_ nodes in this pack that set a plain viewport-display property rather than run an operator.

How it works

There's no mechanism to explain beyond what it says: turn it on, and the object's name floats above it in the 3D viewport, useful when you've got a busy scene of overlapping character parts (eyes, mouth, hair curves, body mesh) and want to tell them apart at a glance while building or debugging a graph. Turn it off, and the label disappears. Nothing about the object's actual data, transform, or export changes either way.

The inputs and outputs that matter

• value - boolean, default false. Set true to show the name label, false to hide it.

Output is the same BPY_OBJ.

How to install it

Through ComfyUI Manager, search "Avatar Graph" and install - or manually: cd ComfyUI/custom_nodes && git clone https://github.com/avatechai/avatar-graph-comfyui, cd avatar-graph-comfyui && pip install -r requirements.txt, then restart. This pack requires Python 3.10.x because it runs Blender as a library (bpy), which only ships wheels for that exact version - anything newer and the install fails, or the blender-category nodes (this one included) don't appear at all. macOS/Linux: dedicated conda env at 3.10. Windows: Avatech's prebuilt Python-3.10 ComfyUI zip, pack installed through Manager.

Common issues & troubleshooting

Adding this and expecting some functional change. There isn't one - this is purely cosmetic viewport debugging aid, not something that affects the object's mesh, the Shape Flow rig, or the exported .glb/.gltf. If a run "does nothing" after adding this node, that's correct behavior, not a failure.

Genuinely marginal utility in an automated pipeline. Most Avatar Graph graphs run headless or export straight to file - this is more useful while you're actively looking at Avatech's live web preview and trying to tell overlapping objects apart than it is in a scripted, unattended run. There's no harm in leaving it out entirely unless you specifically need the label while debugging.

Not documented in the README. Correct - like the rest of this pack's blender-category nodes, it's a direct, auto-generated wrapper around a Blender object property via generate_blender_types.py, not one of the roughly seven higher-level nodes the README covers by hand. There's nothing deeper to look up here than what's on this page - it really is just a name-label toggle.