Retro Replay Retro Replay gaming reviews, news, emulation, geek stuff and more!
PadForge v3.3.2 has been released as a modern controller mapping utility for Windows, allowing users to map any controller, keyboard, or mouse to virtual devices recognized by games. The update includes three bug fixes concerning multi-device setups, enhancing the Copy From/Paste functionality, which now correctly targets the destination slot’s device. The handling of Y-axis inputs has been improved for consistent recording behavior, and joystick-class devices have been included in the mapping process, correcting previous exclusions. Users migrating from older versions can restore lost devices by reverting to the pre-migration file. Download the latest version for enhanced features and fixes.
(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 đ)
PadForge v3.3.2 has been released. It is a cutting-edge controller mapping utility for Windows that allows users to map any controller, keyboard, or mouse to virtual Xbox 360, DualShock 4, custom DirectInput, or MIDI controllers via ViGEmBus, vJoy, and Windows MIDI Services, which are recognized by games and applications as genuine hardware.
PadForge changelog:
This version includes three bug fixes from v3.3.1, specifically addressing issues reported on a multi-device setup (arcade sticks + Xinmotek + Xbox Series X across two virtual controllers).
The Copy From / Copy / Paste function now targets the destination slot’s device
Previously, when copying a slot’s mapping table to another, each Source’s DeviceGuid remained linked to the source slot’s physical-device instance. If both slots had different physical instances of the same device, the destination slot’s MappingSet would incorrectly reference the source slot’s hardware. Now, each Source’s DeviceGuid is correctly assigned to a UserSetting at the target slot that matches the source device’s variation. If the source’s instance is also assigned to the destination slot, it remains; otherwise, the first different-instance, same-product device from the destination is selected. Sources that are not found on the destination are excluded.
This change affects both the in-process “Copy From” dialog and the clipboard Copy/Paste functionality. Shift activator DeviceGuid + ChordSecondDeviceGuid retarget along the same path.
The extra-source Record button for Y-axis targets now aligns with the primary
Previously, the two Record buttons on a mapping row (the primary descriptor and the per-source “+ Add Source”) had inconsistent handling for Y-axis targets. The primary handler used negRecording=true for Y-axis targets (resulting in ShouldAutoInvert being routed through the axisPositive branch â UP press = non-inverted); while the extra-source handler did not, causing the !axisPositive branch to run (meaning the same UP press = inverted). Now, both record buttons on a Y-axis row treat an UP press as non-inverted and a DOWN press as inverted.
Joystick-class devices now traverse the legacy-XML pipeline
BuildOneSlotFromLegacy previously filtered devices by CapType == Gamepad (21) before migrating them. Joystick-class devices (CapType 20 â DirectInput arcade sticks, racing wheels, flight sticks, throttles) were excluded from constructing MappingSets. As a result, a slot with three contributing devices (e.g., UltraStik + Xinmotek + Xbox Series X) only retained the Gamepad sources; mappings authored by the user on joystick devices were lost.
The predicate has been expanded to include the complete controller-class set (Gamepad + Joystick + Driving + Flight + FirstPerson + Supplemental) â matching the criteria already utilized by DeviceService.AutoEnableHidingDefaults. Mouse, Keyboard, and Touchpad remain excluded to prevent a keyboard’s outdated auto-mapped gamepad descriptor from affecting a migrated row.
To recover a backup that lost devices due to the previous filter, simply restore the pre-migration PadForge.xml and relaunch using v3.3.2 â the joystick-class devices will populate the MappingSet upon this load.
