Glide DLSS5 (old)

Two nodes, one class, no difference in behaviour

If you went looking for Glide DLSS5 and found two of them - one plain, one labelled (old) - you're not looking at a fork or a stale build. You're looking at a compatibility shim.

The source is blunt about it: CSGlideDLSS5Legacy subclasses the real node, changes nothing, and sets DEPRECATED = True. It exists under the node id that the standalone ComfyUI-Glide-DLSS5 folder used before the author folded it into the CGlide pack, so every workflow saved against that older folder still opens instead of greeting you with a red missing-node box.

So: identical inputs, identical outputs, identical code path. The difference is purely which id it registers under, and what ComfyUI does with it.

What it does, since the code is shared

Glide DLSS5 is a front end for NVIDIA's DLSS 5 neural renderer via Blueforcer's ComfyUI-DLSS5-Enhancer pack, which this node doesn't ship a line of. Drop a video on it, scrub to a frame, press Preview and you get a before/after split of a short DLSS burst rendered up to the playhead; Queue renders the whole file through the Enhancer's own video pipeline, so the output is what that pack would have produced anyway.

The reason to want the preview at all: DLSS 5 is a real-time neural pass with a reputation for re-deciding faces, and it's closer to an interpolation method than to a generative restorer - it cleans pixels, it doesn't find detail that wasn't there. Auditioning eight frames at the playhead beats discovering the problem after a full render. The whole point of preview_frames is that DLSS accumulates across consecutive frames, so a single frame would lie to you about what it looks like inside a real run.

Same inputs as the current node: settings (a DLSS5 Settings node wired in directly, which the preview reads live), video (drop a file on the node, or a path inside ComfyUI's input, output or temp folder - nothing else is accepted), codec / container / quality, filename_prefix, copy_audio, preview_frames, and an optional output_directory. Outputs are video_path and frames.

Which one to build with

The current one: Glide DLSS5, node id CSGlideDLSS5CS, display name with no suffix.

The old one still runs, so if you load an old workflow and it works, nothing forces you to touch it. But because it's flagged deprecated, ComfyUI hides it from the node search and the add-node menu - the only way to get one is to open a workflow that already contains it. That's the entire design intent. It's a door left open for old files, not a second tool.

If you'd rather move a saved workflow onto the current node, swap it by hand and then check its widgets. ComfyUI matches saved widget values by position, so a delete-and-re-add will smear your codec, container and quality choices across whatever widget positions it finds. Re-set them, re-connect the DLSS5 Settings node, and re-drop the video file - the video value is restored on load, but a path that no longer resolves is just an error message.

Installing or fixing it

There's no separate install. Same pack, same commands:

cd ComfyUI/custom_nodes
git clone https://github.com/Blueforcer/ComfyUI-DLSS5-Enhancer
git clone https://github.com/CGlide/ComfyUI-CGlide

Restart ComfyUI, or install the CGlide pack from ComfyUI Manager by searching CGlide. Both node ids come from that one folder; nothing else needs cloning.

Two things worth doing while you're in there:

• If the old ComfyUI-Glide-DLSS5 folder is still sitting in custom_nodes, take it out. You don't want two packs registering CSGlideDLSS5.
• Update ComfyUI. The DLSS path relies on the Enhancer and its runtime; a stale ComfyUI is the usual cause of "this node used to work".

When it goes wrong

• "Missing node: CSGlideDLSS5" while loading someone else's workflow - install the CGlide pack. That id is exactly what this node is for.
• The settings input won't accept anything / no DLSS5_SETTINGS type in the list - the input type comes from the DLSS5 Enhancer pack. Install and load that first; this node reads its modules out of the running ComfyUI, so an Enhancer that's installed but failing to import produces the same symptom.
• You changed a .py file and nothing changed. A full ComfyUI restart, not a browser refresh.
• A preview that never finishes - only one preview runs at a time by design, and a second request gets refused rather than fighting the first for the GPU.
• The same error you'd get on the current node ("needs ComfyUI-DLSS5-Enhancer installed and loaded", or a version-mismatch message naming an internal module) means the engine pack, not this node. Fix that one.