Object Multires External Pack

Object_MultiresExternalPack is the "put it back" half of Blender's external multires workflow. The Multires modifier can store its high-resolution displacement in external .bpyx files instead of inside the .blend - handy when you want a small file or to share displacement separately. This node packs that external data back into the scene, undoing the external save.

What it actually does

It's a wrapper around bpy.ops.object.multires_external_pack(), auto-generated like the rest of Avatar Graph's Object_* family. There's exactly one input - BPY_OBJ - and one output, the same BPY_OBJ. No modifier name, no options. If the object you pass in has a Multires modifier whose displacement points at external .bpyx files, this node pulls the data back into the Blender file so the modifier no longer depends on those files on disk.

When you'd use it

Only if you or an upstream node used Object_MultiresExternalSave first. That's a deliberate, somewhat unusual choice for an avatar pipeline - external displacement files are a Blender production workflow thing, not a typical "rig my character" thing. If you never touched external save, this node is a no-op. It's here because the pack generated the full object-operator surface, and it's one of the more esoteric entries in the list.

How it works

Standard plumbing: the node sets the BPY_OBJ as the active object in the shared headless Blender scene, runs the operator, and returns the object for further chaining. Because it needs the object to already carry a Multires modifier with external displacement, the wiring is really "whatever you passed through Object_MultiresExternalSave earlier in the graph."

Installing it

Same pack, same install:

• ComfyUI Manager: search "Avatar Graph", install, restart.
• Or:

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

Watch the bpy==3.6.0 requirement: Python 3.10 only. Anything newer means "no module named bpy" and the pack won't load at all. The README walks Windows users through a bundled Python 3.10 environment (ComfyUI_3.10.7z, run run_nvidia_gpu_3.10.bat); on Linux/macOS, conda with python=3.10.

The honest take

You will probably never use this node, and that's fine. It exists because Avatar Graph exposes Blender's whole object-operator surface rather than just the pieces an avatar needs. If you're here because a workflow template imported it, you can usually delete it without harm - but if you're doing the external-save dance deliberately, this is the node that makes the file self-contained again before export.