How to use Gradient Color node in Oraphim

Type ID: geometry.gradient_color
Category: Color

What this node does

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

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

Inputs

Socket	Key	Type
Geometry	geometry	Geometry3D

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Axis	axis	String	Gradient	0.0
Color A R	colorAR	Float	Color A	0.11999999731779099
Color A G	colorAG	Float	Color A	0.46000000834465027
Color A B	colorAB	Float	Color A	1.0
Color A A	colorAA	Float	Color A	1.0
Color B R	colorBR	Float	Color B	1.0
Color B G	colorBG	Float	Color B	0.3400000035762787
Color B B	colorBB	Float	Color B	0.23999999463558197
Color B A	colorBA	Float	Color B	1.0

How to use it

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

Related nodes

• 3D Cursor — geometry.tool_3d_cursor
• Active Camera — geometry.input_active_camera
• Active Element — geometry.tool_active_element
• Advect Grid — geometry.grid_advect
• Arc — geometry.curve_primitive_arc

Return to the complete Oraphim node reference.