简体中文
EnglishWhere to Find Troubleshooting and FAQ Information for Nefarius Projects
Updated
Troubleshooting and FAQ content on docs.nefarius.at is organized per project, not in one central support page. Each major project (DsHidMini, HidHide, BthPS3, ViGEm, ScpToolkit) has its own FAQ, debugging, or removal page, so the fastest path is to open the documentation section for the specific tool that is failing. Use the project-specific page when you know which driver or utility is involved; use the general debugging and research pages when the symptom is a crash, a driver load failure, or a device that is not detected at all.
Project-specific FAQ and troubleshooting pages
| Project | Where to look | Typical problems covered |
|---|---|---|
| DsHidMini | Frequently Asked Questions, Debugging the Drivers, How to Install/Remove, Output Rate Control Explained, HID Device Modes Explained | Controller modes, installation issues, output rate behavior |
| HidHide | Frequently Asked Questions, Simple setup guide, Fixing an improper removal of HidHide, Manual installation on ARM64 | Hidden devices not behaving as expected, broken uninstall, ARM64 setup |
| BthPS3 | Frequently Asked Questions, Debugging the Drivers, Driver Configuration Utility Explained, Compatible Bluetooth Devices | Bluetooth pairing and compatibility, driver configuration |
| ViGEm | Common Errors, Emergency Feature, Possible Exit Codes, Logging, Signature & Manifest Verification | Runtime errors, exit codes, log collection, integrity checks |
| ScpToolkit | Manual removal of ScpToolkit residue, History of SCP | Leftover files and registry residue after removal |
| FireShock / AirBender | Removal Guide pages | Clean removal of the driver |
Debugging guides that apply across projects
Several pages address failure modes that are not tied to a single tool:
- Debugging the Drivers (listed under both BthPS3 and DsHidMini) — for driver-level faults.
- Fix Symbol loading for Kernel Driver minidump analysis — under Research; use this when you have a kernel minidump and need symbols to read it.
- How to check which architecture I'm running — relevant before installing or manually removing any driver, since ARM64 and x64 paths differ (see the HidHide ARM64 page).
- Common Errors and Possible Exit Codes under ViGEm — for command-line or runtime failures with explicit error codes.
Compatibility and device-specific notes
If the problem is "my controller or Bluetooth device is not recognized," check the compatibility pages before assuming a bug:
- Compatible Bluetooth Devices and Controller Compatibility under BthPS3.
- Amazon's Choice "Pro Controller" Compatibility — a device-specific note.
- Vendor and Product IDs used by NSS drivers — under Research; useful when a device is detected but matched to the wrong driver.
How to use these pages effectively
- Identify the exact project involved (which driver or utility is installed and failing).
- Open that project's FAQ first; most recurring issues are answered there.
- If the FAQ does not cover it, move to the project's Debugging or Common Errors page.
- For uninstall or reinstall problems, use the dedicated Removal Guide or Fixing an improper removal page rather than a general install guide.
- For crashes with logs or dumps, use the symbol-loading and logging pages to produce readable diagnostics.
A practical example: if a game does not see a DualShock 4 through DsHidMini, the sequence is DsHidMini FAQ → HID Device Modes Explained → XInput Mode Explained, since the mode determines whether the controller appears as XInput or DInput. If instead the device is invisible to the whole system, check HidHide's FAQ and the improper-removal page, because a partially removed HidHide installation can keep hiding devices.