- wine-gitlab - winehq.org

Re: [PATCH v2 0/4] MR7448: Use _NSGetExecutablePath to get the binary path on macOS - approved
by Alexandre Julliard (＠julliard) 03 Mar '25

03 Mar '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7448

1 0

Re: [PATCH v2 0/3] MR7450: wbemprox: Get Win32_VideoController values from the registry. - approved
by Alexandre Julliard (＠julliard) 03 Mar '25

03 Mar '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7450

1 0

Re: [PATCH v2 0/3] MR7394: Remove pre-macOS 10.12 workarounds - approved
by Alexandre Julliard (＠julliard) 03 Mar '25

03 Mar '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7394

1 0

Re: [PATCH v2 0/1] MR7444: make_unicode: Generate the PostScript builtin font metrics. - approved
by Alexandre Julliard (＠julliard) 03 Mar '25

03 Mar '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7444

1 0

Re: [PATCH v2 0/1] MR7454: msvcr120: Simplify feupdateenv implementation. - approved
by Alexandre Julliard (＠julliard) 03 Mar '25

03 Mar '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7454

1 0

Re: [PATCH v8 0/1] MR7369: include/security.h: Add definition of NEGOSSP_NAME - approved
by Alexandre Julliard (＠julliard) 03 Mar '25

03 Mar '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7369

1 0

Re: [PATCH v4 0/2] MR7443: d2d1/tests: Add some tests for device context handling in the DC target. - approved
by Alexandre Julliard (＠julliard) 03 Mar '25

03 Mar '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7443

1 0

Re: [PATCH v3 0/1] MR7458: kernelbase/tests: Skip test if EnumSystemFirmwareTables is not available. - approved
by Alexandre Julliard (＠julliard) 03 Mar '25

03 Mar '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7458

1 0

[PATCH 0/2] MR7465: winegstreamer: Validate the value of cbSize in aac decoder.
by Brendan McGrath (＠redmcg) 03 Mar '25

03 Mar '25

This MR fixes a mf:transform test that started failing as a result of MR !7417. It also adds new tests to mf:transform to test different values of `MF_MT_USER_DATA` against the aac decoder. It adds validation of `cbSize` to the aac decoder, which, in addition to fixing the previous test, allows some of these new tests to pass. But it does not validate the content of the user data (as the new tests seem to indicate Windows does). -- https://gitlab.winehq.org/wine/wine/-/merge_requests/7465

4 7

[PATCH v6 0/7] MR7422: winebus/dinput: Support arbitrary number of axes in the virtual PID descriptor
by Tomasz Pakuła (＠TomaszPakula) 03 Mar '25

03 Mar '25

Related Wine issue: https://bugs.winehq.org/show_bug.cgi?id=52714 I'm starting work on updating/extending Linux force feedback API and one of my goals is to expose the number and an array that contains the device's ffb-enabled axes. As I'm mainly working with USB PID driver, I already have a POC of obtaining this data. What prompted this is that currently Wine always creates virtual joysticks with two PID ffb axes. This causes issues with [Richard Burns Rally](https://github.com/ValveSoftware/Proton/issues/6702#issuecomment-267…, as this game incorrectly initializes a `CONSTANT_FORCE` effect with all the FFB axes that contain `DIDOI_FFACTUATOR` flag and then trying to update `cAxes` and `rgdwAxes` values which leads to `DIERR_INVALIDPARAM`. Now, this flag is set by wine while enumerating virtual device's axes and while `(axis index < FFB axes)`, flag is applied. This means, that every device which has FFB functionality and at least two axes, will report FFB on `X`, `Y`. While updated API would mean a lot of steering wheels would correctly report only 1 axis, a lot of USB PID wheels still include `X` and `Y` in their `AXES_ENABLE` and `DIRECTION` usages. This, again, would lead to broken FFB (in affected games). On Windows, there's a possibility of overwriting some joystick capabilities with registry entries, which ends up removing `DIDOI_FFACTUATOR` flag from a selected axis. This doesn't work in Wine. This MR allows Wine to add an arbitrary number (up to `PID_AXES_MAX`) of axes to the PID descriptor, based on the value of Haptic Axes from SDL or from Linux FF api in the future (I'm working on it). Additionally, to work around RBR and other games with similar, wrong FFB handling, I introduced a [hint](https://github.com/libsdl-org/SDL/issues/12341) to SDL that allows a dynamic overwrite of the number of haptic axes. For the Linux API, I'll figure out a nice way to override when the number of axes will be exposed. With these changes, I was able to successfully get force feedback on my Moza Racing R9 with all axes usable. With additional traces in the dinput code, I confirmed that with one axis defined in the PID descriptor, the game created a constant force effect with just one axis and `cAxes = 1`. -- v6: https://gitlab.winehq.org/wine/wine/-/merge_requests/7422

3 10

2025

2024

2023

2022

wine-gitlab