# Joystick/Wheel Beta 1 — customer testing guide

## Packages and versions

Use the matching pair:
- [Windows x64 Client ZIP](https://open-stream.net/beta/joystick-beta-1/Maximizer-Client-Windows-x64-joystick-beta-1.zip)
- [Ubuntu 24.04-compatible amd64 Linux Host DEB](https://open-stream.net/beta/joystick-beta-1/Maximizer-Host-Ubuntu24.04-amd64-joystick-beta-1.deb)

Beta 1 uses the exact verified preview 5 binaries. Version labels are intentionally
`1.0.273-joystick-preview5` (Client) and `1.0.268-joystick-preview5` (Host).
The release tag's extra changes are publication automation and documentation;
application bytes are identified in `Client-BUILD-PROVENANCE.json`,
`Host-BUILD-PROVENANCE.json` and `SHA256SUMS.txt`, available from the
[OpenStream beta area](https://open-stream.net/beta.html).

## First setup

1. Connect the wheel/joystick/accessories to the Windows PC. Install the normal
   vendor driver where required and verify the controls in Windows first.
2. Install the matching Host DEB on the Linux gaming PC through its normal package
   installation process. Enable Host controller input and its normal uinput/input
   permissions.
3. Extract the Windows ZIP and run `Maximizer/Moonlight.exe` after closing another
   running Client instance.
4. Enable **Settings → Gamepad Settings → Forward joysticks and wheels (preview)**.
   Start a new stream. Standard force feedback has its own checkbox.
5. In the game, select **Maximizer Wheel/Joystick** and bind the controls. Forwarding
   is automatic, but game-specific action mapping generally needs a saved profile:
   select Steering and turn the wheel; select Accelerator/Brake/Clutch and press
   each pedal; bind gears, buttons and hats similarly. Use the driver/game settings
   for calibration, inversion and deadzones. Check Steam Input/direct joystick
   settings for the particular game if needed.

Separate USB pedals, shifters and button boxes appear separately. Ordinary supported
gamepads retain their existing gamepad mapping. Minimal generic devices may show
up to two extra always-released classification buttons; bind the real controls.

## Test scenarios

- Steering through its full range; independent pedals and combined pedal input.
- Extra buttons, short presses, all hat directions, stick twist/throttle/rudder.
- Multiple accessories together, unplug/replug, stream disconnect/reconnect.
- Focus away/back with background gamepad input disabled, then enabled.
- Input with force feedback disabled, followed by supported standard effects with
  feedback enabled. Check force direction/feel, gain and centering using game controls.
- A longer session in the intended native Linux or Proton game.

The Client requests autocenter off before closing output it controlled; physical
drivers still determine the resulting motor behavior. This is a customer beta,
with synthetic-input/SDK-boundary automated qualification rather than vendor-device
certification.

## Send a useful compatibility report

After the session, use **Settings → Gamepad Settings → Export device diagnostics**.
The report is saved in Windows Documents and contains the latest stream sample.
Include:
- Exact device model, connection and selected hardware/driver mode.
- Windows/driver versions and the displayed Client/Host versions.
- Linux distribution/kernel, game title and Proton version when applicable.
- Which controls/effects worked or failed, and the steps that reproduce a problem.
- Device diagnostics and matching Client/Host logs through the usual support channel.

## Current feature limits

Eight devices, 16 axes, 128 buttons and four hats per device; up to 16 supported
standard force-feedback effects. Proprietary TrueForce, RPM LEDs, telemetry displays
and firmware/configuration passthrough are outside this beta's supported scope.