Save 4 hours! We auto-setup your workflow! Free!

Drop your workflow.json — we handle every dependency, custom node, and model. Just open the link and run.

Auto-Setup Workflow Json (Free) Now!
ComfyUI > Nodes > ComfyUI-RH-DLSS5

ComfyUI Extension: ComfyUI-RH-DLSS5

Repo Name

ComfyUI-RH-DLSS5

Author
RH-RunningHub (Account age: 210 days)
Nodes
View all nodes(1)
Latest Updated
2026-11-11
Github Stars
0.05K

How to Install ComfyUI-RH-DLSS5

Install this extension via the ComfyUI Manager by searching for ComfyUI-RH-DLSS5
  • 1. Click the Manager button in the main menu
  • 2. Select Custom Nodes Manager button
  • 3. Enter ComfyUI-RH-DLSS5 in the search bar
After installation, click the Restart button to restart ComfyUI. Then, manually refresh your browser to clear the cache and access the updated list of nodes.

Visit ComfyUI Online for ready-to-use ComfyUI environment

  • Free trial available
  • 16GB VRAM to 80GB VRAM GPU machines
  • 400+ preloaded models/nodes
  • Freedom to upload custom models/nodes
  • 200+ ready-to-run workflows
  • 100% private workspace with up to 200GB storage
  • Dedicated Support

Run ComfyUI Online

ComfyUI-RH-DLSS5 Description

ComfyUI-RH-DLSS5 integrates NVIDIA DLSS neural rendering, image and video upscaling, and AI frame interpolation into ComfyUI to enhance detail, boost resolution, and create smoother motion.

ComfyUI-RH-DLSS5 Introduction

ComfyUI-RH-DLSS5 brings NVIDIA DLSS Neural Rendering, optional upscaling, and frame generation into your ComfyUI workflows. You can use it to refine images, process video frames, increase resolution, or create smoother motion by adding AI-generated frames between existing ones.

The extension provides two nodes:

NodeMain purposeWhere to find it
RH DLSS5 Enhance (NR / Upscale) — RH_DLSS5EnhanceApply neural enhancement at the original resolution or enlarge images and video framesimage/upscaling
RH DLSS5 Frame Interpolation — RH_DLSS5FrameInterpolationIncrease a sequence’s frame rate using NVIDIA DLSS frame generationvideo

What you can use it for

  • Refine AI-generated artwork: adjust local contrast and reconstructed detail, including skin and material structure.
  • Clean up generated video: use neural enhancement to reduce noise or compression artifacts while controlling how much texture remains.
  • Create larger deliverables: choose a fixed enlargement factor or a resolution target such as 2K or 4K.
  • Make animation look smoother: turn a 24 fps clip into a 48 fps clip with 2x frame interpolation, for example.
  • Keep processing inside ComfyUI: use standard IMAGE and VIDEO connections rather than a separate online service.
  • Preserve sound where supported: retain source audio or provide replacement audio to the frame-interpolation node.

The extension calls NVIDIA’s native NGX runtime. It does not imitate DLSS with a look-alike filter, and it does not send your frames to an HTTP processing service.

Compatibility at a glance

  • GPU: a compatible NVIDIA RTX GPU and NVIDIA runtime build are required. Compatibility depends on the combination of GPU, driver, and runtime—not just the RTX name.
  • Windows: Windows 10/11 x64. The enhancement node uses an in-process D3D12 bridge.
  • Linux: uses Windows native workers through Wine, together with DXVK, vkd3d-proton, and DXVK-NVAPI.
  • ComfyUI: native video workflows need a build with VIDEO, LoadVideo, and SaveVideo support. Image workflows use the standard IMAGE type.

The author reports end-to-end Linux testing on an RTX 4090. See the models and verification sections for the distinction between tested configurations and runtime-dependent support.

How ComfyUI-RH-DLSS5 Works

The two nodes solve different problems: enhancement changes the appearance or size of frames; interpolation adds frames to the timeline.

Neural enhancement: refining what is already in the frame

Think of enhancement as a finishing pass. You provide an image, and NVIDIA’s neural renderer reconstructs its appearance using the available visual information.

In a game, neural rendering can receive additional information about geometry, lighting, and materials. Ordinary images and videos do not contain those engine buffers. Here, the renderer works from your frames and motion guidance estimated from the footage.

That distinction matters: this is not the same as supplying a complete 3D scene. You should judge the result as a reconstruction based on the source, not as a guaranteed recovery of the original physical lighting or missing details.

