DLSS 5 Runtime Status

Every node in ComfyUI-DLSS5 has a hidden dependency: a VapourKit runtime environment, NVIDIA DLLs, a config file - if any of it is missing or moved, the fancy upscaler you queued fails with an error that tells you almost nothing. This node is the pack's health check. It has zero inputs, you drop it anywhere, queue it, and it tells you in plain text whether the machinery is ready and exactly which paths it resolved to.

Run it right after setup, run it whenever a pipeline node starts failing mysteriously, and definitely run it before you post a bug report - the output is the first thing the author will ask for.

What the output means

The single STRING output starts with either READY or NOT READY. READY means every path below it resolved - the VapourSynth-capable Python interpreter, the neural-rendering wrapper (vsdlssnr.dll), the NR runtime (nvngx_dlssnr.dll), the super-resolution wrapper (vsdlssr.dll), and the SR runtime (nvngx_dlss.dll). It also reports whether both the SR and NR paths share the same Python, which matters because the pack expects one coherent runtime environment rather than two half-configured ones.

NOT READY is where the node earns its keep, because the message that follows names the exact thing that's broken. The common failure modes map cleanly:

• Missing paths or NOT READY right after setup - the extracted VapourKit directory moved or the config is stale. Rerun DLSS Runtime Setup (One Click) and re-check.
• No module named vapoursynth - you've configured plain ComfyUI Python instead of VapourKit's own VapourSynth-capable interpreter. That specific error is the pack's most common setup mistake, and this node surfaces it instantly.
• nvngx_dlssnr.dll missing - expected if you only did the Super Resolution path; the neural-render nodes need that file, which you supply yourself and no installer will fetch for you.

The two things to remember about this node

First, it's a diagnostic with no processing of its own - wire it in, read the string, and feel free to leave it out of final workflows. Second, and this is the one that gets people: redact the output before posting it anywhere. It prints machine-specific absolute paths (and your Windows username, if your ComfyUI lives under a personal folder). The README's troubleshooting section explicitly tells you to redact personal directory names before sharing Runtime Status output publicly - a screenshot of this node is a map of your disk.

Everything else is the pack's shared context: Windows + NVIDIA only, runtime installed via the one-click setup node, and the pack itself from https://github.com/HECer/ComfyUI-DLSS5. This is the node you end every install with, and the one you start every debugging session from.