Object Paths Update
Update cached motion paths — the node you can safely ignore
- BPY_OBJ
- BPY_OBJ
Object_PathsUpdate refreshes the cached motion paths on animated Blender objects - the wrapper for bpy.ops.object.paths_update(). It's the sibling of Object_PathsClear: one clears the path cache, this one re-syncs it after keyframes change. And it's about as irrelevant to avatar rigging as a node in this pack gets.
What it is
Blender's motion paths are a viewport preview - the little trajectory lines that show how an animated object moves over time. You calculate them once, then paths_update re-runs that calculation so the preview reflects any keyframe changes. The node has a single input, BPY_OBJ (in/out), and no other options. Set the object active, run the operator, get the same object back.
Why it exists
Same reason Object_OceanBake and the particle nodes exist: Avatar Graph auto-generates a wrapper for every bpy.ops.object.* operator, and paths_update was on the list. It is not part of the avatar pipeline. Your avatar's motion comes from shape keys and the Shape Flow runtime, not from Blender keyframe motion paths. If a downloaded template includes this node, deleting it won't hurt anything.
How it works
Standard Object_* plumbing. The node makes your BPY_OBJ the active object in the shared headless Blender scene, runs the operator, and returns the same object for continued chaining. If there are no motion paths to update, it's a silent no-op.
Installing it
Ships in Avatar Graph:
- 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
Pack-wide requirement: bpy==3.6.0 only builds for Python 3.10. On 3.11+ you'll see "no module named bpy" at startup and the pack won't load. Windows: the README's bundled ComfyUI_3.10.7z + run_nvidia_gpu_3.10.bat. Elsewhere: conda with python=3.10.
The honest take
This is filler - a faithful wrapper for a Blender operator you won't need while building avatars. If you recognize that, you've already learned the most useful thing about Avatar Graph's Object_* nodes: the pack exposes Blender's entire object-operator surface, and most of it is there for completeness, not because your character needs it. The nodes you'll actually build rigs with are the mesh, shape-key, and shape-flow ones. Object_PathsUpdate is a good reminder to judge each Object_* node on whether your workflow uses it - not on whether it exists.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| BPY_OBJopt | BPY_OBJ | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| BPY_OBJ | BPY_OBJ | — |