The enhancement pipeline is:

Image or video frames
    → Frame preparation and motion guidance
    → Optional DLSS Super Resolution enlargement
    → DLSS Neural Rendering
    → Processed IMAGE or VIDEO
  • At 1x, neural enhancement runs at the original dimensions.
  • Above 1x, ordinary DLSS Super Resolution first supplies the enlarged image. Neural Rendering then processes that higher-resolution surface.

For example, a 480 × 736 portrait processed at 2x becomes 960 × 1472.

Motion guidance: telling the renderer what moved

Optical flow estimates how visible objects move between neighboring frames. Imagine drawing small arrows over the picture: each arrow indicates where a patch of the image moved.

These arrows help processing follow a coherent sequence rather than treating every frame as unrelated.

  • For a still image, zero motion is appropriate.
  • For a video sequence, estimated motion provides temporal guidance.
  • For unrelated images in one batch, use still images so each image starts fresh.

Scene cuts: clearing the visual memory

When a clip cuts from one shot to another, information from the previous shot should not influence the new one. The extension resets its temporal history at detected scene changes.

The enhancement node also treats implausible flow—such as unreliable estimates during fast movement or noisy footage—as a reason to reset history, helping prevent accumulated ghosting.

Frame interpolation: drawing the moments between frames

Interpolation creates new images between existing frames rather than blending two pictures together.

At 2x, a sequence can be thought of like this:

Original:       A         B         C
Interpolated:   A    AB   B    BC   C

AB and BC are generated intermediate frames.

For a continuous sequence with T source frames, the documented 2x path produces 2T − 1 frames at exactly twice the source frame rate. It does not invent an additional interval beyond the last source frame. Generated frames are skipped across detected scene cuts.

The 3x and 4x modes use cascaded processing, so they require more work than 2x.

Streaming: why VIDEO inputs matter for longer clips

For frame interpolation, a VIDEO input follows a streaming path: output frames go directly into the video encoder instead of accumulating as one full-length floating-point image batch.

This keeps host-memory use bounded with respect to clip length, though actual memory requirements still depend on resolution, decoding, and the chosen multiplier.

An IMAGE batch returns all output images in memory. That is useful for further image processing, but it can be much more demanding for long sequences.

ComfyUI-RH-DLSS5 Features

Enhance images and videos with one node

RH_DLSS5Enhance accepts image, video, or both.

ConnectionWhat it provides
image inputA still image or an ordered batch of images
video inputA native ComfyUI video, processed in playback order
images outputProcessed images when an image input was supplied
video outputProcessed video when a video input was supplied
status outputA short summary of frame counts, dimensions, backend, channel order, and output notes

Connect images to SaveImage and video to SaveVideo.

Choose native enhancement or upscaling

upscaling_modeWhat it doesExample use
1x (DLAA)Enhances without increasing dimensionsFinish an image already at delivery size
1.5xMultiplies width and height by 1.5A moderate enlargement
1.724xUses NVIDIA’s balanced scaling factorAn intermediate choice between 1.5x and 2x
2xDoubles width and heightTurn 960 × 540 into 1920 × 1080
3xTriples width and heightA larger enlargement from a smaller source
1K / 2K / 4K / 8KAutomatically resolves the scale needed for a target resolution bucketChoose a delivery target rather than a manual factor

The automatic buckets use these short-edge targets:

BucketTarget short edgeDocumented 16:9 output
1K1080 pixels1920 × 1080
2K1440 pixels2560 × 1440
4K2160 pixels3840 × 2160
8K4320 pixels7680 × 4320

The extension preserves aspect ratio and selects the smallest supported factor that reaches the target. An input already at or above the bucket stays at 1x; the node does not downscale it.

A request fails with an explanatory error if the target cannot be reached within 3x or would exceed the documented 7680 × 4320 output envelope.

A scaling factor applies to both dimensions. A 3x enlargement contains approximately nine times as many pixels per frame, which can substantially increase processing and memory requirements.

Control the enhancement look

These controls map to NVIDIA’s DLSS Neural Rendering properties. Their exact effect can vary with the supplied runtime.

ControlRange or choicesHow to use it
styledefault, natural, cinematic, off (bypass NR)Select an overall style profile, or bypass all processing
intensity0.0–2.0; default 1.0Overall neural-pass strength. Lower values blend toward the source; values above 1.0 usually add no further effect
tone0.0–2.0; default 1.0Higher values increase local contrast; lower values produce a flatter appearance
structure0.0–2.0; default 1.5Higher values emphasize reconstructed detail and texture; lower values give a softer, cleaner result
skin−1.0–2.0; default 2.0Skin-specific structure strength; −1 leaves the decision to the model
auto_maskon / off; default onLets the runtime identify skin regions and apply skin there
presetInteger 0–9; default 0Internal rendering hint. Keep 0 unless your runtime documentation defines another value

