🔀 CR Model Input Switch

Same pattern as CR Latent Input Switch, applied to checkpoints instead: wire in two MODEL sources, flip one number between 1 and 2, and whichever one you picked passes through. Useful for toggling between two model branches - comparing a base checkpoint against a merged one, or switching between two fine-tunes - without rewiring anything each time you want to compare.

How it works

model1 and model2 are both optional - leave one unconnected if you're not using that branch. Input (1 or 2) decides which gets forwarded. It's a pure passthrough, not a blend: the model you didn't select simply isn't used for that run, and nothing about either model is modified.

This is genuinely simple by design, and that's the appeal - a single-purpose router rather than something you have to configure. Comfyroll ships a matching switch for nearly every socket type in ComfyUI (latent, conditioning, CLIP, VAE, image, ControlNet, text), and this is the MODEL one. If you find yourself reaching for it a lot across different types, it's worth knowing they all share the same Input 1-or-2 convention, so once you've used one you already know how the rest behave.

Inputs and outputs that matter

• Input - integer, 1 or 2. The switch.
• model1, model2 - the two optional model sources.
• Output: MODEL (whichever was selected) plus show_help.

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, restart. No models bundled - this routes checkpoints you've already loaded elsewhere.

Common issues

Same trap as its latent counterpart: leave Input on 1, swap something on the model2 branch, and wonder why nothing changed - check the switch value first before assuming a downstream problem. You also need something actually connected to whichever slot Input currently points at; both inputs being optional at the node level doesn't mean the selected one can be empty.

If you're using this to compare two full checkpoints rather than two variants of the same one, remember everything downstream (CLIP, conditioning, VAE) generally needs to come from the model you're actually routing to at that moment - mixing a model from branch 1 with CLIP encoded against branch 2's vocabulary rarely does what you want, so route the whole set together rather than switching model alone while leaving CLIP hardwired to one side.

As with every node in this pack: if it's missing from the search menu, that's the wider Comfyroll registration failing somewhere else - check your ComfyUI console for an import error before troubleshooting this node in isolation.