RTX Remix Layer Type

Layer types are the vocabulary of RTX Remix projects: capture, replacement, workfile, and so on. When you're building a REST API workflow that creates or filters layers, you need those exact strings - and RTX Remix Layer Type is the dropdown that hands them to you without the typing. One selection, two outputs, no fuss.

The node is a glorified, validated constant. You get a combo box with the six supported options - autoupscale, capture_baker, capture, replacement, workfile, and None - pick one, and it flows out as a STRING you can wire into RTX Remix Create Layer (as its layer_type), RTX Remix Get Layers (as part of the type filter), or anywhere else a type is expected.

The validation is the part that earns its keep. When it executes, it asks the running Toolkit for its supported layer types (GET /stagecraft/layers/types) and errors if you've selected something invalid - which basically can't happen with the dropdown, but it's a nice safety net if the Toolkit's list ever changes between releases. Like the pack's texture-type counterpart, it's the "write it right the first time" insurance.

Inputs:

• layer_type (enum) - the six-option dropdown.
• context (RTXRemixContext) - threaded from your start node.
• enable_this_node (BOOLEAN) - the standard bypass; off returns an empty string.

Outputs:

• context - passed through.
• layer_type (STRING) - your selection, ready to feed downstream.

Useful pairing: since it passes context through untouched, you can string several of these (or mix them with RTX Remix Layer Types, the multi-select sibling) into a single chain without breaking execution order. Build a "which types do I care about today" section at the top of your graph, then feed the results into Get Layers or Create Layer below.

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). For the validation call to succeed, the Toolkit must be running with a project open - though if you only need the string constant and don't care about validation, keep in mind the node does hit the live API, so no Toolkit means an error.

Where people get burned: None is a real, selectable option here - it's the Toolkit's way of saying "no type / untyped layer," not a bug in the dropdown. And don't confuse the layer-type list with the texture-type list from the RTX Remix Texture Type node; different domain, same "dropdown that validates" pattern. Mixing them up is a classic "why is Create Layer rejecting this" moment.