Important: skin only has an effect when auto_mask=on.

style=off is a complete bypass, not an “upscale without enhancement” mode. Image batches are returned unchanged, and file-backed videos pass through without decoding or re-encoding.

Suggested starting points

Your goalStarting settingsWhat to inspect
Clean up generated videointensity=1.0, default structureRaise structure if detail disappears; lower it if noise remains
Refine a portraitauto_mask=on, skin=2.0Check skin texture alongside hair, clothing, and background detail
Reduce an over-processed lookLower structure firstIf still too strong, reduce intensity
Add local contrastIncrease tone graduallyWatch shadow detail and bright areas
Finish at the existing size1x (DLAA)Compare texture and tone without a resolution change

Change one setting at a time on the same image or short clip. This makes it easier to tell whether an improvement comes from structure, tone, or overall intensity.

Manage motion and frame relationships

ControlOptionsPurpose
motionauto, optical_flow, noneauto uses optical flow when OpenCV is available; none supplies zero motion
scene_change_thresholdFloating-point thresholdControls optical-flow-based scene-cut history resets
batch_modetemporal sequence, still imagesKeep history for a coherent sequence, or reset it for every independent image
warmup_framesIntegerReports a warm-up budget to the worker; 0 is a valid starting point
keep_audioOn/offRetains original audio in video output where supported

Keep video frames in playback order. A batch is interpreted as a sequence, not as a collection to be automatically sorted.

Increase frame rate with DLSS frame generation

RH_DLSS5FrameInterpolation accepts either a video or an ordered image batch.

ControlOptions or behavior
output_fps1x, 2x, 3x, 4x, or exact target-rate presets spanning 23.976–144 fps
motionauto uses hardware NVOFA when available, otherwise OpenCV DIS; nvof or dis forces a guide
scene_change_threshold0.01–1.0, default 0.24; higher values cause fewer scene-cut resets
keep_audioDefault on; off removes audio during processing
audioOptional replacement audio for video, or an audio source for image-batch inputs

For exact target rates, the node builds the smallest suitable 2x / 4x / 8x dense grid and selects frames for the requested timeline without duplicating frames. The target must be higher than the source rate and no more than 6x the source rate.

Examples:

  • 24 → 48 fps: choose 2x, the author’s recommended starting point.
  • 24 → 72 fps: choose 3x.
  • 24 → 60 fps: choose the exact 60 fps target.
  • No interpolation: choose 1x.

1x is a true passthrough: it does not interpolate or re-encode. It ignores motion and audio-processing options and keeps the source audio.

Understand interpolation inputs and outputs

Input typeTiming and audioOutputs
VIDEOUses source frame rate and source audio, unless replacement audio is suppliedStreaming-encoded video; images is None
IMAGE batchAssumes a 24 fps source; attach sound through audioFull images batch plus an in-memory video object

When possible, source-file audio is stream-copied without re-encoding. Replacement audio or audio without a usable source file is encoded to AAC when needed.

Advanced runtime and backend controls

Most workflows can leave these controls at their defaults.

ControlPurpose
backendEnhancement node: auto, linux-wine, or windows-bridge
channel_orderEnhancement node: automatic color-order detection, with manual RGBA or BGRA overrides
runtime_dirOverrides the runtime folder for the selected node
wine_prefixOverrides the Wine environment used on Linux

The enhancement runtime lookup is:

runtime_dir
    → DLSS5_RUNTIME_DIR
    → ComfyUI/models/dlss5
    → extension runtime/ fallback

The interpolation runtime lookup is:

runtime_dir
    → DLSS5_FG_RUNTIME_DIR
    → ComfyUI/models/dlss5/dlssg
    → extension runtime/dlssg fallback

For managed or multi-GPU systems, the extension resolves CUDA_VISIBLE_DEVICES and attempts to keep Wine workers on the assigned GPU. Advanced overrides include DLSS5_GPU_INDEX, DLSS5_WINE, and DLSS5_WINEPREFIX. These are troubleshooting controls rather than artistic settings.

Queueing and caching

