RTX Remix String Constant

Every node in this pack's REST API family wears a 🌐 prefix, which strongly suggests they all talk to the RTX Remix Toolkit over the network. RTX Remix String Constant doesn't. It's a plain multiline text box that emits exactly what you typed, untouched, no HTTP call, no key, no hidden model. The globe is inherited from the menu namespace, not from behavior. Once you know that, this is the most boring and most useful node in the pack.

Where this fits

This pack is NVIDIA GameWorks' official bridge between ComfyUI and the RTX Remix Toolkit - NVIDIA's tool for remastering old DirectX 8/9 games with path tracing, where AI upscaling and PBR generation happen in ComfyUI. It has two personalities: integration workflows (the toolkit drives ComfyUI - the recommended route) and REST API workflows (ComfyUI drives the toolkit - advanced). This node lives on the REST API side, under RTX Remix > REST API > common. If you only ever run integration workflows, you'll never touch it, and that's fine. If you're building a REST workflow, you'll want several of these.

What it actually does

In a REST workflow you're assembling layer ids, texture paths, asset names, edit targets, and prompts that get threaded through nodes like RTX Remix Get Textures, Set Texture, Create Layer, and Ingest Texture. Most of those are fixed strings - and the whole point of this node is that you declare them once instead of retyping them at every connection point. It's the same instinct as rgthree's primitives: keep the "here are the values" part of the graph readable, separate from the "here's what happens" part.

The mechanism is a zero-compute pass-through. The class takes string and returns it. No validation, no formatting, no side effects. That's the entire contract.

Inputs and outputs

There's exactly one input and one output, which is refreshing.

• string (STRING, multiline, default empty) - the text you want to reuse. The multiline flag is a small blessing; paste a long path or a chunk of a JSON payload without fighting a single-line box.
• string (STRING) - the same text, emitted for wiring into any STRING slot downstream.

If you need two different values, add two nodes. If you need to build a name from parts, the pack's sibling RTX Remix String Concatenate joins two strings with a separator, so you can keep a base path in one constant and swap the tail in another.

Installing the pack

In ComfyUI Manager, search "RTX Remix" (or comfyui-rtx_remix), hit Install, and restart. Or go manual:

cd ComfyUI/custom_nodes
git clone https://github.com/NVIDIAGameWorks/ComfyUI-RTX-Remix
cd ComfyUI-RTX-Remix
./install.sh   # install.bat on Windows

Then restart ComfyUI. The pack needs ComfyUI v0.3.48+ - it uses the newer V3 node schema (comfy_api.latest), so an old install just won't load it. The installer pulls huggingface-hub, numpy, OpenEXR, pillow, a pinned pydantic, requests, and torch. Manager handles all of that; the manual route runs the same requirements file.

Gotchas and troubleshooting

The one trap is expectation management. Because it wears the 🌐 globe, beginners assume the toolkit must be running for this node to work. It doesn't - this node works offline, and it's actually the only family member that reliably will. If your workflow runs fine up to this node and dies later, the problem is a node that does call the API (texture, layer, or project nodes), or the context chain: the REST nodes order themselves by threading a context wire from RTX Remix Start Context through to RTX Remix End Context, so a missing context hop stops the whole graph.

Also worth knowing up front: the README labels the toolkit integration a work in progress, and REST workflows in particular are pitched squarely at advanced users. This node is the easy part.