Nexus virtual output: VIIPER and USB-IP
Nexus reads a physical controller and publishes the virtual controller selected by the profile. VIIPER/USB-IP enables that virtual output. A physical controller may be detected even when the backend is unavailable.
Use Nexus’s Controller and Driver Setup check first. Install or repair only when required, follow the actual Windows prompt and reboot if requested. An installed component is not proof that gameplay works.
HidHide: optional double-input protection
HidHide hides the physical controller from games while allowing Nexus to read it. Installing it alone is not enough: configure the application allowlist and hiding selection correctly. A misconfigured hiding rule can also make a controller disappear from Nexus. Keep a way to reopen its configuration.
FakerInput: optional keyboard and mouse output
Standard virtual gamepad output does not require FakerInput. Use it only when your keyboard/mouse mapping setup needs its supported output method. Test a simple mapping before a complex macro.
DualShock 3: separate setup
DS3/SIXAXIS uses DsHidMini and, for supported Bluetooth setups, BthPS3. Follow their official instructions. SXS and DS4Windows input modes use different Nexus input paths; enable the corresponding family and reconnect after mode changes. Do not follow DS4 Windows Bluetooth pairing steps for DS3.
DsHidMini documentation ↗ · BthPS3 documentation ↗
Legacy DS4Windows: different backend
Many older DS4Windows releases use ViGEmBus. Those instructions should not be used to diagnose every Nexus VIIPER issue. Keep the exact release and backend in mind when asking for help.
Runtime
The complete Nexus x64 package includes .NET 10.0.14. Framework-dependent developer builds have their own runtime requirements. Extracting only an EXE is not a supported installation.