EditUtils: Load Condition From Loras lrzjason

LoadConditionFromLoras_EditUtils is LoadCondition_EditUtils with a different filing system. Instead of listing .ckpt files from the conditions directory, its filename dropdown lists files from your models/loras/ folder - but it still actually loads the conditioning from models/conditions/, matched by name.

Read that twice, because it's the entire point. The author's intended convention is: you have a LoRA that your workflow uses, you save a conditioning named after that LoRA, and this node lets you pick the condition by the LoRA name you already recognize. "Load the condition for my consistency LoRA" becomes picking that LoRA from a dropdown full of LoRA names, and the matching .ckpt comes out of the conditions folder. If you're the kind of person who keeps a conditions/ folder with one file per LoRA setup, this is a nicer way to browse it.

The inputs and outputs are the same shape as LoadCondition_EditUtils: one filename combo box, one CONDITIONING output. If the matching file is missing or fails to load, it returns an empty list and prints an error to the console - the same silent-ish failure mode as its sibling, so keep an eye on the terminal. And same rules apply: the loaded conditioning carries reference latents inside it (that's how this pack threads references through), and it's bound to whatever model family it was encoded for. The loras/conditions naming overlap is just organizational - the node does no LoRA loading itself.

Honest take: this is a thin organizational nicety, not a workhorse. If you have exactly one LoRA per workflow, plain LoadCondition_EditUtils does the job and you can ignore this one. Where it earns its place is a multi-LoRA editing setup where you swap condition caches by which style LoRA is active - then picking by LoRA name is genuinely less error-prone than remembering which arbitrary .ckpt you saved.

Install

Part of lrzjason/ComfyUI-EditUtils - install the pack once (Manager → search "ComfyUI-EditUtils", or clone into custom_nodes and restart), and the node appears under advanced/conditioning. No pip dependencies, no bundled models.

Troubleshooting

The classic confusion: you see LoRA names in the dropdown and assume it's loading LoRAs. It isn't. If you pick a LoRA name that has no matching .ckpt in models/conditions/, you get an empty conditioning and a console error, so save the condition under the LoRA's exact basename first. And because the dropdown is built at graph-load time, new files won't appear until you reload the workflow or restart ComfyUI.