RTX Remix String Concatenate
Join two strings with a separator, and don't think about it again
- STRING
RTX Remix String Concatenate does exactly one thing: string1 + separator + string2, and hands you the result. It's the pack's most boring node, which is precisely why it's useful. In RTX Remix workflows you're constantly building strings - texture names, layer paths, output directories - and this is the tiny glue node that assembles them without you hand-typing the whole thing.
The detail that makes it worth reaching for over a plain text box is the separator. Default is _, so "wooden" + "crate" becomes wooden_crate - which, as it happens, is a very texture-name-shaped output. Change the separator to / and it becomes a path builder; set it to empty and it's a plain join. One node, three joining styles, all by editing a string.
Inputs:
string1(STRING) - first part. Empty by default.string2(STRING) - second part. Empty by default.separator(STRING, optional) - the glue between them. Defaults to_.
Output:
STRING- the joined result.
It's pure logic - no context, no Toolkit call, no enable_this_node. Like the pack's RTX Remix Invert Bool, it works in any workflow, REST API or not. The pack even ships a standalone RTX Remix String Constant for the parts you want as fixed values, so the canonical pattern is: constants and concats building names at the top of your graph, feeding into layer and texture operations below. You can chain concats (concatenate the output of one into the next) to build longer strings, though the two-input design means long chains get tall fast - that's what the separator and a couple of stages are for.
Install: part of NVIDIAGameWorks/ComfyUI-RTX-Remix, NVIDIA's official pack. ComfyUI Manager (search "RTX Remix") or:
cd ComfyUI/custom_nodes
git clone https://github.com/NVIDIAGameWorks/ComfyUI-RTX-Remix
# restart ComfyUI
Needs ComfyUI v0.3.48+ (V3 schema); no Toolkit or special dependencies for the node itself.
Where people get burned: whitespace and missing separators. If string1 has a trailing space and you're using _ as the separator, you get wooden _crate - subtly broken, and a whole class of "why won't the Toolkit find this path" bugs. Decide on your separator once and be consistent. Also, remember it's a two-input concat, not an n-input one; when you need three parts, chain two of them and double-check you didn't lose a separator along the way.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| string1 | STRING | — | |
| string2 | STRING | — | |
| separatoropt | STRING | _ | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| STRING | STRING | — |