Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

(no longer using long types)
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

Calling GetConsoleCP() when ReadConsoleW() fails (potentially indicating
that cmd.exe's instance isn't attached to a console) makes no sense.

In details, since GetConsoleCP() returns 0 when not attached to a console
to indicate error, we're in fact using CP_ACP.

So fallback explicitely to OEM CP (which is the default for CUI programs).
Signed-off-by: Eric Pouech <eric.pouech@gmail.com>

The HID PID steering wheels always declare one force feedback axis,
while the joysticks always have two or more. So it is safe to
assume that joysticks with single FFB axis are racing wheels.

Fixes FH5 not having force feedback with a Simucube 2 steering
wheel, when using the hidraw backend.

Windows.Gaming.Input on Windows always uses the X and Y axes for
FFB, ignoring what is declared in the HID report descriptor, and
the Axes Enable collection. Since we have the correct behavior
on Wine, this allows the test to complete on both platforms
without issues.

Fixes the Download method not sending an initial type specific
HID PID report in the rare cases where all type specific params
are set to 0 through the initial SetParameters call, so they aren't
considered as modified.

FH5 is affected by this issue, since it initially sets the
direction of its constant effect to 0, which translates to 0
magnitude in dinput.