Skip to content

VPadConnect 0.2.1 Beta 3

Latest

Choose a tag to compare

@ArvinNotDev ArvinNotDev released this 04 Nov 19:44
· 1 commit to main since this release

VPadConnect 0.2.1 Beta 3

New Features

  • Added gyro steering support for DualShock 4.
  • Added DualShock 4 vibration and rumble support.
  • Improved DualShock 4 battery percentage and charging status detection.

Improvements

  • Improved Sony controller HID report handling.
  • Added DualShock 4-specific calibration and motion processing.
  • Preserved existing DualSense gyro, vibration, and Lightbar functionality.

Compatibility and Installer

  • Preserved existing wired DualShock 4 controls.
  • The Windows x64 Inno Setup installer continues to bundle the official
    ViGEmBus 1.22.0 installer and use the existing driver detection and
    installation flow. A working installation is detected and left in place;
    the bundled installer runs only when required.
  • The installer retains the existing selectable install folder, Start Menu
    shortcut, optional Desktop shortcut, launch option, and uninstaller. Removing
    VPadConnect does not remove the shared ViGEmBus driver.

Testing Note

DualShock 4 gyro and rumble support have not yet been tested with a physical
DualShock 4 controller.

Build and Validation

  • The project build script completed successfully with PyInstaller 6.11.1 and
    Inno Setup 6.7.4.
  • The installer includes the official ViGEmBus 1.22.0 payload. Its SHA-256
    matches the pinned project value, and its Authenticode signature is valid.
  • python -m compileall -q core ui tests main.py passed.
  • The focused DualShock 4, HID report layout, and installer orchestration
    checks passed (17 tests). The web frontend checks passed (32 tests).
  • The full Python suite reported 132 passed and 2 failed. One existing
    DualSense gyro test fixture does not set Mapper.controller_type; another
    expects the previous battery Lightbar RGB values, while the current main
    code uses the updated saturated palette.
  • Windows Sandbox is disabled in the build environment, so clean installation,
    application launch, shortcut, upgrade, and uninstall behavior could not be
    exercised in an isolated Windows environment. The installer was not run on
    the host.