RTX Remix Invert Boolean Value

Every automation toolkit eventually needs a !. RTX Remix Invert Boolean Value is exactly that: one boolean in, its opposite out. True becomes false, false becomes true. It's the pack's version of the NOT gate, and it's so trivial you might wonder why it exists - until you're mid-workflow and realize the logic you want is "run this node unless that flag is on."

That's the classic use case. The pack's REST API nodes all carry enable_this_node, a boolean that bypasses them when off. Sometimes what you want to express is "do this when the user's toggle is NOT checked." Wire the toggle into RTX Remix Invert Bool, and feed its output into the enable_this_node of whatever node should do the opposite. Suddenly a whole branch of your graph flips with one checkbox.

It's also handy for pairing with the all_layer_type_exist boolean from RTX Remix Get Layers or the File deleted output from RTX Remix Delete File - any time you want the inverse of a condition for a Switch, this is the glue.

Inputs:

• value (BOOLEAN) - the value to flip. Defaults to true.

Output:

• BOOLEAN - not value.

No context, no Toolkit call, no enable_this_node of its own - it's pure logic and it runs standalone. That's a genuine advantage: you can build and test this node in a plain ComfyUI workflow with zero RTX Remix infrastructure running. It's one of the few nodes in the pack that works in any workflow, not just REST API ones, though it lives in the RTX Remix > REST API menu alongside its siblings.

Install: part of NVIDIAGameWorks/ComfyUI-RTX-Remix. 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+ (the pack is V3-schema), but no Toolkit and no special dependencies for this node itself.

Where people get burned: double-negation confusion, mostly - it's easy to stack two inverters and forget which one you meant. If a condition feels "backwards," trace the chain: each invert flips the polarity, and two of them cancel out. There's no hidden behavior here - what you see is literally not value. Use it as a one-way valve in your logic and you'll never regret it.