August 2025 - Wine-GitLab - list.winehq.org

[PATCH v6 0/1] MR8605: winebus: Do not touch autocenter on device reset and stop all effects
by Tomasz Pakuła Aug. 6, 2025

Aug. 6, 2025

FFB Autocenter introduced in https://gitlab.winehq.org/wine/wine/-/merge_requests/4911 had one major misunderstanding. The USB PID standard doesn't actually define any explicit way to autocenter a device. One could of course use the spring effect with a deadzone of 0 and dead band of 0. This is what I'm actually working on for the Linux PID driver (spring + friction/damper). Some devices implement autocenter in firmware when they receive the DC Disable Actuators command. Very few, if not just one, implement this weird autocenter effect on slot 1. This is, from what I can gather, only implemented on the MS SideWinder joystick(s) and the Windows' USB PID driver is created around these devices. Windows PID driver is a bit out of spec, is quite permissive when it comes to fields missing in the descriptor (basically, only effect types and their effect type blocks are optional). Another thing it does is handling of this out-of-spec autocentering for their joysticks. Funnliy enough, the creator of the Linux PID driver based the initial code on testing with MS Sidewinder so it's autocentering is supported. This is where the autocentering mentioned in the MR comes from. It's not the directinput api that does it but the Windows PID driver. As such, autocentering on reset should be left to the drivers, not handeled by Wine. SDL lacks full reset support and Linux is even more barebones, whre it's not even possible to query the device state, effects etc (something I'm working on slowly). As such, when games send out RESET to prepare the device, the device starts autocentering for no good reason and the effect is not removed once other effect are uploaded and played which would be the case for MS sidewinder. In any case, even Windows in inconsistent and I think the directinput documentation has some errors. directinput ffb api is largely based on USB PID but: ![image](/uploads/6548386550b874d2e5548f35f7fe76b0/image.png) ![image](/uploads/851484a555c744c6791d48b3fd194e91/image.png) Testing with my Moza Racing R9 wheelbase, the DC Reset PID command is sent, but there's no DC Disable Actuators in sight. The games still call reset then enable actuators though. tl;dr Set autocentering to 0 instead of max value when DISFFC_RESET is received to remove the unwanted autocenter behavior. Signed-off-by: Tomasz Pakuła <tomasz.pakula.oficjalny(a)gmail.com> -- v6: winebus: Do not touch autocenter on device init and device reset https://gitlab.winehq.org/wine/wine/-/merge_requests/8605

2 2

[PATCH v5 0/1] MR8605: winebus: Do not touch autocenter on device init, device reset and stop all effects
by Tomasz Pakuła Aug. 6, 2025

Aug. 6, 2025

FFB Autocenter introduced in https://gitlab.winehq.org/wine/wine/-/merge_requests/4911 had one major misunderstanding. The USB PID standard doesn't actually define any explicit way to autocenter a device. One could of course use the spring effect with a deadzone of 0 and dead band of 0. This is what I'm actually working on for the Linux PID driver (spring + friction/damper). Some devices implement autocenter in firmware when they receive the DC Disable Actuators command. Very few, if not just one, implement this weird autocenter effect on slot 1. This is, from what I can gather, only implemented on the MS SideWinder joystick(s) and the Windows' USB PID driver is created around these devices. Windows PID driver is a bit out of spec, is quite permissive when it comes to fields missing in the descriptor (basically, only effect types and their effect type blocks are optional). Another thing it does is handling of this out-of-spec autocentering for their joysticks. Funnliy enough, the creator of the Linux PID driver based the initial code on testing with MS Sidewinder so it's autocentering is supported. This is where the autocentering mentioned in the MR comes from. It's not the directinput api that does it but the Windows PID driver. As such, autocentering on reset should be left to the drivers, not handeled by Wine. SDL lacks full reset support and Linux is even more barebones, whre it's not even possible to query the device state, effects etc (something I'm working on slowly). As such, when games send out RESET to prepare the device, the device starts autocentering for no good reason and the effect is not removed once other effect are uploaded and played which would be the case for MS sidewinder. In any case, even Windows in inconsistent and I think the directinput documentation has some errors. directinput ffb api is largely based on USB PID but: ![image](/uploads/6548386550b874d2e5548f35f7fe76b0/image.png) ![image](/uploads/851484a555c744c6791d48b3fd194e91/image.png) Testing with my Moza Racing R9 wheelbase, the DC Reset PID command is sent, but there's no DC Disable Actuators in sight. The games still call reset then enable actuators though. tl;dr Set autocentering to 0 instead of max value when DISFFC_RESET is received to remove the unwanted autocenter behavior. Signed-off-by: Tomasz Pakuła <tomasz.pakula.oficjalny(a)gmail.com> -- v5: winebus: Do not touch autocenter on device init and device reset https://gitlab.winehq.org/wine/wine/-/merge_requests/8605

