Node reference

How to use Handle Type Selection node in Oraphim

Use the Handle Type Selection node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.curve_handle_type_selection.

Updated August 28, 2026

How to use Handle Type Selection node in Oraphim

Type ID: geometry.curve_handle_type_selection
Category: Utility

What this node does

The Handle Type Selection 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 1 sockets and 1 properties for this node. Its main registered inputs are no fixed inputs; its main outputs are Selection. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

This node has no fixed input sockets in the current runtime registry.

Outputs

Socket Key Type
Selection selection Bool

Controls

Control Key Type Group Registry default
Handle Type handleType String Node 0.0

How to use it

  1. Add Handle Type Selection from node search. Use geometry.curve_handle_type_selection when you need the exact registry entry.
  2. Place the node as a source/context operation; it has no fixed input socket in the current registry.
  3. Start with the registry defaults and adjust Handle Type first so you can see the node's effect in isolation.
  4. Route Selection (Bool) 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 Handle Type Selection. Change Handle Type away from its registry default and compare the result. Connect Selection 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.