Device Monitor
Device Monitor is the main tool for checking what Helios receives and what it sends.
Sections
- Sticks
- Buttons
- Other, including motion, touch, and available rumble feedback
- Keyboard
- Mouse
- Two configurable graphs
Each section can be set to Always, Active, or Hidden. IN is the current input, including an active GPC 3 Input Translator’s mappings.
Controller OUT is selected automatically: GPC 3 output while GPC 3 is active, otherwise the report from a connected Titan Two, otherwise direct Helios output. There is no output-source selector. Keyboard and mouse sections show their logical output. These readings do not confirm that the target game accepted an input.
The Other section shows separate Titan rumble, PS rumble, and Xbox rumble rows when feedback is available. L/R are body motors and LT/RT are trigger feedback. PlayStation LH/RH are haptic signal levels, not motor strength. Zero can mean no current feedback; it does not establish that the device lacks support. Disconnecting a source clears its feedback.
Graphs
Drag an IN or OUT value onto Graph 1 or Graph 2 to track it over time. Choose a color for each plotted value and remove items that are no longer needed.
Use
| Step | Action |
|---|---|
| 1 | Start the source tool and confirm IN values move. |
| 2 | Start GPC3 or another processing tool and compare the changed OUT values. |
| 3 | Start the destination and confirm the update-rate label remains active. |
Troubleshooting
- No data: no compatible input or output source is active.
- Unexpected controller OUT values: check whether GPC 3 is running or Titan Bridge is connected; these determine the displayed report automatically.
- IN moves, OUT does not: for direct passthrough, enable Developer Mode and the input tool's write-to-output switch. For a processed path, leave direct write off and confirm the processor is running.
- Values update slowly: check the source polling/capture status before blaming the monitor.