How to use Geometry Proximity node in Oraphim

Type ID: geometry.proximity
Category: Utility

What this node does

The Geometry Proximity 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 7 sockets and 4 properties for this node. Its main registered inputs are Geometry, Group ID, Sample Position; its main outputs are Position, Distance, Is Valid. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Geometry	target	Geometry3D
Group ID	groupId	Int
Sample Position	sourcePosition	Vector3
Sample Group ID	sampleGroupId	Int

Outputs

Socket	Key	Type
Position	position	Vector3
Distance	distance	Float
Is Valid	isValid	Bool

Controls

Control	Key	Type	Group	Registry default
Group ID	groupId	Int	Inputs	0.0
Sample Position	sourcePosition	Vector3	Inputs	0.0
Sample Group ID	sampleGroupId	Int	Inputs	0.0
Target Geometry	target_element	String	Node	FACES

How to use it

1. Add Geometry Proximity from node search. Use geometry.proximity 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 Group ID, Sample Position, Sample Group ID first so you can see the node's effect in isolation.
4. Route Position (Vector3) 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 Geometry Proximity. Feed a compatible source into Geometry. Change Group ID away from its registry default and compare the result. Connect Position 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

• Sample Nearest Surface — geometry.sample_nearest_surface
• Image Info — geometry.image_info
• Raycast — geometry.raycast
• Sample Curve — geometry.curve_sample
• Sample UV Surface — geometry.sample_uv_surface

Return to the complete Oraphim node reference.