ZeroCue is a free, experimental Windows application for using a SCUF Envision Pro without keeping Corsair iCUE active. It reads the controller in wired or wireless-receiver mode, exposes an Xbox-compatible virtual controller, and lets you manage mappings and device settings from a single interface.
Warning
ZeroCue is alpha software. ViGEmBus must be installed before installing the ZeroCue WinUSB driver. ZeroCue replaces the Windows driver for the selected SCUF interfaces, so without ViGEmBus the physical Xbox-compatible controller disappears and ZeroCue cannot create the virtual Xbox 360 replacement. Installing the wired controller driver, the wireless receiver driver, or both requires administrator privileges. While a ZeroCue driver is installed, iCUE cannot detect the controller through those interfaces.
Caution
Hardware compatibility is currently guaranteed only for the SCUF Envision Pro
V2. Wired SCUF Envision V2 devices using VID_1B1C / PID_3A04 are detected as
an experimental, unvalidated profile that reuses the Pro V2 protocol. Original
wired Envision-family devices using VID_2E95 / PID_434B or PID_434D are
also experimental and reuse that wired protocol. The SCUF PC Controller Dongle
V1 using VID_2E95 / PID_434E is experimental and
reuses the V2 wireless protocol only after its WinUSB endpoint topology has
been validated. ZeroCue is early alpha software: bugs, failed connections,
crashes, and unexpected behavior may occur, and reliable operation is not
guaranteed.
ZeroCue is an independent project and is not affiliated with or endorsed by Corsair or SCUF Gaming.
- Wired and wireless-receiver controller communication.
- Xbox-compatible virtual controller output through ViGEm.
- Face-button, paddle, G-key, keyboard, mouse, macro, and shifted mappings.
- Per-profile stick curves, deadzones, trigger curves, rumble, RGB, eco mode, and automatic application linking.
- Profile import and export through portable, versioned JSON files. Machine-local application links are excluded from transferred profiles.
- Configurable system tray behavior that keeps remapping active in the background when the main window is hidden.
- Portable, self-contained Windows x64 build: no separate .NET installation.
- Two centralized diagnostic logs beside the executable: communication and input/mapping activity.
- Restricted driver recovery based on packages created and recorded by ZeroCue.
- Windows 10 or Windows 11 on an x64 PC.
- ViGEmBus 1.22.0 installed and working. ZeroCue includes the ViGEm client library, but it does not include or install the ViGEmBus system driver.
ViGEmBus is what allows ZeroCue to expose the SCUF controller as a virtual Xbox 360 controller. Without it, ZeroCue may still read the physical controller after WinUSB is installed, but games and gamepad testers will not see an Xbox controller. ZeroCue checks this requirement at startup and displays a warning if ViGEmBus is missing or unavailable.
You can verify the installation in Windows Device Manager by selecting View > Devices by connection and looking for Nefarius Virtual Gamepad Emulation Bus. Its device status should report that it is working correctly. See the official ViGEmBus installation and troubleshooting guide.
- Install ViGEmBus 1.22.0 from the official release linked above. Restart Windows if the installer requests it.
- Download the portable ZeroCue ZIP from the GitHub release.
- Extract the complete ZIP to a normal writable folder. Do not run the executable from inside the ZIP.
- Run
zerocue.exe. If ZeroCue reports that ViGEmBus is unavailable, do not install WinUSB until ViGEmBus is installed and working. - Connect the controller by cable or its supported receiver.
- Install the required driver from ZeroCue: choose the controller driver for a wired USB connection or the receiver driver for a wireless connection. Install both if you plan to use both connection modes. Windows will show an administrator prompt. ZeroCue closes iCUE during the operation and reopens it when the operation ends.
- After installation, iCUE will no longer detect the controller through the modified connection mode. Restore the original driver before using that mode with iCUE again.
Windows SmartScreen may warn about the unsigned alpha. Verify the SHA-256 shown in the GitHub release notes before running it. Never download a build from an unofficial mirror.
ZeroCue records the driver packages it installs and its restore option only removes verified packages for the selected SCUF controller or receiver. Restoring the original driver allows iCUE to detect the device again.
The wired installer recognizes the known Envision-family controller identities
1B1C:3A04, 1B1C:3A05, 2E95:434B, and 2E95:434D. The 2E95 wired
identities are treated as experimental and use the same MI_00, MI_03, and
MI_04 WinUSB bindings as the established wired transport. Driver selection
diagnostics enumerate every present and phantom 1B1C or 2E95 USB node so an
unknown hardware revision is visible in the communication log instead of being
reported only as a generic missing controller.
For the experimental V1 dongle, ZeroCue treats 2E95:434E as its composite base
state and modifies only interfaces MI_03 and MI_04; it does not replace
MI_00 or the composite parent. The observed 2E95:5046 identity is treated as
the experimental active state and follows the same whole-device model as the V2
active receiver. Both observed active identities (1B1C:3A09 and 2E95:5046)
use one unified 64-byte WinUSB transport on OUT 0x01 / IN 0x81; ZeroCue keeps
one reader on that shared ACK/input endpoint. Base identities continue to use
MI_04 (0x02 / 0x82) for control and MI_03 (IN 0x81) for input.
If the required WinUSB endpoints are not immediately available after
installation, ZeroCue removes and rescans only the exact base MI_03 device node
to force Windows to publish its new WinUSB interface, while restarting the other
selected binding normally. Active whole-device bindings are restarted directly.
Validation and diagnostics use bounded retries and timeouts. If validation still
fails, ZeroCue reports the detected topology and starts an exact automatic
rollback. Recovery also waits for every previously present interface to return on
its original driver before reporting success. Installation diagnostics include
present and phantom vendor PnP nodes, parent and problem-code properties, WinUSB
binding readiness, bounded rescan output, and the final wdi-simple output.
Automatic rollback also records a complete PowerShell and pnputil transcript in
the communication log.
ZeroCue is not required for recovery. You can use Windows Device Manager as an
administrator, locate only the SCUF controller or receiver interfaces modified by
ZeroCue, choose Uninstall device, and select the option to remove the driver
when Windows offers it. Then disconnect and reconnect the device, or reinstall
iCUE, so Windows can restore the original driver. Do not uninstall unrelated USB
devices or delete files manually from C:\Windows\INF.
- Settings, profiles, and driver manifests:
%APPDATA%\ZeroCue - Communication log:
logs\zerocue-communication.logbesidezerocue.exe - Input and mapping log:
logs\zerocue-input-mappings.logbesidezerocue.exe
Logs can contain device identifiers and local diagnostic details. Review and redact them before posting publicly.
If ZeroCue fails, disconnects, or behaves unexpectedly, please open a GitHub issue and attach both logs listed above so the problem can be analyzed and fixed. Include the exact controller version, connection mode, Windows version, and the steps that triggered the problem. Review the logs first and redact any identifiers or local details you do not want to share publicly.
- Only Windows x64 is supported.
wdi-simple.exeis the existing unsigned alpha helper. It is pinned by SHA-256, but its exact historical build recipe has not been reconstructed.- The application executable is not yet Authenticode-signed.
See SECURITY.md for private vulnerability reporting.
ZeroCue is licensed under the Apache License 2.0. You may use, modify, and redistribute it, including commercially. Redistributed modifications must retain the license and attribution notices and must clearly state which files were changed. See NOTICE and THIRD_PARTY_NOTICES.md for attribution and dependency terms.