Print Model

Not part of the actual try-on pipeline - this one's a debug tool the pack author apparently left in for anyone poking around the internals. It takes a MODEL, and it outputs the exact same MODEL. Wiring it into a graph changes nothing about what runs; the whole point is what it does on the side while your model passes through.

What it's for

Being honest about the source here: the pack's README never mentions this node, and its own node_description field is blank. So this is read from the shape of it rather than any documentation - an input and an output of the identical type is the textbook signature of a pass-through debug node, the kind you build for yourself while wiring up a loader, find genuinely useful, and leave in the public release. Given the class name, the reasonable read is that it dumps some representation of the model object to the ComfyUI console when the node runs, then hands the identical object on downstream so nothing else in your graph even notices it's there.

Where that's actually useful: right after LoadCatvtonFluxLoRA, where you're feeding in your own locally-loaded Flux Fill checkpoint and applying a LoRA on top of it. If the try-on results are coming out wrong and you suspect you accidentally wired in a plain Flux Dev checkpoint instead of a Fill-dev one, splice ModelPrinter in right after your loader, queue a run, and check the console output - a quick way to confirm what actually got loaded before you go chasing the wrong bug in the sampler settings.

Inputs and outputs

There's exactly one of each, and neither has any configuration:

• MODEL in - whatever model object you want to inspect.
• MODEL out - the same object, unmodified, wired onward to wherever it would have gone anyway.

No widgets, no dropdowns, nothing to set. You place it, connect it, and read the console.

Installing it

Same install as the rest of the pack. Search ComfyUI-CatvtonFluxWrapper in ComfyUI Manager, or clone it by hand:

cd ComfyUI/custom_nodes
git clone https://github.com/lujiazho/ComfyUI-CatvtonFluxWrapper

Restart ComfyUI and it'll show up under the pack's node category alongside the loaders and the sampler. It has no extra dependencies of its own beyond what the rest of the pack already needs.

Where people get burned

Because it's a pure pass-through, "my workflow broke after I added this node" almost never means the node itself is the problem - it isn't touching the model object at all, so if something downstream changed behavior, look upstream of ModelPrinter, not at it.

The more common snag is seeing nothing in the console at all. That's usually a plain ComfyUI execution quirk rather than anything specific to this node: if its output doesn't actually feed into something else that gets executed, ComfyUI may not run the node at all depending on how your graph and queue mode are set up. Make sure the pass-through output is actually wired into the rest of your pipeline, not just dangling.

And a fair caveat since there's no public documentation for this one: exactly what gets printed isn't guaranteed to be anything in particular. Treat it as "wire it in and see what shows up" rather than expecting a specific, documented format.