Getting Started

A Helios workflow normally has a source, optional processing, and a destination.

text

Controller or Video → Optional Script or CV → Output

First Controller Workflow

Step	Action
1	Open an input tool that matches the controller: XInput Input, DS4 Input, or DS5 Input.
2	Refresh the list and select the controller. For direct passthrough, enable Developer Mode under Preferences → Other, then enable Write to Controller Output.
3	Start the input tool.
4	Open Device Monitor and confirm the IN values respond.
5	Open the desired output tool, configure it, and start it.
6	Confirm OUT values respond in Device Monitor and test in the target app or console.

For keyboard/mouse, use KBM Input and press Esc + Left Shift when you need to leave capture.

Leave Write to Controller Output off when GPC 3 or another processor should produce the final output. The direct-write switch is only needed when the input should pass straight to the destination.

Add GPC3

Step	Action
1	Leave the input tool's direct-write switch off, then create or select a `.gpc3` script in File Explorer.
2	In GPC 3, compile the source to `.gbc3` if needed.
3	Select the bytecode and, optionally, a `.ipt` Input Translator profile.
4	Start GPC 3 and verify the changed OUT values in Device Monitor.

See the GPC3 language documentation for syntax and functions.

Add Computer Vision

Step	Action
1	Start one capture tool and confirm its Write FPS is stable.
2	Configure Python in Preferences when using CV Python.
3	Select a `.py` or supported C++ CV script and start the matching scripting tool.
4	Use Video Display or OpenGL Display to inspect the processed frame.
5	Start the controller/output path only if the CV script needs it.

See Computer Vision Setup for capture, GPU, and inference details.

Organize the Workspace

Use the Activity Bar to switch between layouts in the current setup.
Load a different complete setup from View → Load Setup.
Add a Run Group when several tools should start and stop together.
Use a panel's Float button to move it to its own window.
Closing a panel lets you hide or unload it; loaded panels can be shown again from View → Panels.

Debug in This Order

Step	Action
1	Source tool is running.
2	Device Monitor shows IN activity.
3	Script or CV tool shows no error.
4	Device Monitor shows expected OUT activity.
5	Destination tool is connected and running.