How to use Import Text node in Oraphim

Type ID: geometry.import_text
Category: Input

What this node does

Imports Text data as an editable geometry-graph source.

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

Inputs

Socket	Key	Type
Instance	instanceLayerId	String
Text	text	String
Font Family	fontFamily	String
Font Style	fontStyle	String
Size	size	Float
Font Weight	fontWeight	Float
Tracking	tracking	Float
Line Height	lineHeight	Float
Depth	depth	Float
Color R	colorR	Float
Color G	colorG	Float
Color B	colorB	Float
Random Color	randomColor	Bool
Random Seed	seed	Int

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Instance	instanceLayerId	String	Inputs	0.0
Text	text	String	Inputs	0.0
Font Family	fontFamily	String	Inputs	0.0
Font Style	fontStyle	String	Inputs	0.0
Size	size	Float	Inputs	96.0
Font Weight	fontWeight	Float	Inputs	400.0
Tracking	tracking	Float	Inputs	0.0
Line Height	lineHeight	Float	Inputs	0.0
Depth	depth	Float	Inputs	0.0
Color R	colorR	Float	Inputs	1.0
Color G	colorG	Float	Inputs	1.0
Color B	colorB	Float	Inputs	1.0
Random Color	randomColor	Bool	Inputs	0.0
Random Seed	seed	Int	Inputs	0.0

How to use it

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

• Import CSV — geometry.import_csv
• Import VDB — geometry.import_vdb
• Mouse Position — geometry.mouse_position
• Named Attribute — geometry.input_named_attribute
• Active Camera — geometry.input_active_camera

Return to the complete Oraphim node reference.