Nodes/ComfyUI-FilterLoRATriggers/Regional Layout Info
ComfyUI Node

Regional Layout Info

What layout did my wildcard actually pick?

By DrkSun81·Created about a month ago·Updated about a month ago· 0
Regional Layout Info
    • layout_used
    • region_count
    layout!!

    The smallest node in the ComfyUI-FilterLoRATriggers pack, and the one that saves the debugging session. RegionalLayoutInfo does one thing: it takes a layout token, normalizes it the same way the pack's mask node does, and tells you what it actually means - as a clean string and a region count. No masks, no dimensions, no fuss.

    Why would you want that? Because in the workflows this pack was built for, the layout isn't a widget you set - it's a line pulled from a text file (Master_List_NTR_v2_Layouts.txt) via WildPromptor, so each generation rolls a different split for your regional scene. When you've got "3" and "LR" and "TOPMIDBOTTOM" all feeding the same wire, you lose track of which layout you actually got. This node answers that in two numbers.

    How it works

    It shares the exact same normalize_layout() function as RegionalLayoutMasks, so layout_used here is guaranteed to match the layout_used the mask node reports for the same token - same aliases (2!!, 3!!!, LR!!, TOPBOTTOMTB, TOPMIDBOTTOMTMB, SINGLE/FULL/1OFF), same fallback to !! for anything unrecognized. It's not a second implementation that could drift; it's the same table, read out for you.

    The region count follows the presets: OFF counts as 1 (the full frame), !! and TB as 2, !!! and TMB as 3.

    Inputs and outputs

    • layout (required, default !!): the token to parse. It's forceInput, so it takes a wire - which is the point, since your layout usually comes from a wildcard or a switch further up the graph.
    • layout_used (STRING): the normalized token - !!, !!!, TB, TMB, or OFF. Always the canonical form, never the alias you fed in.
    • region_count (INT): how many regions that layout implies.

    Two practical uses: pipe layout_used into a display or text node so you can see what ran on that seed, or branch on region_count - three regions means three prompt blocks to wire up, two means two. Some workflows use it to drive a switch that routes the right set of character prompts to the sampler. That's the "Info" in the name doing real work.

    Installing it

    Identical to the rest of the pack, because it ships in the same repo.

    cd ComfyUI/custom_nodes
    git clone https://github.com/DrkSun81/ComfyUI-FilterLoRATriggers.git
    

    Then restart ComfyUI and confirm [ComfyUI-FilterLoRATriggers] registered: [...] in the console. Or use ComfyUI Manager and search for the pack title. No models, no extra dependencies - torch comes with ComfyUI, and this node barely needs that.

    Where people get burned

    • It reports the preset table, not your render. If you feed it a typo like TOPPBOTTOM, you'll silently get the !! fallback and a region count of 2, which looks right until you notice your composition flipped to a side-by-side. That fallback is honestly the feature: garbage in, visible !! out. Treat an unexpected layout_used as the first clue your wildcard line was malformed.
    • Don't use it as a validator for the whole graph. It confirms what token the layout resolved to; it won't tell you whether your masks align with the latent. That's RegionalLayoutMasks's job to check, by comparing layout_used on both.

    It's a boring node. It doesn't generate anything, it doesn't blend anything. But when your layout comes from a text file and you're rerolling seeds at 2 a.m., the difference between "what did it pick?" and knowing is exactly this node.

    Categoryutils/regional

    Inputs (1)

    NameTypeDefaultDescription
    layoutSTRING!!

    Outputs (2)

    NameTypeDescription
    layout_usedSTRING
    region_countINT