Node reference

How to use Switch Value node in Oraphim

Use the Switch Value node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID motion.logic.switch.

Updated August 28, 2026

How to use Switch Value node in Oraphim

Type ID: motion.logic.switch
Category: Utility

What this node does

The Switch Value node is registered in Oraphim's Utility category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 5 sockets and 3 properties for this node. Its main registered inputs are Condition, False, True; its main outputs are Value, Condition. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Condition in_condition Bool
False in_false Float
True in_true Float

Outputs

Socket Key Type
Value out_value Float
Condition out_condition Bool

Controls

Control Key Type Group Registry default
Condition condition Bool Defaults 0.0
False Value falseValue Float Defaults 0.0
True Value trueValue Float Defaults 1.0

How to use it

  1. Add Switch Value from node search. Use motion.logic.switch when you need the exact registry entry.
  2. Connect a compatible Bool source to Condition. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Condition, False Value, True Value first so you can see the node's effect in isolation.
  4. Route Value (Float) into a compatible downstream node, viewer, or output path.
  5. Preview a representative frame, change one input/control at a time, and save/reopen reusable graphs to verify persistence.

Practical example

Create a small test graph with Switch Value. Feed a compatible source into Condition. Change Condition away from its registry default and compare the result. Connect Value to a compatible downstream stage so the result is visible. Keeping this test graph small makes socket-type, context, and parameter mistakes easier to diagnose before the node is used in a production graph.

Troubleshooting

  • If a connection is rejected, compare the exact socket data types in the tables above; Oraphim graph connections are typed.
  • If the result looks unchanged, confirm this node is on the active path to the viewer/output and that the expected graph/resource is selected.
  • If a control is unavailable, check required inputs and whether the property belongs to an internal or mode-dependent group.
  • If a saved graph behaves differently later, reopen it and verify node identity, connections, and edited property values before rendering.

Return to the complete Oraphim node reference.