How to use Image Texture node in Oraphim

Type ID: geometry.image_texture
Category: Input

What this node does

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

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

Inputs

Socket	Key	Type
Image	image	String
Path	path	String

Outputs

Socket	Key	Type
Geometry	out_geometry	Geometry3D

Controls

Control	Key	Type	Group	Registry default
Image	image	String	Inputs	0.0
Path	path	String	Inputs	0.0

How to use it

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