Each run starts with fresh processing state, so temporal history is not intended to leak from one queued job into another.

  • Linux launches a Wine worker for each execution, with execution serialized by an internal lock.
  • Windows enhancement reuses a bridge session on the same GPU when dimensions and settings match.
  • Identical work may be served from ComfyUI’s cache, based on settings and input probes or video metadata.

Re-queueing the same workflow therefore does not necessarily start another render.

ComfyUI-RH-DLSS5 Models and Runtime Components

This extension does not offer a collection of artist-selectable checkpoint models. It uses NVIDIA runtime libraries, with optional GPU-specific Neural Rendering builds selected automatically.

What each component does

ComponentRoleWhen it is needed
nvngx_dlssnr.dllDLSS Neural Rendering, NGX feature 18Required for enhancement
nvngx_dlssnr_rtx30.dllOptional RTX 30-lineage Neural Rendering buildPreferred automatically on RTX 30 GPUs when present
nvngx_dlssnr_rtx40.dllOptional RTX 40-lineage Neural Rendering buildPreferred automatically on RTX 40 GPUs when present
nvngx_dlss.dllDLSS Super Resolution carrierEnhancement modes above 1x
_nvngx.dllNVIDIA NGX core loaderRuntime infrastructure
nvngx_dlssg.dllDLSS frame generationFrame interpolation
dlssg-worker.exeNative host that drives frame generationFrame interpolation
nvngx.dll in dlssg/NGX SDK loader stubFrame interpolation

These files are not interchangeable. For example, renaming nvngx_dlss.dll to _nvngx.dll does not replace the NGX loader.

Automatic GPU-specific selection

GPU familySelection orderVerification reported by the author
RTX 30 / AmpereRTX 30 build → RTX 40 build → universal buildNot yet tested
RTX 40 / AdaRTX 40 build → universal buildRTX 4090 tested
RTX 50 / RTX 6000D, SM120Universal buildRTX 6000D tested

The documentation describes a universal build covering RTX 20 through RTX 50, but does not establish verified RTX 20 operation. Stock SDK builds may have narrower support, including RTX 50-only builds. Treat support as specific to the runtime you are authorized to use.

For advanced diagnostics, DLSS5NR_SNR_FILENAME can override automatic selection with a plain runtime filename.

Related projects expose controls such as model presets J / K / L / M, dedicated encoding options, or separate settings nodes. Those are not documented controls of ComfyUI-RH-DLSS5.

Likewise, runtime-download scripts and bundled-runtime behavior described by other projects should not be assumed to apply here. This extension does not download or redistribute NVIDIA runtime libraries or the frame-generation worker.

Use only runtime files you are legally entitled to use. See runtime/README.txt for component details and the official NVIDIA DLSS releases for publicly available SDK releases.

ComfyUI-RH-DLSS5 Workflows and Examples

Enhance a still image

LoadImage
    → RH DLSS5 Enhance (NR / Upscale)
    → SaveImage
  1. Connect the image to image.
  2. Start with 1x (DLAA) to evaluate enhancement separately from enlargement.
  3. Use still images for independent artwork.
  4. Adjust structure, skin, or intensity after comparing against the source.
  5. Select an upscaling factor if you need a larger result.

Example: image API workflow.

Enhance a video

LoadVideo
    → RH DLSS5 Enhance (NR / Upscale)
    → SaveVideo
  1. Connect the source to video.
  2. Use temporal sequence.
  3. Start with automatic motion guidance.
  4. Keep audio enabled if the result should retain sound.
  5. Connect the video output to SaveVideo.

Example: video enhancement API workflow.

Make motion smoother

LoadVideo
    → RH DLSS5 Frame Interpolation
    → SaveVideo
  1. Begin with output_fps=2x.
  2. Leave motion=auto.
  3. Review fast motion, object boundaries, and scene transitions.
  4. Move to 3x, 4x, or an exact target only when the additional smoothness is useful.

Example: frame-interpolation API workflow.

The supplied examples are API-format JSON workflows. Replace their placeholder media names before submitting them through a compatible workflow interface.

ComfyUI-RH-DLSS5 Current Improvements and Verification

The supplied documentation does not include a numbered release history. The following are documented improvements and checks, rather than an invented version-by-version changelog.

Streaming frame interpolation

VIDEO interpolation now sends generated frames directly to an FFmpeg video encoder instead of constructing a full-length floating-point output batch.

Why this matters:

  • Longer clips no longer require output memory to grow as one complete floating-point sequence.
  • 2x avoids an intermediate generated-frame grid buffer.
  • 3x / 4x retain one compact 8-bit grid buffer between cascade stages.
  • Original audio can be stream-copied from the source.

