How to use Text Motion node in Oraphim

Type ID: geometry.text_motion
Category: Text

What this node does

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

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

Inputs

Socket	Key	Type
Mode	mode	String
Text	text	String
Progress	progress	Float
Start Value	startValue	Float
End Value	endValue	Float
Font	fontFamily	String
Style	fontStyle	String
Size	fontSize	Float
Weight	fontWeight	Float
Depth	depth	Float
Tracking	tracking	Float
Leading	leading	Float
Center	center	Bool
Seed	seed	Int

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Mode	mode	String	Inputs	Typewriter
Text	text	String	Inputs	0.0
Progress	progress	Float	Inputs	1.0
Start Value	startValue	Float	Inputs	0.0
End Value	endValue	Float	Inputs	100.0
Font	fontFamily	String	Inputs	0.0
Style	fontStyle	String	Inputs	0.0
Size	fontSize	Float	Inputs	96.0
Weight	fontWeight	Float	Inputs	400.0
Depth	depth	Float	Inputs	0.0
Tracking	tracking	Float	Inputs	0.0
Leading	leading	Float	Inputs	0.0
Center	center	Bool	Inputs	1.0
Seed	seed	Int	Inputs	1.0

How to use it

1. Add Text Motion from node search. Use geometry.text_motion when you need the exact registry entry.
2. Connect a compatible String source to Mode. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Mode, Text, Progress 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 Text Motion. Feed a compatible source into Mode. Change Mode 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

• String to Curves — geometry.string_to_curves
• Glyphs on Elements — geometry.glyphs_on_elements
• Text to Glyph Geometry — geometry.text_to_glyph_geometry
• Join Strings — geometry.string_join
• Fillet Curve — geometry.curve_fillet

Return to the complete Oraphim node reference.