Nodes/ComfyUI Flakes/Flake Model Combo
ComfyUI Node

Flake Model Combo

Flake Model Combo

By JeyzerMC·Created 4 months ago·Updated 2 months ago· 1
Flake Model Combo
    • flake_data
    model_familySDXL/Base
    preset
    overrides_json

    Flake Model Combo is the checkpoint-flavored twin of Flake Combo: same relationship to Flake Model Preset that Flake Combo has to Flake Stack. The backend loads a single preset - in fact it is FlakeModelPreset's code, a subclass that inherits everything - and hands you one flake_data pin out. The frontend is where the combo magic lives. You pick a list of model presets, and when you hit Queue, the pack cycles the preset widget through each one, generating a job for every combination across all FlakeCombo and FlakeModelCombo nodes in the graph.

    That pairing is the real use case, and it's the most satisfying thing this pack does. Think of the common photoreal-stack situation in mid-2026: you've got two or three SDXL checkpoints you rotate through, each with its own ideal resolution and sampler settings already captured in a model preset. Put those in a Flake Model Combo, put your character, outfit, and pose choices in Flake Combos, and one queue gives you the full checkpoint × character × outfit × pose matrix. The model family field matters more here than on a single preset, because it tells the pack which ecosystem each preset belongs to and where to drop the outputs (output/img/<family>/...), keeping sweeps across different bases from dumping into one folder.

    Inputs and outputs. Same shape as Flake Model Preset: model_family (default SDXL/Base), the preset dropdown, and overrides_json for per-instance overrides of steps/cfg/sampler/scheduler/filename_prefix that the widget manages for you. Output is a single flake_data pin for wiring into Flake Stack, Flake Combo, or Flake Generate. Because it loads a real preset, all the file rules apply: the preset lives in ComfyUI/models/flakes/model_presets/, the checkpoint it names must resolve under models/checkpoints/, and the node re-runs whenever a preset file changes on disk.

    The math, honestly. A combo multiplies. Three checkpoints × four poses × five outfits is sixty jobs. The Jobs: N counter on the node is not decoration - it's the last line of defense between you and a three-hour queue. Bypassed entries are excluded from the cycle, so toggle rather than delete.

    Install. ComfyUI Manager → search ComfyUI Flakes → Install, or:

    cd ComfyUI/custom_nodes
    git clone https://github.com/JeyzerMC/comfyui-flakes
    

    then restart. PyYAML is the only dependency and it ships with ComfyUI core.

    One reality check: model presets are SDXL-first right now (the README says so), so a "combo" across Z-Image and SDXL bases is more aspirational than battle-tested. For its intended job - systematic checkpoint comparisons on SDXL - this is the node that turns "which checkpoint handles this character best?" from a guessing game into a single queue.

    Categoryflakes

    Inputs (3)

    NameTypeDefaultDescription
    model_familyCOMBOSDXL/Base7 options: SDXL/Base, SDXL/Illustrious, SDXL/Pony, ZImage/Base, ZImage/Turbo, Anima/Base, +1
    presetCOMBO2 options: Select a preset..., No model preset is selected
    overrides_jsonoptSTRINGJSON override of steps/cfg/sampler/scheduler/filename_prefix. Managed by the Flake widget.

    Outputs (1)

    NameTypeDescription
    flake_dataFLAKE_DATA