How to use Surface Match / Planar Blend node in Oraphim

Type ID: fusion.surfacematch
Category: Transform

What this node does

The Surface Match / Planar Blend node is registered in Oraphim's Transform category and performs the graph operation represented by its sockets and controls below.

The current Oraphim runtime registers 0 sockets and 21 properties for this node. Its main registered inputs are no fixed inputs; its main outputs are no fixed outputs. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

This node has no fixed input sockets in the current runtime registry.

Outputs

This node has no fixed output sockets in the current runtime registry.

Controls

Control	Key	Type	Group	Registry default
Top Left X	cornerTLX	Float	Planar Corners	0.0
Top Left Y	cornerTLY	Float	Planar Corners	0.0
Top Right X	cornerTRX	Float	Planar Corners	0.0
Top Right Y	cornerTRY	Float	Planar Corners	0.0
Bottom Right X	cornerBRX	Float	Planar Corners	0.0
Bottom Right Y	cornerBRY	Float	Planar Corners	0.0
Bottom Left X	cornerBLX	Float	Planar Corners	0.0
Bottom Left Y	cornerBLY	Float	Planar Corners	0.0
Surface Displace	surfaceDisplace	Float	Surface Match	12.0
Surface Scale	surfaceScale	Float	Surface Match	7.5
Edge Wear	edgeWear	Float	Surface Match	0.2800000011920929
Paint Opacity	paintOpacity	Float	Surface Match	0.8199999928474426
Light Wrap	lightWrap	Float	Surface Match	0.3499999940395355
Grain Match	grainMatch	Float	Texture Match	0.1599999964237213
Blur Match	blurMatch	Float	Texture Match	1.5
Contrast Match	contrastMatch	Float	Texture Match	-0.11999999731779099
Seed	seed	Float	Texture Match	13.0
Tracker Influence	trackerInfluence	Float	Tracking	1.0
Tracker Offset X	trackerOffsetX	Float	Tracking	0.0
Tracker Offset Y	trackerOffsetY	Float	Tracking	0.0
Blend Hint	blendHint	String	Composite	0.0

How to use it

1. Add Surface Match / Planar Blend from node search. Use fusion.surfacematch when you need the exact registry entry.
2. Place the node as a source/context operation; it has no fixed input socket in the current registry.
3. Start with the registry defaults and adjust Top Left X, Top Left Y, Top Right X first so you can see the node's effect in isolation.
4. Because there is no fixed output socket, validate the graph context or downstream resource that this node is intended to affect.
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 Surface Match / Planar Blend. Change Top Left X away from its registry default and compare the result. 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

• Transform — fusion.transform
• 3D Camera Tracker — fusion.cameratracker
• Advanced Color Correction — fusion.advanced_color_correction
• Audio — fusion.audio
• Audio Generate — fusion.audio_generate

Return to the complete Oraphim node reference.