Three additive widget upgrades on Pixal3DImageToMesh — purely
wrapper-layer additions that leave the pipeline.run() integration
unchanged. Defaults are backward-compatible: every existing workflow
behaves identically to v0.1.4.
New widgets (all optional, all default to existing v0.1.4 behavior):
• save_to_output_dir (BOOLEAN, default True) — when False, skip
auto-saving the GLB to ComfyUI/output. Useful for chained
workflows that export via Trellis2ExportTrimesh / SaveGLB
downstream.
• output_filename_prefix (STRING, default "pixal3d") — customize
the saved GLB's filename prefix. Final name:
<prefix>_<unix_ns>_<seed>.glb. Sanitized to ASCII alnum + _ -
so no path traversal.
• (keep_warm from v0.1.4, unchanged)
New output port (RETURN_TYPES 4-tuple → 5-tuple):
• glb_path (STRING) — absolute path of the saved GLB. Connect
directly into Preview3D's model_file to skip the explicit
Trellis2ExportTrimesh hop. Empty string if save_to_output_dir
is False.
Pixal3DLoadPipeline now logs per-stage timing (pipeline load,
MoGe load, total) so users diagnosing "is it stuck?" can see
each phase break down.
Live verification (static): six tests covering INPUT_TYPES schema,
RETURN_TYPES extension, run_pixal3d signature plumbing,
generate() pass-through, save-conditional branch existence,
and module import cleanliness. The pipeline.run() call path is
byte-for-byte identical to v0.1.4 (which was live-tested in
section c.f. commit history).
Why not add use_tiled_decoder / Pixal3D-T / per-stage memory mgmt:
upstream investigation confirmed those features live in
TRELLIS2's wrapper layer (per-stage ComfyUI nodes), not in
Tencent's pipeline.run(). Adopting them would mean rewriting our
single-node design into a multi-node graph — out of scope. See
README "Upstream roadmap" section.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
