DP Switch Controller

Big workflows accumulate a lot of independent on/off decisions - are you doing txt2img or img2img right now, is IPAdapter active, is ControlNet active. Wiring each of those as a separate boolean scattered across your canvas gets messy fast. DP Switch Controller bundles three of the most common ones into a single node with a single output, so one wire carries all three settings instead of three separate ones tangled through your graph.

How it works

Three dropdowns, each a straightforward on/off (or mode) choice: Mode_Settings picks Txt2Image or Img2Img, IPadapter_Mode picks IPadapter_OFF or IPadapter_ON, ControlNet_mode picks Controlnet_OFF or Controlnet_ON. All three get packed into one output typed as SWITCH_SETTINGS - a custom type specific to this pack.

That custom type is the important detail. This node doesn't do any branching itself - it produces a settings bundle, and it's genuinely only useful once you wire that bundle into another node elsewhere in this pack that's built to read a SWITCH_SETTINGS input and actually branch your workflow based on it. On its own, with nothing downstream consuming the output, this node changes nothing.

Inputs and outputs

Required, all three are enum toggles:

• Mode_Settings - Txt2Image (default) or Img2Img.
• IPadapter_Mode - IPadapter_OFF (default) or IPadapter_ON.
• ControlNet_mode - Controlnet_OFF (default) or Controlnet_ON.

No optional inputs.

One output: settings, typed SWITCH_SETTINGS - a bundle of all three choices, meant to feed a matching node elsewhere in this pack.

Installing it

ComfyUI Manager: search ComfyUI-Desert-Pixel-Nodes, install, restart. Manual:

cd ComfyUI/custom_nodes
git clone https://github.com/DesertPixelAi/ComfyUI-Desert-Pixel-Nodes

Restart ComfyUI. This pack ships 100+ nodes total; this article covers 20 of them, and the node(s) that actually consume a SWITCH_SETTINGS input aren't among those 20 - so if you install just to try this specific node, be aware it needs a matching consumer elsewhere in the full pack to do anything visible. Browse the "Switches & Controllers" section of the pack's own README, or search DP in the node browser, to find it.

Where people get tripped up

The most likely confusion is exactly the gap noted above: wiring this node's output nowhere, or into something that doesn't accept a SWITCH_SETTINGS type, and expecting flipping the dropdowns to change your generation. Because the output is a custom typed bundle rather than a plain boolean or string, ComfyUI's type system will refuse a connection to anything not built to accept it - if you can't find a valid place to plug it in, that's the type system telling you the consuming node isn't in your current graph yet, not a bug in this node.

The three settings are also independent of each other - this node doesn't enforce any logic between them (it won't stop you from setting Mode_Settings to Img2Img while leaving both IPadapter_Mode and ControlNet_mode off, which is a perfectly normal combination). Don't expect it to validate that your combination makes sense for your actual workflow; it's a labeled bundle, not a rules engine.