Node reference

How to use Field Distortion node in Oraphim

Use the Field Distortion node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID motion.field.image_distort.

Updated August 28, 2026

How to use Field Distortion node in Oraphim

Type ID: motion.field.image_distort
Category: Distort

What this node does

The Field Distortion 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 4 sockets and 7 properties for this node. Its main registered inputs are Image, Field; its main outputs are Output, Metadata. The tables below are generated from the runtime registry rather than a handwritten approximation.

Inputs

Socket Key Type
Image in_color Image
Field in_field Field

Outputs

Socket Key Type
Output out_color Image
Metadata out_metadata Metadata

Controls

Control Key Type Group Registry default
Amount amount Float Distortion 1.0
Strength Scale strengthScale Float Distortion 0.0005000000237487257
Maximum Displacement maxDisplacement Float Distortion 500.0
Interpolation interpolation String Sampling Bilinear
Edges edgeMode String Sampling Clamp
Time Scale timeScale Float Animation 1.0
Preserve Alpha preserveAlpha Bool Alpha 1.0

How to use it

  1. Add Field Distortion from node search. Use motion.field.image_distort when you need the exact registry entry.
  2. Connect a compatible Image source to Image. Add the other inputs only when the operation needs them.
  3. Start with the registry defaults and adjust Amount, Strength Scale, Maximum 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 Field Distortion. Feed a compatible source into Image. Change Amount 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.

Return to the complete Oraphim node reference.