Node reference

How to use Set Spline Resolution node in Oraphim

Use the Set Spline Resolution node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.set_spline_resolution.

Updated August 28, 2026

How to use Set Spline Resolution node in Oraphim

Type ID: geometry.set_spline_resolution
Category: Transform

What this node does

Changes spline resolution on incoming geometry and passes the edited result downstream.

The current Oraphim runtime registers 4 sockets and 2 properties for this node. Its main registered inputs are Curve, Selection, Resolution; its main outputs are Curve. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Curve curve Geometry3D
Selection selection Bool
Resolution resolution Int

Outputs

Socket Key Type
Curve out_geometry Geometry3D

Controls

Control Key Type Group Registry default
Selection selection Bool Inputs 1.0
Resolution resolution Int Inputs 12.0

How to use it

  1. Add Set Spline Resolution from node search. Use geometry.set_spline_resolution when you need the exact registry entry.
  2. Connect a compatible Geometry3D source to Curve. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Selection, Resolution first so you can see the node's effect in isolation.
  4. Route Curve (Geometry3D) 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 Set Spline Resolution. Feed a compatible source into Curve. Change Selection away from its registry default and compare the result. Connect Curve 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.