How to use Perspective Warp node in Oraphim

Type ID: fusion.perspectivewarp
Category: Distort

What this node does

The Perspective Warp 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 2 sockets and 16 properties for this node. Its main registered inputs are Input; 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

Outputs

Socket	Key	Type
Output	out_color	Image

Controls

Control	Key	Type	Group	Registry default
Effect Type	effectType	String	Internal	fx_corner_pin
Coordinate Space	coordinateSpace	String	Corners	Auto
Top Left X	cornerTLX	Float	Corners	0.0
Top Left Y	cornerTLY	Float	Corners	0.0
Top Right X	cornerTRX	Float	Corners	1.0
Top Right Y	cornerTRY	Float	Corners	0.0
Bottom Right X	cornerBRX	Float	Corners	1.0
Bottom Right Y	cornerBRY	Float	Corners	1.0
Bottom Left X	cornerBLX	Float	Corners	0.0
Bottom Left Y	cornerBLY	Float	Corners	1.0
Perspective	perspective	Float	CC Power Pin	100.0
Unstretch	unstretch	Bool	CC Power Pin	0.0
Expansion	expansion	Float	CC Power Pin	0.0
Edge Mode	edgeMode	String	Edges	Transparent
Quality	quality	String	Quality	High
Preserve Alpha	preserveAlpha	Bool	Alpha	1.0

How to use it

1. Add Perspective Warp from node search. Use fusion.perspectivewarp 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 Coordinate Space, Top Left X, Top Left Y 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 Perspective Warp. Feed a compatible source into Input. Change Coordinate Space 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
• Displacement Map — fusion.displacementmap
• Page Turn — fusion.pageturn
• Perspective Effect — fusion.perspectiveeffect

Return to the complete Oraphim node reference.