DS4MapperTest

Fork of archived DS4MapperTest, used as a testing ground for controller mapping ideas, binding behaviour, sensitivity settings, etc. The application currently supports the DualShock 4, DualSense, 8BitDo Ultimate 2 Wireless, Steam Controller 2015, Steam Controller 2026, JoyCon, and Switch Pro.

Quick Start

• Download and unzip the latest build: Latest release
• Install the runtime dependencies listed below.
• Connect a supported controller.
• Run DS4MapperTest.exe from the unzipped folder.
• Select or create a profile.
• Configure the bindings and settings you want.
• Save the profile and start using it.

Windows SmartScreen Warning

The first time you run DS4MapperTest.exe, Windows shows a blue "Windows protected your PC" screen. Click More info, then Run anyway.

This happens because the release binaries are not code signed. The warning means Windows does not recognise the publisher, not that it found anything wrong with the file. A code signing certificate is issued to a verified person or company and costs money to maintain, so this fork ships unsigned. If you would rather not take that on trust, build from source using the steps under Installation for Devs.

Profile Storage

Profiles are saved under your Windows user profile, in %APPDATA%\DS4TestUniversal\Profiles\ (i.e. C:\Users\<you>\AppData\Roaming\DS4TestUniversal\Profiles\). Each profile is a .universal-profile.json file and works with any supported controller, so profiles are grouped into folders you name yourself (Default and VALORANT are created for you) rather than by controller type. Back them up or move them between machines by copying that folder.

Profiles from before the universal format live alongside it in %APPDATA%\DS4TestUniversal\LegacyProfiles\, in a subfolder per controller type (DualShock4, DualSense, SwitchPro, JoyCon, SteamController, SteamControllerTriton, EightBitDoUlt2Wireless). These are kept only as a migration source and are not loaded directly.

The upstream Ryochan7 DS4MapperTest stores its data in %APPDATA%\DS4Test\. This fork does not read, write, copy, move, or migrate that folder automatically, so the original app and this fork can be installed side by side without affecting each other's profiles. If you want to reuse an upstream profile here, copy it manually into this fork's profile folder.

Runtime Dependencies

• .NET 10 Desktop Runtime x64 https://dotnet.microsoft.com/en-us/download/dotnet/10.0
• Visual C++ 2015-2022 Redistributable x64 https://aka.ms/vs/17/release/vc_redist.x64.exe
• USBIP Driver 0.9.7.7 or later https://github.com/vadimgrn/usbip-win2
• libVIIPER is bundled with the application https://github.com/Alia5/VIIPER

Optional Tools

• FakerInput 0.1.1 Needed for the FakerInput mouse and keyboard output backend. https://github.com/Ryochan7/FakerInput/releases/download/v0.1.1/FakerInput_Setup_0.1.1_x64.msi
• HidHide For if you want to hide the physical controller while using a virtual output device. https://docs.nefarius.at/projects/HidHide/Simple-Setup-Guide/

Screenshots

Binding workflow

Mouse routing

Gyro sensitivity and angle calibration

Controller Compatibility

• DualShock 4
• DualSense
• DualSense Edge
• 8BitDo Ultimate 2 Wireless
• Steam Controller 2015
• Steam Controller 2026
• JoyCon
• Switch Pro

Installation for Devs

• Install Visual Studio with the .NET desktop development workload.
• Install the .NET 10 SDK.
• Open DS4MapperTest.sln.
• Use the x64 platform.
• Set DS4MapperTest as the startup project if you want to run the app directly.
• Restore NuGet packages before building.
• FakerInputWrapper is bundled under DS4MapperTest/libs/x64/, so nothing extra is needed to build the FakerInput-backed features. Running them still needs the FakerInput driver installed.

Running the Tests

The unit tests build only under the Debug Tests and Release Tests configurations:

dotnet test DS4MapperTest.sln -c "Release Tests"

A bare dotnet test resolves the Debug configuration, where the test project is deliberately left out of the build, and reports a missing test assembly rather than running anything. Those two configurations define MAKE_TESTS, which stubs out the real keyboard and mouse injection, so a test run cannot type into the desktop of whoever is running it. That is why the tests are not simply built everywhere.

Acknowledgements

• GamepadMotionHelpers: Source of some ported gyro-related logic. MIT licensed. https://github.com/JibbSmart/GamepadMotionHelpers/blob/master/LICENSE
• JoyShockMapper: behavioural reference and source of some ported gyro-related logic. MIT licensed. https://github.com/JibbSmart/JoyShockMapper/blob/master/LICENSE.md
• JSM Custom Curve: UI inspiration. https://github.com/evan1mclean/JSM_custom_curve

Licence

• GPL v3: LICENSE.txt