4 23

[PATCH 0/1] MR8719: winegstreamer: Only add the capsfilter for avdec_h264.
by Brendan McGrath (＠redmcg) Aug. 6, 2025

Aug. 6, 2025

avdec_h264 will fail when combined with h264parse and a drain request is made during caps neg. To fix this, a capsfilter was added to force a stream-format of byte-stream for all h.264 decoders. However, this introduced a new issue with the vtdec element, as it only supports the avc stream-format. Therefore, this patch looks to address both problems by only introducing the capsfilter when the avdec_h264 element is used. It also removes the stream-format and alignment requirements from the parsed caps, applying them only to the capsfilter. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8719

3 3

[PATCH v2 0/1] MR8713: widl: Fix crash while replacing type parameters for arrays.
by Vibhav Pant (＠vibhavp) Aug. 6, 2025

Aug. 6, 2025

Fixes a crash with parameterized interfaces that have methods containing array argument(s). ``` namespace Test { interface ITest1<T>; [ uuid(006735f5-5f5d-4c39-9106-e1821b4caf04) ] interface ITest1<T> { void Method1([in] int a, [out, retval, size_is(a)]T *v); } declare { interface ITest1<int>; } } ``` widl: ../tools/widl/typegen.c:378: enum typegen_type typegen_detect_type(const type_t *, const attr_list_t *, unsigned int): Assertion `0' failed. -- v2: widl: Fix crash while replacing type parameters for arrays. https://gitlab.winehq.org/wine/wine/-/merge_requests/8713

3 2

[PATCH 0/6] MR8720: winedmo: Miscellaneous fixes.
by Rémi Bernon Aug. 6, 2025

Aug. 6, 2025

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/8720

1 6

Re: [PATCH v5 0/7] MR8690: widl: Various metadata fixes
by Rémi Bernon Aug. 6, 2025

Aug. 6, 2025

Crap, my turn to ignore the test results this time. Turns out that something in adc7014a26b22a60c45cf230ac71516b6091825f broke various tests. There's a suspicious `0124:err:ole:reg_get_typelib_module Could not get version value?` in the output. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8690#note_112182

1 0

Re: [PATCH v2 0/1] MR8532: winegstreamer: Force h264parse to output 'au' aligned byte-stream.
by Brendan McGrath (＠redmcg) Aug. 5, 2025

Aug. 5, 2025

On Tue Aug 5 16:25:54 2025 +0000, Tim Clem wrote: > Oh no worries - thanks for hashing this out with me. That version does > the trick, of course. Thanks for testing. I've raised this as MR !8719. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8532#note_112178

1 0

[PATCH 0/1] MR8717: po: update Polish translation
by Adam Markowski (＠AMark) Aug. 5, 2025

Aug. 5, 2025

Small changes. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8717

2 1

[PATCH v2 0/7] MR8715: opengl32: Use generated wow64 thunks for context functions.
by Jacek Caban (＠jacek) Aug. 5, 2025

Aug. 5, 2025

-- v2: opengl32: Use generated wow64 thunk for wglCreateContextAttribsARB. opengl32: Use generated wow64 thunk for wglCreateContext. opengl32: Avoid unneeded wrapper return type casts. opengl32: Use manual_win_functions for wglGetCurrentReadDCARB. https://gitlab.winehq.org/wine/wine/-/merge_requests/8715

2 7

[PATCH 0/7] MR8715: opengl32: Use generated wow64 thunks for context functions.
by Jacek Caban (＠jacek) Aug. 5, 2025

Aug. 5, 2025

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/8715

3 9