Node reference
How to use Font node in Oraphim
Use the Font node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID geometry.input_font.
Updated August 28, 2026How to use Font node in Oraphim
Type ID: geometry.input_font
Category: Input
What this node does
Provides font data to downstream geometry operations.
The current Oraphim runtime registers 2 sockets and 1 properties for this node. Its main registered inputs are Font; its main outputs are Geometry. The tables below are generated from the runtime registry rather than a handwritten approximation.
Inputs
| Socket | Key | Type |
|---|---|---|
| Font | font |
String |
Outputs
| Socket | Key | Type |
|---|---|---|
| Geometry | out_geometry |
Geometry3D |
Controls
| Control | Key | Type | Group | Registry default |
|---|---|---|---|---|
| Font | font |
String |
Inputs | 0.0 |
How to use it
- Add Font from node search. Use
geometry.input_fontwhen you need the exact registry entry. - Connect a compatible
Stringsource to Font. Add the other inputs only when the operation needs them. - Start with the registry defaults and adjust Font first so you can see the node's effect in isolation.
- Route Geometry (
Geometry3D) into a compatible downstream node, viewer, or output path. - 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 Font. Feed a compatible source into Font. Change Font 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
- Active Camera —
geometry.input_active_camera - Bone Info —
geometry.bone_info - Camera Info —
geometry.camera_info - Collection —
geometry.input_collection - Collection Children —
geometry.collection_children
Return to the complete Oraphim node reference.