Nodes/Avatar Graph/Object Isolate Type Render
ComfyUI Node

Object Isolate Type Render

Solo-rendering one object type — the avatar's render-hygiene node

By avatechai·Created 3 years ago·Updated 2 years ago· 264
Object Isolate Type Render
  • BPY_OBJ
  • BPY_OBJ

Blender's render view can get noisy fast: lights, probes, empties, and all your helper objects can clutter a scene, and the export you actually want might just be the meshes. Object_IsolateTypeRender is the "render only this type" switch - it calls bpy.ops.object.isolate_type_render(), the operator behind Blender's Object > Show/Hide > "Restrict render visibility" isolation. In the Avatar Graph pack, it's how you tell the embedded Blender scene "from here on, only render objects of the active object's type."

Where does that matter? Avatar Graph builds rigged 2.5D characters for the Avatech editor, and the final AvatarMainOutput node exports the scene. If your graph has sprinkled in lights, probes, or a rig armature that shouldn't end up in the output, this node narrows what gets rendered without you having to hunt through a tree of visibility flags.

How it works

It wraps the isolate_type_render operator. The behavior: whatever the active object's type is (mesh, light, empty, etc.), render visibility gets restricted to objects of that type; everything else is set to not render. The BPY_OBJ input determines the active object (and therefore the type that wins), then passes through unchanged on output.

Nuance worth knowing: the input object's type is what's "isolated." Feed in a mesh and meshes render, lights and empties drop out. Feed in a light and you've just told the renderer to show only lights - almost never what you want. Think of it as "solo the kind of thing I'm pointing at."

Inputs and outputs

  • BPY_OBJ - the object whose type becomes the render filter; returned unchanged.
  • BPY_OBJ output - pass-through.

When you'd use it in an avatar graph

Late in the pipeline, right before export. If the workflow template has you adding lights and light probes for the real-time preview but the final GLB/AVA shouldn't carry them, isolate type render on a mesh gets you a clean mesh-only result. It's a blunt instrument - it's not per-object, it's per-type - so it's a coarse "only meshes render" switch more than a fine control.

Installing it

Part of Avatar Graph (avatechai/avatar-graph-comfyui). ComfyUI Manager: search "Avatar Graph". Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/avatechai/avatar-graph-comfyui
cd avatar-graph-comfyui && python -m pip install -r requirements.txt

Pack constraints: bpy==3.6.0 pins you to Python 3.10.x (newer Pythons fail to build it), and first launch downloads the SAM ViT-H checkpoint (~2.5 GB) plus MediaPipe models.

Common issues

The classic footgun is pointing the node at the wrong type - a helper empty instead of a mesh - and then wondering why the render came out blank. Because it filters by type, "nothing renders" usually means you isolated on a non-rendering type. Also remember this is render visibility, not viewport visibility; if you expected objects to disappear in the preview too, that's the separate Object_HideViewSet node's job. The README warns the pack is still being changed, so re-check behavior after updates.

Categoryblender

Inputs (1)

NameTypeDefaultDescription
BPY_OBJoptBPY_OBJ

Outputs (1)

NameTypeDescription
BPY_OBJBPY_OBJ