🔀 CR Switch Model and CLIP

This is a two-way selector for a model-and-CLIP pair. You wire two checkpoints in, set one number, and the node passes exactly one of them through to the rest of your graph. It's the "which of these two am I using right now" switch - flip a value instead of re-dragging wires every time you want to compare.

It's part of Comfyroll Studio (Suzie1 / RockOfFire), in the logic-utilities section. Nothing here generates anything; like rgthree's context and switch nodes, it's pure quality-of-life plumbing that makes a big graph less painful to work in.

How it works

The Input value (1 or 2) picks the pair. Set it to 1 and model1/clip1 come out the MODEL and CLIP pins; set it to 2 and you get model2/clip2. Model and CLIP travel together as a unit, which matters - a checkpoint's UNet and its text encoder are a matched set, and this keeps them paired so you never accidentally run one model's CLIP against another's weights.

The inputs that matter

• Input - the selector, 1 or 2. This is the only knob. Change it to switch which pair flows downstream.
• model1 / clip1 and model2 / clip2 - the two checkpoint pairs. Pull each pair from its own Load Checkpoint node.

Outputs are MODEL and CLIP (the selected pair) plus the usual show_help link. Run MODEL into your sampler and CLIP into your text-encode nodes, exactly as you would straight off a checkpoint loader.

How to install it

• ComfyUI Manager: search Comfyroll Studio, install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/Suzie1/ComfyUI_Comfyroll_CustomNodes.git, then restart.

No models bundled with the pack itself - you bring your own checkpoints.

Common issues

The thing that surprises people: switching the Input value doesn't stop the other branch from loading. ComfyUI evaluates what's connected, so both Load Checkpoint nodes upstream still run and sit in memory. If you're trying to save VRAM by switching, this node won't do that on its own - it selects, it doesn't unload. For true "only run one branch" behavior you want a muting/bypass approach on the unused loader.

Also make sure the two pairs are actually the same architecture family if anything downstream cares - swapping an SD 1.5 pair for an SDXL pair mid-graph will break nodes tuned to one or the other. And keep model and CLIP from the same checkpoint together; the node keeps them paired for a reason, so don't cross them from separate loaders. If the node's missing from your menu entirely, that's the Comfyroll pack failing to load rather than this node - check the console for a pack-level import error.