How to use Glyphs on Elements node in Oraphim

Type ID: geometry.glyphs_on_elements
Category: Text

What this node does

The Glyphs on Elements 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 14 sockets and 12 properties for this node. Its main registered inputs are Geometry, Text, Font; 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
Text	text	String
Font	fontFamily	String
Style	fontStyle	String
Size	fontSize	Float
Weight	fontWeight	Float
Depth	depth	Float
Glyph Scale	glyphScale	Float
Offset X	offsetX	Float
Offset Y	offsetY	Float
Offset Z	offsetZ	Float
Point Radius	pointRadius	Float
Center	center	Bool

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Text	text	String	Inputs	0.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
Glyph Scale	glyphScale	Float	Inputs	0.009999999776482582
Offset X	offsetX	Float	Inputs	0.0
Offset Y	offsetY	Float	Inputs	0.0
Offset Z	offsetZ	Float	Inputs	0.0
Point Radius	pointRadius	Float	Inputs	0.03500000014901161
Center	center	Bool	Inputs	1.0

How to use it

1. Add Glyphs on Elements from node search. Use geometry.glyphs_on_elements 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 Text, Font, Style 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 Glyphs on Elements. Feed a compatible source into Geometry. Change Text 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
• Text Motion — geometry.text_motion
• 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.