Latent Display State Info

RES4LYF's guide and unsampling features attach extra bookkeeping ("state info") to a latent as it moves through a chain - which regions were guided, what crop state is active, and similar internal tracking the pack needs to make dual-guide and unsampling workflows behave correctly. Most of the time you never see any of that; it just works in the background. Latent Display State Info is the debug window into it: feed it a latent, and it prints whatever state info is attached as a plain string, right in the UI.

This is a terminal node - it's marked as an output node, meaning it doesn't pass anything further down your graph. You use it purely to look, not to keep building on. The obvious moment to reach for it is when a guided or unsampled chain is producing results you didn't expect, and you want to confirm what RES4LYF actually thinks is happening with your latent's crop or guide state before assuming the sampler settings are the problem.

Input and output

• latent (LATENT) - required, the latent whose state info you want to inspect.
• Output: STRING - displayed in the node itself (this is an output node, so nothing continues downstream from it).

Drop it as a branch off your main chain - connect the same latent wire into it that's feeding your next real node, rather than routing your workflow through it.

Installing it

Part of the full RES4LYF pack:

• ComfyUI Manager - search "RES4LYF," install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/ClownsharkBatwing/RES4LYF, then cd RES4LYF && pip install -r requirements.txt, restart.

No extra downloads.

Common issues

The output looks empty or minimal. If your latent hasn't passed through any of RES4LYF's guide-crop or unsampling nodes, there's likely nothing meaningful attached - this isn't a sign of a broken node, it's telling you accurately that no state info exists yet at that point in the chain.

Not sure how to read what it prints. The pack doesn't document the exact format of this string anywhere public, so treat it as a diagnostic aid rather than a fully specified report - useful for spotting "something is attached here" versus "nothing is," and for comparing before/after a suspect node, rather than for parsing precise field-by-field meaning.

Used it and want to reset the state afterward. Once you've confirmed what's attached, Latent Clear State Info is the companion node for wiping it if you've decided the leftover state is the source of unexpected behavior downstream.