Object Paths Update Visible

The companion node to Object Paths Calculate, and simpler: Object Paths Update Visible wraps bpy.ops.object.paths_update_visible, which recalculates the motion-path trails on every visible object in the scene that already has one - no picking a specific object, no frame-range options. It's the "refresh all" button for viewport motion trails after something about the animation changed.

How it works

Once a motion path exists on an object (created by Object Paths Calculate or interactively in Blender), it's just cached display data - it doesn't automatically follow along if you edit keyframes afterward. This operator forces every visible object's existing motion path to recompute against the current animation state, so the trails you're looking at actually reflect the latest edit rather than a stale snapshot from before you moved something.

The inputs and outputs that matter

Just the object:

• BPY_OBJ - the object in context for the update call.

No other settings - this operator, true to its "update visible" name, sweeps every visible object with an existing motion path rather than taking parameters to scope the update. Output is the same BPY_OBJ.

How to install it

ComfyUI Manager: search "Avatar Graph" and install. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/avatechai/avatar-graph-comfyui, cd avatar-graph-comfyui && pip install -r requirements.txt, then restart. The whole pack is pinned to Python 3.10.x because it depends on bpy (Blender as a library), which doesn't publish wheels for newer Python versions - install on 3.11/3.12 and you'll either get an install failure or a missing blender node category. macOS/Linux: dedicated conda env at 3.10. Windows: Avatech's prebuilt Python-3.10 ComfyUI zip, pack installed through Manager afterward.

Common issues & troubleshooting

It appears to do nothing. If nothing in your scene has an existing motion path yet, there's nothing for this operator to update - it only refreshes paths that already exist, it doesn't create new ones. Run Object Paths Calculate first if you actually want a trail to look at.

This affects viewport display only. Same caveat as its companion node: motion paths are a Blender-viewport animation-review aid, not something that shows up in an exported .glb/.gltf or changes how the Shape Flow rig actually behaves at runtime. If you're troubleshooting the avatar's real motion, this node isn't where to look.

Missing from the README. Correct - like the rest of the pack's blender-category nodes, it's a direct, auto-generated wrapper around a Blender operator (via generate_blender_types.py), not one of the roughly seven higher-level Avatech nodes the README documents. It's a small utility that's easy to skip entirely unless you're specifically reviewing animation timing inside a Blender-facing part of the graph.