Load UNET

Every model has a counterpart, and this is the counterpart to UNET Selector. Where the selector just records which UNET you picked - no loading, no VRAM, just a description - Load UNET is the one that actually pulls the weights off disk and hands you a real MODEL ready for the KSampler. It's the loader half of Sage Utils' pick-first-load-later split, and understanding that split is the whole key to the pack.

The single required input is unet_info, the MODEL_INFO output you get from UNET Selector (or from a checkpoint-style loader like Load Diffusion Model w/ Metadata). One output, model, which wires straight into your sampler. If you've used the selector to set a weight dtype, this is where it takes effect: the code expands into a core UNETLoader node and lets it do the real work, honoring the dtype you picked - default fp16-style behavior, or the fp8 variants (fp8_e4m3fn, fp8_e4m3fn_fast, fp8_e5m2) if that's what fits your card. It also tracks model timestamps in the pack's cache so its metadata reporting stays honest about what you actually loaded.

That "expands into a core loader" detail is worth appreciating: the node isn't a reimplementation of UNET loading. It builds the standard ComfyUI loader under the hood at execution time, so you get core behavior with the pack's metadata handling layered on. Which means no weird edge cases - if the core UNETLoader works on your setup, this does too. If unet_info is somehow empty or malformed, you get a clear error ("Failed to create UNET node from unet_info") instead of a silent nothing.

The workflow shape it fits: UNET Selector → Load UNET → KSampler, optionally with a Load UNET + LoRA (Model Only) node in between if you want LoRAs applied on the way in. Keep in mind the selector's weight_dtype choice only makes sense at this point - pick your dtype when you choose the file, and this loader obeys it.

Install is the pack standard - ComfyUI Manager (search "Sage Utils") or:

cd ComfyUI/custom_nodes
git clone https://github.com/arcum42/ComfyUI_SageUtils.git

then restart. This node downloads no models; it just needs the files you've already placed in models/unet (or wherever your UNETs live), which the selector's dropdown already reflects. If the dropdown is empty, that's a file-location problem, not a node problem.