RTX Remix Get Edit Target

RTX Remix works on the concept of an edit target: the single layer that receives your modifications at any moment. Change the target and your next texture replacement or material edit lands on a different layer. Most of the time you're setting that target deliberately - but sometimes you need to know what it currently is, and that's exactly what RTX Remix Get Edit Target is for.

It's a read node, the live-question cousin of the pack's Set Edit Target. It does one GET /stagecraft/layers/target call against the running Toolkit and returns the current target's layer ID as a string. That's the whole operation, and it's genuinely useful in a few spots:

• Introspection in branching logic. Before you mutate something, check whether the edit target is the layer you expect. If it isn't, set it - via a Switch feeding Set Edit Target - rather than assuming.
• Storing the target for later. Grab the target at the start of a workflow, do a bunch of work that changes the target, then restore it at the end so you leave the project the way you found it. This is the kind of tidy-up that separates a scripted pipeline from a one-off hack.

Inputs:

• context (RTXRemixContext) - the connection info threaded from RTX Remix Start Context.
• enable_this_node (BOOLEAN) - the standard bypass; off returns an empty string.

Outputs:

• context - passed through.
• layer_id (STRING) - the current edit target's layer ID.

One behavior worth knowing: like the other "read the live project" nodes, this one always re-executes - it explicitly tells ComfyUI not to cache its result. Because the edit target can change in the Toolkit UI between runs without any ComfyUI input changing, a cached answer would be a stale one. Every execution is a fresh query.

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) and a running RTX Remix Toolkit with a project open - the node calls the live Toolkit, so no Toolkit means an error, not an empty answer.

Where people get burned: not much to burn here, honestly - it's one of the simpler nodes in the pack. Just remember it answers the current Toolkit state. If you're setting the target elsewhere in the same workflow, make sure this node runs after the setter (context ordering handles that if you wire the context chain in order). And don't confuse it with Get Layers - that returns a list of layers matching filters; this returns the one layer that's the active edit target.