Load Latent MXD

If Save Latent I2V MXD is how you pause a WAN 2.2 generation mid-flight, Load Latent I2V MXD is how you unpause it. It picks a .latent file from your input/latents folder and reconstructs everything the save bundled: the latent itself, the positive and negative conditioning, and the sampler settings - steps, CFG, sampler, scheduler, shift, and end-at-step - so the second stage of your workflow runs with the exact parameters the first stage used. No reconstructing settings from memory, no drift between stages.

What comes out

The node reads the .latent safetensors file (and its .cond.pt conditioning sidecar) and returns a stack of outputs:

• samples - the latent, ready for the sampler
• positive and negative - the conditioning from the original WAN image→video encode
• steps, cfg, sampler_name, scheduler, end_at_step - the sampler configuration, restored
• shift - the SD3-style shift value this workflow uses
• filename_prefix - the base name derived from the loaded file (folder + stem), so if you save the finished result it lands with a sensible name

You wire those into a KSampler-Advanced-style node and a save, and you're continuing the run rather than restarting it. The input is just latent - a dropdown of every .latent file in input/latents.

How it fits the two-stage pattern

This is the finishing stage of the workflow the save node starts: run stage one, save the high-noise latent, then come back - maybe after a reboot, maybe with a different upscale branch - load it here, and finish the low-noise pass. Because the workflow graph itself is embedded in the file, dragging the finished video back into ComfyUI can reconstruct the whole two-stage setup on one canvas. The pair is built for the "save your place in an expensive generation" problem that long WAN 2.2 runs make painfully real.

Gotchas

• Keep .latent and .cond.pt together in the same folder. The loader needs the sidecar for conditioning; split them and you lose the settings that make the resume seamless.
• Files must live under ComfyUI/input/latents - that's where the dropdown scans, recursively by folder.
• It's built for WAN 2.2's latent format and the pack's save convention. It'll load other .latent files, but the settings reconstruction is tuned for this pack's pipeline.

Install

ComfyUI Manager → search Maxed Out → install → restart, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Maxed-Out-99/ComfyUI-MaxedOut

No requirements.txt, no model downloads. Under MXD/Latents (I2V). If you've ever re-run a long generation from scratch just because you didn't want to redo the setup, this is the node that makes "resume later" a real option.