Troubleshooting¶
"Nothing happens when I press V"¶
- Check Project Settings → Quick Menu → Active Graph is set
- Verify the graph has a Root node connected to at least one WheelOutput
- If using Switch nodes, make sure the current context has a matching output (or a Default connection)
"Menu shows wrong actions for this editor"¶
- Open your graph and check your Switch node connections
- Verify the Switch type matches what you're trying to detect (Editor Context vs. Editor Mode vs. Selection Count)
- Add the missing context as a case on the Switch node
"Python action doesn't work"¶
- Ensure the Python Editor Script Plugin is enabled (Edit → Plugins → search "Python")
- Check the Output Log for Python errors (Window → Developer Tools → Output Log)
- Test your code in the Python console first (Window → Developer Tools → Python Console)
"Some actions are grayed out"¶
- Blueprint actions (Component Op, Component Property) require a Blueprint Editor to be open with a component selected
- Niagara/PCG actions only appear when those plugins are enabled
- Some actions require a specific selection state (e.g., Actor Op → Group requires multiple actors selected)
"How do I create a context-aware menu?"¶
- Add a Switch node (e.g., Switch: Editor Context)
- Add the contexts you want as cases
- Connect each case output to a different WheelOutput
- Each WheelOutput can have different actions
- Connect a Default output for unmatched contexts
See Context Detection for a detailed walkthrough.
"How do I create nested sub-menus?"¶
- Add a SubMenu node
- Connect action nodes to the SubMenu's menu input pins
- Connect the SubMenu's menu output to a WheelOutput menu pin
- When hovering that wedge, children expand as a nested ring
"Wedge limit reached"¶
Each wheel supports a maximum of 10 wedges. Use SubMenu nodes to group related actions and reduce top-level wedge count.
Getting Help¶
- Discord — community support
- GitHub Issues — bug reports
- GitHub Discussions — Q&A, ideas, showcase