Retro Replay Retro Replay gaming reviews, news, emulation, geek stuff and more!
DS4MapperTest v0.0.29 has been released, serving as a platform for experimenting with various mapping ideas. It supports multiple controllers, including DualShock 4, DualSense, 8BitDo Ultimate 2 Wireless, Steam Controller, JoyCon, and Switch Pro. Key updates include reestablishing gyro calibration for Steam Controllers, defaulting KB+M profile selection to Xbox 360, and improved error handling. The solution now targets .NET 10, with updates to Visual Studio 2026 and various libraries like HandyControl and NewtonsoftJson. Additionally, the version includes enhancements for touchpad functionality and attempts to streamline service management with VIIPER compatibility.
(HEY YOU!! We hope you enjoy! We try not to run ads. So basically, this is a very expensive hobby running this site. Please consider joining us for updates, forums, and more. Network w/ us to make some cash or friends while retro gaming, and you can win some free retro games for posting. Okay, carry on đ)
DS4MapperTest v0.0.29 has been released. It primarily serves as a testing platform for exploring various mapping concepts. The app currently supports the DualShock 4, DualSense, 8BitDo Ultimate 2 Wireless, Steam Controller, JoyCon, and Switch Pro.
DS4MapperTest Changelog:
Set the firstReport flag for a reconnected Steam Controller to enable gyro calibration again
Initiated prototype usage of libVIIPER
Updated the KB+M profile selection to default to Xbox 360 type, based solely on the enabled flag
Added DispatcherUnhandledException
Included DS4 touchpad click as an output button binding
Updated solution targeting .NET 10 and transitioned to Visual Studio 2026. Upgraded HandyControl
Updated NewtonsoftJson, WpfScreenHelper, and NLog
Updated packages for the test suite
Enabled SuppressUnmanagedCodeSecurity for additional delegates used with libVIIPER
Created an alias for the DS4 touchpad click button
Corrected old unit tests
Attempted to allow the service to be stopped and restarted when utilizing VIIPER, as usbip_win2 can be temperamental.
