https://bugs.winehq.org/show_bug.cgi?id=51791
Bug ID: 51791
Summary: Unity 2019.4.29f1m, 2019.4.9f1 and 2019.2.17f1
(probably others) mess up the controller mapping
Product: Wine
Version: 6.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: braiamp(a)gmail.com
Distribution: ---
When games use 2019.4.29f1m, 2019.4.9f1 or 2019.2.17f1 (older than 2019.2.17f1
seems to be not affected), they detect the wrong mapping. Dpad only detects
Left/Right as Up/Down and L/R triggers as Left/Right dpad. Is very likely a
issue with the Unity engine, but Proton 5.13 correctly handles these
situations. Changing the type of controller from Xbox to PS4 gets you different
mapping but less functional.
This affects the following games:
- Subnautica
- Subnautica Below Zero
- Death's Door
The affected versions of Unity were taken from each of these games.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48582
Bug ID: 48582
Summary: PlayStation Now: Controllers aren't detected with
Microsoft's native xinput1_3.dll
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: minor
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: devilj(a)outlook.pt
Distribution: ---
Xbox One controllers (at least) aren't detected when using Microsoft's native
xinput1_3.dll, but they are working fine when using Wine's built-in version.
I captured a log using Wine's BUILT-IN implementation, but it doesn't say much.
The program polls "XInputGetStateEx" to get the state of indices 0 and 1:
004d:trace:xinput:XInputGetStateEx (index 0, state 0842FEB0)!
004d:trace:xinput:XInputGetStateEx (index 1, state 0842FEB0)!
And the respective +relay (using only the built-in module):
0040:Call xinput1_3.XInputGetStateEx(00000000,07edfeb0) ret=0048d99d
0040:Ret xinput1_3.XInputGetStateEx() retval=00000000 ret=0048d99d
0040:Call xinput1_3.XInputGetStateEx(00000001,07edfeb0) ret=0048d99d
0040:Ret xinput1_3.XInputGetStateEx() retval=0000048f ret=0048d99d
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46151
Bug ID: 46151
Summary: XInput support doesn't support rumble on the DS4 (at
least)
Product: Wine
Version: unspecified
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: xinput
Assignee: wine-bugs(a)winehq.org
Reporter: epigramx(a)yahoo.com
Distribution: ---
That would be a neat feature and it's lacking right now. All Xbox Controllers
support two motors on the device. It appears that currently Wine doesn't
provide that data to applications. I was interested in the DS4 specifically out
of the box but I support the feature may be missing on the actual Xbox
controllers as well.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=45688
Bug ID: 45688
Summary: Gamepad appears both as dinput and xinput (eg.
Valkyria Chronicles)
Product: Wine
Version: 3.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: directx-dinput
Assignee: wine-bugs(a)winehq.org
Reporter: gabriel.corona(a)enst-bretagne.fr
Distribution: ---
AFAIU, on Windows a gamepad appears either on DirectInput or on XInput.
Some games are helpful and automatically work with both. For example, Valkyria
Chronicles apparently automatically switches between DirectInput and Xinput
based on the latests input.
On Wine >= 3.3, every gamepad appears both on DirecrInput and XInput. This is
useful because the gamepad can work both on DirectInput and XInput gamed.
However, on Valkyria Chronicles (for example) the effect is that the game
switches randomly between the two modes because it apparently sees the same
gamepad from both APIs. This can be seen because the buttons displayes on
screen change from numbered key labels ("1", "2", "3", etc.) and XInput based
key labels ("A", "B", "C", "D").
In order to sucessfully run the game, I has to disable the gamepad from
DirectInput (using "wine control"). This works, but prevents running
DirectInput only games without reconfiguration.
A possible workaround would be to have an option to disable DirectInput
gamepads if both libraries are mapped in the same process.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52371
Bug ID: 52371
Summary: Horizon Zero Dawn : Gamepad not recognized
Product: Wine
Version: 7.0-rc5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: hid
Assignee: wine-bugs(a)winehq.org
Reporter: berillions(a)gmail.com
Distribution: ---
Created attachment 71561
--> https://bugs.winehq.org/attachment.cgi?id=71561
+timestamp,+pid,+seh,+debugstr,+loaddll,+hid,+hidp,+xinput,+dinput,+plugplay
log
Hi,
With wine-7.0-rc5, my gamepad (XBox Series) is not recognized in-game - I tried
with wireless or wired mode and in both cases, the pad does not work.
On Win11, the gamepad is automatically recognized, no need to modify controller
in settings.
Tried with Proton-6.3 outside Steam and same issue.
Thanks,
Maxime
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=44086
Bug ID: 44086
Summary: HiDPI: Consider evaluating `GDK_SCALE` for default DPI
size
Product: Wine
Version: 2.0.3
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: pmenzel+bugs.winehq.org(a)molgen.mpg.de
Distribution: ---
Opening the Wine configuration on a HiDPI monitor, the fonts are very small.
Despite having the user to increase the DPI size under the tab *Graphics*,
environment variables like `GDK_SCALE` [1] should be evaluated, and the default
DPI number be adjusted accordingly.
[1] https://wiki.archlinux.org/index.php/HiDPI
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=38749
Bug ID: 38749
Summary: Left 4 Dead: text in terminal is unreadable
Product: Wine
Version: 1.7.44
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ilya-valeev(a)yandex.ru
Distribution: ---
Created attachment 51666
--> https://bugs.winehq.org/attachment.cgi?id=51666
Log
When I call terminal (`), I cant read some text (see screenshot). Font tips
from here:
https://appdb.winehq.org/objectManager.php?sClass=version&iId=19444
doesnt help.
Tried wine 1.6.2, 1.7.42 and 1.7.44. Debian 8. 1920x1080
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=48666
Bug ID: 48666
Summary: Left 4 Dead 2: freezes during loading when shader
detail set to higher than medium
Product: Wine
Version: 5.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jhopper(a)safe-mail.net
Distribution: ---
Created attachment 66522
--> https://bugs.winehq.org/attachment.cgi?id=66522
wine console output
only freezes when vulkan renderer used (DXVK) GL working fine, there used to be
a problem with this when GL was used in previous versions of wine but I
couldn't find that specific bug in the list
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=43040
Bug ID: 43040
Summary: steam version of Left 4 Dead 2 v2.1.4.7 prevents
connection to server with a 'client timed out' error
Product: Wine
Version: 2.7
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: manoa(a)manoa.flnet.org
Distribution: ---
the bug occurs usually on the second attempt to connect to a server
in addition, once the error occurs it will persist, even after steam is
restarted
if not trying to connect to a server for a couple of minutes it may allow
connection, but if that connection fails, the next connection will have the
error
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=37158
Bug ID: 37158
Summary: Left 4 Dead pressing tab crashes the game
Product: Wine
Version: 1.6.2
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: nothingmuchheretosay(a)gmail.com
Pressing tab in a game, whether in Single or Multiplayer mode, the game will
crash.
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.