The author reports a 400-frame, 1080p, 2x test completing at roughly 20 GB peak host RAM. The earlier non-streaming implementation was terminated by the memory limit on the same clip. This is a specific measurement, not a general memory guarantee.

Linux execution and recovery handling

Documented behavior includes:

  • Automatic management of a shared virtual display on headless systems.
  • Handling of stale display locks left by interrupted workers.
  • Wine-prefix validation with actionable errors.
  • GPU selection intended to respect scheduler-assigned devices.

These changes help reduce failures on servers and shared multi-GPU systems.

Reported verification

The author reports:

  • Enhancement at 1x and 1.5x on a 48-frame, 320 × 240 test clip.
  • Linux testing with Ubuntu 22.04, Wine 11.0, DXVK 3.1, vkd3d-proton 3.0.1, and DXVK-NVAPI.
  • RTX 4090 testing with driver 580.95.05 and DLSSNR 310.8.
  • A fresh Ubuntu 22.04 container validation in September 2026.
  • Frame-interpolation checks for 2x / 3x / 4x, source-frame alignment, NVOFA and DIS guidance, and audio stream-copy.

The Windows enhancement bridge follows the same protocol as the referenced native integration; the detailed end-to-end verification above was reported for Linux.

Troubleshooting ComfyUI-RH-DLSS5

Start with a small, simple test

Before changing advanced runtime settings:

  1. Use one image or a short clip.
  2. Choose 1x (DLAA) for enhancement or 2x for interpolation.
  3. Leave backend and channel order on auto.
  4. Read the node’s status output.
  5. Inspect ComfyUI’s console for the complete error message.

Record the GPU, driver, selected runtime, dimensions, and settings when comparing failures.

The result looks too soft, artificial, or over-processed

  1. Compare at the same display size.
  2. If detail is disappearing, raise structure gradually.
  3. If the result looks plasticky or overly reconstructed, lower structure.
  4. If the overall effect is still too strong, lower intensity.
  5. For portraits, confirm auto_mask=on before evaluating skin.

Increasing intensity above 1.0 is usually not a way to recover more detail.

Skin settings appear to do nothing

  1. Turn auto_mask on.
  2. Confirm that the image contains visible skin regions.
  3. Compare two skin-strength settings on the same source.
  4. Keep other settings unchanged during the comparison.

With automatic masking off, the documented skin-strength control is inactive.

Red and blue appear swapped

  1. Leave channel_order=auto for the initial test.
  2. If colors remain wrong, try RGBA.
  3. If necessary, try BGRA.
  4. Compare against the source and keep the correct setting.

This override handles runtime builds that expose different red/blue channel ordering.

The requested resolution fails

  1. Check the input dimensions and selected factor.
  2. Try a lower fixed factor.
  3. For an automatic bucket, check whether reaching its short edge would require more than 3x.
  4. Check whether the output would exceed the documented size envelope.

An automatic bucket does not downscale an oversized source.

Video shows ghosting or influence from another image

  1. Confirm that frames are in playback order.
  2. Use temporal sequence only for one coherent sequence.
  3. Use still images for unrelated artwork in a batch.
  4. Check motion guidance and scene-cut settings.
  5. For interpolation, lower the scene-change threshold if real cuts are not being detected; higher thresholds produce fewer resets.

A runtime file cannot be found

  1. Read the error to identify the missing component.
  2. Check the selected node’s runtime_dir.
  3. Check whether an environment override points to an old folder.
  4. Verify that the required files are present and correctly named.
  5. Consult runtime/README.txt.

Enhancement and interpolation use different runtime folders. A working enhancement runtime does not by itself provide frame-generation support.

Feature creation fails with 0xBAD00001

This can indicate that the runtime rejects the selected GPU/driver combination. On headless Linux systems, it can also result from GPU identification failure.

  1. Confirm that the selected runtime supports your GPU.
  2. Check the NVIDIA driver.
  3. On Linux, look for Failed to get NvPhysicalGpuHandle for LUID.
  4. If that message appears on a machine without an active display output, review DXVK-NVAPI compatibility.

The documented headless issue involves DXVK-NVAPI versions up to 0.9.2 and an invalid Vulkan device LUID. A build with a DXGI adapter-LUID fallback, or a suitable virtual display/Xorg configuration with a connected output, is the documented remedy.

Interpolation returns no images

