How to use Displacement Map node in Oraphim

Type ID: fusion.displacementmap
Category: Distort

What this node does

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

The current Oraphim runtime registers 3 sockets and 11 properties for this node. Its main registered inputs are Input, Displacement Map; its main outputs are Output. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket	Key	Type
Input	in_color	Image
Displacement Map	in_displacement_map	Image

Outputs

Socket	Key	Type
Output	out_color	Image

Controls

Control	Key	Type	Group	Registry default
Effect Type	effectType	String	Internal	fx_displacement_map
Horizontal Channel	horizontalChannel	String	Displacement Map	Red
Vertical Channel	verticalChannel	String	Displacement Map	Green
Max Horizontal Displacement	maxHorizontalDisplacement	Float	Displacement	20.0
Max Vertical Displacement	maxVerticalDisplacement	Float	Displacement	20.0
Map Behavior	mapBehavior	String	Map Placement	Stretch Map to Fit
Map Offset X	mapOffsetX	Float	Map Placement	0.0
Map Offset Y	mapOffsetY	Float	Map Placement	0.0
Edge Mode	edgeMode	String	Edges	Clamp
Quality	quality	String	Quality	High
Preserve Alpha	preserveAlpha	Bool	Alpha	1.0

How to use it

1. Add Displacement Map from node search. Use fusion.displacementmap when you need the exact registry entry.
2. Connect a compatible Image source to Input. Add the other inputs only when the operation needs them.
3. Start with the registry defaults and adjust Horizontal Channel, Vertical Channel, Max Horizontal Displacement first so you can see the node's effect in isolation.
4. Route Output (Image) 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 Displacement Map. Feed a compatible source into Input. Change Horizontal Channel away from its registry default and compare the result. Connect Output 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

• CC Blobbylize — fusion.blobbylize
• Detail-preserving Upscale — fusion.detailpreservingupscale
• Page Turn — fusion.pageturn
• Perspective Effect — fusion.perspectiveeffect
• Perspective Warp — fusion.perspectivewarp

Return to the complete Oraphim node reference.