How to use Raycast node in Oraphim

Type ID: geometry.raycast
Category: Utility

What this node does

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

The current Oraphim runtime registers 11 sockets and 6 properties for this node. Its main registered inputs are Target Geometry, Attribute, Interpolation; its main outputs are Is Hit, Hit Position, Hit Normal. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Target Geometry	targetGeometry	Geometry3D
Attribute	attribute	Float
Interpolation	interpolation	Menu
Source Position	sourcePosition	Vector3
Ray Direction	rayDirection	Vector3
Ray Length	rayLength	Float

Outputs

Socket	Key	Type
Is Hit	isHit	Bool
Hit Position	hitPosition	Vector3
Hit Normal	hitNormal	Vector3
Hit Distance	hitDistance	Float
Attribute	attributeOut	Float

Controls

Control	Key	Type	Group	Registry default
Attribute	value	Float	Inputs	0.0
Interpolation	interpolation	Menu	Inputs	Interpolated
Source Position	sourcePosition	Vector3	Inputs	0.0
Ray Direction	rayDirection	Vector3	Inputs	0.0
Ray Length	rayLength	Float	Inputs	100.0
Data Type	data_type	String	Node	FLOAT

How to use it

1. Add Raycast from node search. Use geometry.raycast when you need the exact registry entry.
2. Connect a compatible Geometry3D source to Target Geometry. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Attribute, Interpolation, Source Position first so you can see the node's effect in isolation.
4. Route Is Hit (Bool) 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 Raycast. Feed a compatible source into Target Geometry. Change Attribute away from its registry default and compare the result. Connect Is Hit 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

• Geometry Proximity — geometry.proximity
• Sample Nearest Surface — geometry.sample_nearest_surface
• Sample UV Surface — geometry.sample_uv_surface
• Attribute Statistic — geometry.attribute_statistic
• Image Info — geometry.image_info

Return to the complete Oraphim node reference.