Troubleshooting

Start With the Visible Path

Check a workflow from left to right:

Step Action
1 The source tool is running without an error.
2 Device Monitor shows input or the capture tool shows stable Write FPS.
3 The script/CV tool is running and its status requirements are satisfied.
4 Device Monitor shows the expected output.
5 The destination tool is connected and running.

Stop optional tools until the smallest path works, then add them back one at a time.

Helios Does Not Start

  • Confirm the PC runs 64-bit Windows 10/11 and supports AVX2.
  • Re-extract a complete fresh package to a writable folder.
  • Check Windows Security for a quarantined packaged file.
  • Do not run Helios from inside the downloaded archive.

A Panel Is Missing

Open View → Panels and enable it. If it was unloaded, load a setup that includes the tool or load the packaged plugin again.

Controller Not Detected

  • Connect the controller before refreshing the input list.
  • Try USB before Bluetooth.
  • Close DS4Windows, Steam Input, or other software that may hold or hide the device.
  • Select the controller again and restart the input tool.

Input Moves but Output Does Not

  • For direct passthrough, enable Developer Mode under Preferences → Other, then enable Write to Controller Output in the input tool.
  • For a GPC 3 or translated path, leave the input tool's direct-write switch off and confirm GPC 3 is running with the intended script or translator.
  • Confirm the destination tool is started.
  • Use Device Monitor to compare IN and OUT.

Double Input

The game is probably receiving both the physical device and the virtual one. Close other remappers and configure the game to use only the intended output.

Capture Device Missing or Fails to Start

  • Close OBS, browser capture, conferencing, and other apps using the device.
  • Refresh the device list.
  • Choose a resolution, FPS, and format the device supports.
  • Try KS Capture, DS Capture, MF Capture, or OpenCV Capture as an alternate path.

Low or Unstable Capture FPS

  • Lower resolution or requested frame rate.
  • Try NV12 for lower bandwidth where available.
  • Use a direct USB 3.x port or the intended PCIe connection.
  • Lower the Video/OpenGL Display preview rate.
  • Avoid using the same capture device in multiple apps.

CV Python Is Not Configured or Invalid

Open Preferences → Python, search for environments, and select Python 3.10 or newer. If the environment remains invalid, choose another installation or create a clean managed environment.

Video Input Not Detected in a CV Tool

Start exactly one capture tool first and confirm it is writing frames. Then restart CV Python or CV C++.

Inference or OCR Fails

  • Select a compatible Compute GPU in Preferences.
  • Confirm the model appears in Online Resources or Engine Builder.
  • Rebuild a TensorRT engine on the current GPU/environment if it is incompatible.
  • Start with the model's recommended ROI and class priority when available.
  • Confirm the model task is exactly detect, pose, or segment.
  • For INSTALLATION_INVALID or an installation-verification error, install the latest complete official Helios release and check whether Windows Security quarantined a packaged file.

ViGEm Is Not Available

Use Install ViGEmBus in ViGEm Output and wait for the reported result. Restart Windows when Helios says the driver installation requires it. If the virtual controller exists but the game ignores it, test the other controller type.

Titan Two or Makcu Is Missing

  • Connect the device directly and refresh the list.
  • Check the panel's visible firmware, USB-port, and connection status.
  • Use the panel's repair/update action only when it reports that one is required.
  • Restart the bridge after changing USB connections or output protocol.

Remote Play Will Not Connect

  • Confirm the console and PC are on a reliable local network.
  • Sign in again and refresh profiles/consoles.
  • Wake the console and retry after any displayed cooldown.
  • Some PlayStation games may block Remote Play.

Account or Restricted-Content Error

Sign in again under Preferences → Account, refresh Online Resources, and retry the intended item. Enable automatic Windows time if Helios reports an incorrect clock. Contact support when access still fails.

For email sign-in, keep Helios open and check your junk folder. Confirm only the email that shows Helios's current verification code. If the request expired, start a new sign-in. For browser sign-in failures, check the default Windows browser and start again.

If publishing or author controls are unavailable, link both Discord and a verified email to the same Input Sense account. New uploads require the Discord account to be at least 90 days old and the Input Sense account to be at least 7 days old. If an author cannot find your account, sign in to the current release and copy your Input Sense ID from the Account page.

If a premium plugin asks for sign-in or access, use an account that owns that plugin. For a device-verification error, restart Helios first; if it began after a hardware, firmware, Windows, or security change, contact support.

Getting Help

When contacting support, include the Helios version, the exact visible error, the tools in the workflow, and relevant lines copied from Output Panel. Do not send passwords, session tokens, or private model/script files.

← PreviousFAQ