Node reference
How to use Dropdown Menu Control node in Oraphim
Use the Dropdown Menu Control node in Oraphim. Learn its purpose, exact inputs, outputs, registered controls, example workflow, troubleshooting, and type ID fusion.expr.dropdown.
Updated August 28, 2026How to use Dropdown Menu Control node in Oraphim
Type ID: fusion.expr.dropdown
Category: Utility
What this node does
Publishes a reusable dropdown menu control value for other graph operations.
The current Oraphim runtime registers 4 sockets and 8 properties for this node. Its main registered inputs are Input; its main outputs are Output, Menu Index, Selected Label. 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 |
| Menu Index | out_value |
Int |
| Selected Label | out_label |
String |
Controls
| Control | Key | Type | Group | Registry default |
|---|---|---|---|---|
| Control Type | effectType |
String |
Control | fx_dropdown_menu_control |
| Layer ID | layerId |
String |
Routing | 0.0 |
| Master Node ID | masterNodeId |
String |
Routing | 0.0 |
| Publish to Template | publishToTemplate |
Bool |
Publishing | 1.0 |
| Comment | controlComment |
String |
Publishing | 0.0 |
| Menu Items | menuItems |
String |
Menu | Option 1|Option 2|Option 3 |
| Selected Item | menuIndex |
Int |
Menu | 1.0 |
| Cycle Out-of-range Values | cycleMenu |
Bool |
Menu | 0.0 |
How to use it
- Add Dropdown Menu Control from node search. Use
fusion.expr.dropdownwhen you need the exact registry entry. - Connect a compatible
Imagesource to Input. Add the other inputs only when the operation needs them. - Start with the registry defaults and adjust Control Type, Layer ID, Master Node ID first so you can see the node's effect in isolation.
- Route Output (
Image) into a compatible downstream node, viewer, or output path. - 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 Dropdown Menu Control. Feed a compatible source into Input. Change Control Type 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
- Layer Control —
fusion.expr.layer - 3D Point Control —
fusion.expr.point3d - Angle Control —
fusion.expr.angle - Checkbox Control —
fusion.expr.checkbox - Color Control —
fusion.expr.color
Return to the complete Oraphim node reference.