For a VIDEO input, this is expected.

  1. Connect the node’s video output to SaveVideo.
  2. Use an IMAGE batch input only if you need the entire interpolated image batch in memory.

Audio is missing or was not replaced

  1. Check keep_audio.
  2. Confirm that the source video contains audio.
  3. For image batches, connect an AUDIO input.
  4. For replacement sound, connect audio and leave keep_audio on.
  5. Check whether output_fps=1x: passthrough keeps the original video unchanged and ignores audio-processing options.

Memory use is too high

  1. Prefer the VIDEO input for long interpolation jobs.
  2. Try 2x before 3x or 4x.
  3. Test at a smaller resolution.
  4. Avoid returning a long sequence as a full IMAGE batch unless necessary.

Streaming reduces accumulation of output frames; it does not eliminate decoding buffers or other memory costs.

Linux-specific failures

SymptomWhat to check next
failed to load l_intl.nls during Wine initializationWine’s shared data files are incomplete; have the environment maintainer check the Wine installation
Only llvmpipe appearsWithout DISPLAY, this can be normal. Verify NVIDIA visibility with a valid display environment
ERROR_OUT_OF_HOST_MEMORY from vulkaninfoCheck for a broken or empty nvidia_icd.json; Vulkan loader diagnostics can identify a JSON parsing failure
vr -3 or VK_ERROR_INITIALIZATION_FAILEDCheck for incomplete NVIDIA driver libraries, especially libnvidia-rtcore in containers
Could not create a D3D12 deviceCheck Vulkan operation and DISPLAY before investigating the node
A run hangs and subsequent retries also hangAn orphaned Wine worker or server may still hold GPU resources or pipes

Do not wrap ComfyUI’s worker execution in xvfb-run. The author documents that it can leak logs into the binary frame stream; the node manages its own virtual display.

For a hung Linux environment, an experienced operator can stop leftover processes before retrying:

pkill -f 'dlss5nr_hos[t]'
pkill -x wineserver
pkill -x Xvfb

Caution: these commands can affect other Wine or virtual-display workloads under the same user. On shared systems, ask the environment maintainer to isolate and stop only the affected processes.

Frequently asked questions

Does interpolation make a clip play in slow motion?
The multiplier modes increase the output frame rate along with the frame count. They are intended to improve smoothness, not automatically turn the clip into slow motion.

Why does 2x not always mean exactly twice as many frames?
The documented continuous-sequence count is 2T − 1: there is no future source frame after the last frame. Scene cuts also skip generated frames for the affected intervals.

Can I process unrelated images together?
Yes. Use the enhancement node’s still images batch mode to reset history for every image.

Does style=off keep upscaling active?
No. It bypasses all processing.

Can I use an exact target frame rate below the source rate?
No. Exact interpolation targets must exceed the source rate and remain within 6x.

Why did re-queueing not start processing again?
ComfyUI may reuse a cached result for identical settings and inputs. Change a relevant input or setting when you actually need a new evaluation.

Does the extension save the final result automatically?
Use SaveImage or SaveVideo in your workflow to save the output. The interpolation VIDEO path uses a streaming-encoded temporary video.

Learn More about ComfyUI-RH-DLSS5

Practical starting resources

NVIDIA documentation

These projects provide implementation background. Their node names, runtime packaging, settings, and troubleshooting procedures are not necessarily interchangeable with this extension.

Linux compatibility resources

Use these when the failure concerns graphics translation, Wine, or GPU discovery rather than an artistic setting.

ComfyUI-RH-DLSS5 License and Attribution

The extension’s Python code and project-owned native components are licensed under MIT. See LICENSE.

The native bridge and host derive from the MIT-licensed reference integrations linked above. The frame-generation pipeline also draws on the referenced worker protocol and scheduling designs.

NVIDIA NGX/DLSS runtime binaries are proprietary NVIDIA software, not covered by the extension’s MIT license. They are not included, downloaded, or redistributed by this plugin. The frame-generation worker is also user-supplied.

Use only components you are authorized to use and follow their applicable license terms. DLSS and NGX are NVIDIA trademarks.

ComfyUI-RH-DLSS5 Related Nodes

RunComfy
Copyright 2025 RunComfy. All Rights Reserved.

RunComfy is the premier ComfyUI platform, offering ComfyUI online environment and services, along with ComfyUI workflows featuring stunning visuals. RunComfy also provides AI Models, enabling artists to harness the latest AI tools to create incredible art.

ComfyUI-RH-DLSS5 detailed guide | ComfyUI