Node reference

How to use Sample Curve node in Oraphim

Use the Sample Curve node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.curve_sample.

Updated August 28, 2026

How to use Sample Curve node in Oraphim

Type ID: geometry.curve_sample
Category: Utility

What this node does

The Sample Curve 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 9 sockets and 6 properties for this node. Its main registered inputs are Curves, Factor, Length; its main outputs are Position, Tangent, Normal. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Curves curves Geometry3D
Factor factor Float
Length length Float
Curve Index curveIndex Int
Value value Float

Outputs

Socket Key Type
Position position Vector3
Tangent tangent Vector3
Normal normal Vector3
Value outValue Float

Controls

Control Key Type Group Registry default
Factor factor Float Inputs 0.0
Length length Float Inputs 0.0
Curve Index curveIndex Int Inputs 0.0
Value value Float Inputs 0.0
Attribute attribute String Node 0.0
Domain domain String Node 0.0

How to use it

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