Object Call To Curve Clear

The cleanup half of a pair - this one only makes sense next to Object Call To Curve, also covered on this site. Both are from Avatar Graph, Avatech AI's pack for turning a single character portrait into a real-time interactive 2D avatar using Blender's Python engine (bpy) as its rigging/mesh backend, and both belong to the large ObjectCall_* family of auto-generated Blender-Object-API wrappers with no individual documentation anywhere in the pack's README.

object.to_curve() evaluates a curve, text, or surface-type object and bakes the result into a standalone, temporary Curve datablock. Per Blender's own docs, that temporary data has to be freed explicitly when you're finished with it - object.to_curve_clear() is that cleanup call. Skip it and the temporary curve data from every To Curve call keeps accumulating, which in a repeatedly-executed graph (loops, re-runs) means memory that never gets released - not a crash, just quiet, cumulative bloat over a long session.

Worth being honest about scope here: Avatar Graph's own documented pipeline is entirely mesh-based (segmented image planes → mesh layers → shape keys → export), so there's no obvious point in the pack's normal workflow where curve data - and therefore this cleanup node - would ever come up. If you're not intentionally working with curve-type objects in a custom graph, you're unlikely to ever need this node or its To Curve counterpart.

Schema is as bare as it gets: BPY_OBJ in (optional per the schema, but nothing to clean up without one wired in from whatever object you called To Curve on) and BPY_OBJ out, same handle passed through with the temporary curve data freed. No configurable fields, matching Blender's underlying no-argument call.

Installing it means installing the whole Avatar Graph pack. Via ComfyUI Manager: search "Avatar Graph" and install. Manually: cd ComfyUI/custom_nodes && git clone https://github.com/avatechai/avatar-graph-comfyui, then cd avatar-graph-comfyui && pip install -r requirements.txt, restart. bpy needs Python 3.10.x exactly, so the README's recommended dedicated conda create --name comfyui python=3.10 environment is worth setting up rather than reusing an existing Flux/SDXL one. Restart with --enable-cors-header (--force-fp16 too on macOS) for the live avatar preview.

Troubleshooting: bpy failing to import at ComfyUI startup because the Python version isn't exactly 3.10.x is the failure you're actually most likely to hit, a genuinely common, recurring category of pain across Blender-Python-based ComfyUI nodes broadly. This node itself has essentially no failure surface - the real risk is upstream, forgetting to pair it with To Curve at all, which won't error but will let temporary data pile up. --enable-cors-header only affects the live preview panel; skipping it doesn't change how this node behaves.