🌀 BV Show LoRA Blocks

A LoRA is not one monolithic thing - it's a set of small weight patches aimed at specific blocks of the base model, and which blocks it touches determines what it does. BV Show LoRA Blocks is the inspection tool: pick a LoRA from the dropdown and it outputs the list of that LoRA's blocks. For a file you downloaded and know nothing about, that's genuinely useful intel before you start tuning it.

This plays directly into the block-weight ecosystem that this pack's vector nodes live in. Once you can see that a LoRA patches, say, the early MMDiT blocks but leaves the single-stream DiT blocks alone, you can make an informed decision about which blocks to strengthen or zero out - which is exactly what the BV Vector family and any block-weight node let you do.

Inputs

• lora_name (required) - a dropdown of the LoRAs in your models/loras folder.

One output:

• LORA_BLOCKS (LIST) - the block layout of the selected LoRA.

One thing worth noting about that dropdown: in a fresh install with no LoRAs present, it shows a single "None" entry. Populate your models/loras folder and restart, and the list fills in - the node scans whatever's on disk. So if you see nothing but "None," that's a folder situation, not a broken node.

Why you'd reach for it

Honestly, this is a niche tool even inside a niche pack. The main uses: checking whether a LoRA was built for the architecture you're running (a FLUX LoRA's block layout looks completely different from an SDXL one), and confirming the block structure before you start building block-weight vectors with the BV Vector nodes. If you never do block-weight tuning, you'll probably never touch it. If you do, it's the difference between guessing at a LoRA's shape and reading it.

Install

cd ComfyUI/custom_nodes
git clone https://github.com/BlackVortexAI/ComfyUI-BVortexNodes.git

or via ComfyUI Manager ("BV Nodes"). Restart; no pip dependencies, no model downloads.

The honest caveat

The output is a list of block names, not an explanation of what the LoRA does - you still have to know what FLUX's MMDiT versus DiT blocks are responsible for to make use of it. And if your LoRA was merged or renamed, the block list is only as informative as the file's own metadata. It's a magnifying glass, not a manual.