https://bugs.winehq.org/show_bug.cgi?id=54775
Bug ID: 54775
Summary: alt-tab not working when playing osu!
Product: Wine
Version: 8.5
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winex11.drv
Assignee: wine-bugs(a)winehq.org
Reporter: nellodegregoris66(a)gmail.com
Distribution: ---
Created attachment 74266
--> https://bugs.winehq.org/attachment.cgi?id=74266
logs from launching the game (until x11drv error)
Hello, ever since I updated Wine to 8.0-rc4 (and later versions, as this
happens for latest 8.5 staging too) I've had problems to alt-tab when playing
osu!, as the game would stay focused without having the possibility to switch
to other windows.
Logs show a certain error when alt-tabbing in x11drv, the exact logs are in the
file attached.
This doesn't happen with previous Wine vers. (ex. 7.16).
I've also tried other few games, and the same happens with osu!Lazer.exe too.
Note that this happens on X11 and Wayland too (with XWayland).
Steps to reproduce are:
- Set "Hide Wine Version" in winecfg (this allows proper fullscreen for osu!)
- Launch the game
Thanks in advance for the help!
--
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=54830
Bug ID: 54830
Summary: HITMAN (2016) needs
d3d12_pipeline_state_GetCachedBlob() implementation
Product: vkd3d
Version: 1.7
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Crashes after a while with
vkd3d:fixme:d3d12_pipeline_state_GetCachedBlob iface 000000000C5C36E0, blob
0000000030D6FA20 stub!
1.7-70-g8ed74377
--
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=53295
Bug ID: 53295
Summary: HITMAN 3 crashes on launch (needs
D3D12_FEATURE_DATA_D3D12_OPTIONS6)
Product: vkd3d
Version: 1.4
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: vkd3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
fixme:d3d12_device_CheckFeatureSupport Unhandled feature 0x1e.
--
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=45402
Bug ID: 45402
Summary: Sniper Elite V2 benchmark tool: white texture glitch
Product: Wine
Version: 3.11
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: trivial
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: moihack.inside(a)gmail.com
Distribution: ArchLinux
Created attachment 61715
--> https://bugs.winehq.org/attachment.cgi?id=61715
Sniper Elite V2 benchmark tool - white textures glitch
You can download the free benchmark tool from here:
http://www.guru3d.com/files-details/sniper-elite-v2-benchmark-tool.html
The benchmark installs, runs and exits fine under wine.
Yet, there are some white "glitched" textures here and there while the camera
flies in the scene (see attached screenshoot).
Here is how a normal run should look:
https://www.youtube.com/watch?v=WNs3mnKAdRQ (without the glitched textures)
System: Arch Linux fully updated with wine-3.11 and Radeon HD6870 GPU.
--
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=50619
Bug ID: 50619
Summary: Sniper Elite V2 has broken rendering with OpenGL
renderer
Product: Wine
Version: 6.1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 69309
--> https://bugs.winehq.org/attachment.cgi?id=69309
example
How it looks on AMD.
wine-6.1-122-g2201ca08fb0
--
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=50616
Bug ID: 50616
Summary: Sniper Elite 3 has broken rendering with OpenGL
renderer
Product: Wine
Version: 6.1
Hardware: x86-64
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
Distribution: ---
Created attachment 69307
--> https://bugs.winehq.org/attachment.cgi?id=69307
example
When bug 50235 is for NVIDIA this one is for AMD.
wine-6.1-122-g2201ca08fb0
--
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=50235
Bug ID: 50235
Summary: Broken rendering in Sniper Elite 3
Product: Wine
Version: 5.22
Hardware: x86-64
OS: Linux
Status: NEW
Keywords: regression
Severity: normal
Priority: P2
Component: directx-d3d
Assignee: wine-bugs(a)winehq.org
Reporter: andrey.goosev(a)gmail.com
CC: matteo.mystral(a)gmail.com
Regression SHA1: 77f0149a6c99fc0289d12a788f630519d7dc49d3
Distribution: ---
Created attachment 68741
--> https://bugs.winehq.org/attachment.cgi?id=68741
example
Mix of blinking textures and lights.
--
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=43637
Bug ID: 43637
Summary: Fallout New Vegas: Crash on launch using 64-bit prefix
Product: Wine
Version: 2.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: iamtimscampi(a)gmail.com
Distribution: ---
Upon launching Fallout New Vegas (With or without New Vegas Script Extender) on
a 64-bit prefix, the game crashes after the initial splash screen.
On a 32-bit prefix, the game works as intended, without a crash.
This was tested both with Staging and regular versions of Wine, with and
without the "New Vegas Script Extender" addon.
While not necessary to play the game, a 64bit prefix is necessary for the new
version of Mod Organizer, a third party utility for the game that handles mod
loading. This crash prevents users from using the latest version of it
alongside the game.
--
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=38381
Bug ID: 38381
Summary: Fallout New Vegas (Steam Version) Crashes at Startup
on the Splash Screen
Product: Wine
Version: 1.7.40
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gordan(a)bobich.net
Distribution: ---
Created attachment 51228
--> https://bugs.winehq.org/attachment.cgi?id=51228
Fallout New Vegas Crash Backtrace
Fallout New Vegas (Steam Version) Crashes at Startup on the Splash Screen.
--
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=51730
Bug ID: 51730
Summary: Keyboard and mouse wheel do not work for Fallout
Shelter game
Product: Wine
Version: 6.16
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: aaron.w2(a)gmail.com
Distribution: ---
In Fallout Shelter 1.13.13 the keyboard does not seem to work, in addition, the
mouse wheel does not work for scrolling.
When installing I saw a crash at the end, but the game otherwise appears to
work.
This game is listed as platinum, so this must have been fairly recent. Note
that I am not running the Steam version.
--
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=49051
Bug ID: 49051
Summary: Got "rawinput:RegisterRawInputDevices Unhandled flags
0x230 for device 0" in Fallout3 and NV
Product: Wine-staging
Version: 5.7
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: avenjames(a)live.com
CC: leslie_alistair(a)hotmail.com, z.figura12(a)gmail.com
As title description I got this problem since I updated version after 5.0
stable, from 5.1 to 5.7 stable/staging/dev, the game's cursor could hardly move
and unhandled at all.
I tested version 5.7 staging as usually as I did once notice the update's
coming, but this time I got messages:
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
0061:fixme:rawinput:RegisterRawInputDevices Unhandled flags 0x230 for device 0.
I think it must be related to the problem that I have, any idea friends?
--
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.
http://bugs.winehq.org/show_bug.cgi?id=29736
Bug #: 29736
Summary: Fallout 2 crashes at "Please Stand By" screen.
Product: Wine
Version: 1.3.37
Platform: x86
OS/Version: Linux
Status: UNCONFIRMED
Severity: major
Priority: P3
Component: -unknown
AssignedTo: wine-bugs(a)winehq.org
ReportedBy: mister_a(a)aol.com
Classification: Unclassified
Created attachment 38588
--> http://bugs.winehq.org/attachment.cgi?id=38588
FO2 in terminal
Look at attachments if you want to see the backlogs.
--
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
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=53792
Bug ID: 53792
Summary: Doorstop: builtin winhttp.dll is loaded instead of
native
Product: Wine
Version: 7.18
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: kubastaron(a)hotmail.com
Distribution: ---
Repro:
1. Download TestGame from
https://github.com/BepInEx/TestGame/releases/download/latest/TestGame.Mono.…
(or any other unity game) and extract it
2. Download doorstop from
https://github.com/NeighTools/UnityDoorstop/releases/download/v4.0.0/doorst…
and extract `x86/winhttp.dll` (or `x64/winhttp.dll` if your game is 64-bit)
next to `TestGame.exe`
3. Run `TestGame.exe`
On Windows it will create a `doorstop_*.log` file and start the game, but wine
will just start the game without running doorstop at all because it loads a
builtin winhttp.dll.
A working workaround is to set WINEDLLOVERRIDES="winhttp=n,b".
A potential solution is to make wine prefer native winhttp.dll like so:
> diff --git a/dlls/winhttp/Makefile.in b/dlls/winhttp/Makefile.in
> index 97266fbc92a..eb3618a0e5e 100644
> --- a/dlls/winhttp/Makefile.in
> +++ b/dlls/winhttp/Makefile.in
> @@ -3,6 +3,8 @@ IMPORTLIB = winhttp
> IMPORTS = uuid jsproxy user32 advapi32 ws2_32
> DELAYIMPORTS = oleaut32 crypt32 secur32 iphlpapi dhcpcsvc
>
> +EXTRADLLFLAGS = -Wb,--prefer-native
> +
> C_SRCS = \
> cookie.c \
> handle.c \
This is essentially the same bug as
https://bugs.winehq.org/show_bug.cgi?id=47053, but that one was using forked
doorstop and was specific to beat saber.
$ sha1sum doorstop_win_verbose_4.0.0.zip TestGame.Mono.Windows.2020.3.22f1.zip
ddb2de0fb15b7739127dd12b519c011182f7a628 doorstop_win_verbose_4.0.0.zip
943f40919616181ddf0555b77098ec94d1483f76 TestGame.Mono.Windows.2020.3.22f1.zip
--
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=48754
Bug ID: 48754
Summary: Fallout New Vegas sound glitch\crackling\missing
Product: Wine
Version: 5.0
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: quartz
Assignee: wine-bugs(a)winehq.org
Reporter: avenjames(a)live.com
As title mentioning,
the audio effect missing or crackling sometimes,
the console showing
"
0071:fixme:qtdatahandler:myComponentRoutineProc unhandled select 0x28
0071:fixme:qtsplitter:QT_Process_Movie QuickTime cannot handle media
type(-2048)
"
these line happening continuously,
any idea to fix?
--
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=40838
Bug ID: 40838
Summary: I am able to install the Launcher. however as soon as
installation/updates are complete, the window crashes
into a small box at the upper right corner of my
screen, then crashes comepletely after that
Product: Wine
Version: 1.9.11
Hardware: x86
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ak11(a)cox.net
Distribution: ---
Created attachment 54811
--> https://bugs.winehq.org/attachment.cgi?id=54811
NO THIS IS NOT THE SAME CASE AS bug 40628....the logs are different
I am able to install the Launcher. however as soon as installation/updates are
complete, the window crashes into a small box at the upper right corner of my
screen, then crashes comepletely after that.
Any ideas? I hope its an easy fix, i almost have it working!
--
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=44211
Bug ID: 44211
Summary: Wine (2.21) doesn't work anymore on any game on
FreeBSD
Product: Wine
Version: 2.21
Hardware: x86-64
OS: FreeBSD
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: adrien_fernandes2(a)hotmail.com
Created attachment 59990
--> https://bugs.winehq.org/attachment.cgi?id=59990
Output of AC with csmt
FreeBSD/amd64 11.1 (the release version in december 2017)
Wine staging 2.21 32 bits (built from a 32 bits chroot)
nVidia 765m (nvidia-driver-384.59)
12 GB RAM (even if 32 bits applications take less, you have the information)
from my 32 bits chroot, I installed the nVidia driver
libGL.so -> libGL-NVIDIA.so.1
libGL.so.1 -> libGL-NVIDIA.so.1
libGLESv2.so -> libGLESv2-NVIDIA.so.2
libGLESv2.so.2 -> libGLESv2-NVIDIA.so.2
It always worked that way four months ago (last time I was on my computer)
So actually I tried Streets of Rogue and Assassin's Creed. I copy the output of
AC so you can see what the terminal says me. I set CSMT on one try and disabled
it on the second. (Assassin's Creed always worked in the past, that's why I
give you its output)
--
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.
http://bugs.winehq.org/show_bug.cgi?id=35234
Bug ID: 35234
Summary: Fallout: New Vegas launcher crashes when selecting a
DLC by double click
Product: Wine
Version: 1.7.9
Hardware: x86
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: gyebro69(a)gmail.com
Classification: Unclassified
Created attachment 46995
--> http://bugs.winehq.org/attachment.cgi?id=46995
terminal output
I browsed Bugzilla's already closed and currently opened bug reports related to
Fallout: New Vegas/Fallout 3, but haven't find anything similar to this. It's
not a new bug because I can reproduce it with Wine 1.4.1, 1.6.1, 1.7.9 as well.
The problem: when you start Fallout:New Vegas, the launcher offers an option
named <Data Files> where you can enable/disable the installed DLCs. If I
double-click on the name of the DLC, Wine produces a crash as can be seen in
the attached log.
Single clicking on the name of the DLC doesn't produce the crash.
This was tested with a clean wineprefix, without any dll overrides, dwrite and
gameoverlayrenderer already disabled.
Fedora 19 x86
X.Org X Server 1.14.4
Nvidia binary drivers 325.15
--
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=51260
Bug ID: 51260
Summary: KINGDOM HEARTS HD 1.5+2.5 ReMIX: Black Screen at
launch
Product: Wine
Version: 6.9
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: jakobdev(a)gmx.de
Distribution: ---
Created attachment 70134
--> https://bugs.winehq.org/attachment.cgi?id=70134
The terminal output while running
Launching KINGDOM HEARTS HD 1.5+2.5 ReMIX only results in a black screen. The
Game can be found here:
https://www.epicgames.com/store/de/p/kingdom-hearts-hd-1-5-2-5-remix. It was
launched using Legendary launcher with wine.
--
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=50601
Bug ID: 50601
Summary: gave this error when running application with wine
Product: Wine
Version: unspecified
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: benjaminlihao(a)gmail.com
Distribution: ---
Created attachment 69289
--> https://bugs.winehq.org/attachment.cgi?id=69289
backtrace error
I basically used the wine to open an application but when I opened it, the
application crashed and gave me an 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=52010
Bug ID: 52010
Summary: %USERPROFILE% environment variable gets ignored
Product: Wine
Version: 6.21
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: docmax(a)gmx.de
Distribution: ---
i created a little batch file where %USERPROFILE% is set and when the app
starts it writes into that dir. this works in windows but in wine it gets
ignored (writing to c:\Users\user\...).
how can this be fixed?
--
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=53582
Bug ID: 53582
Summary: The Bat! macro has different results for %DATE on
Windows and in wine
Product: Wine
Version: 7.15
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: mywine(a)schiermeier-it.de
Distribution: ---
I got a strange effect in the application TheBat! which I maintain in AppDB:
Some Background:
TheBat! has an internal macro system to automate for example templates for
mails and so on. This macro system has a function called %DATE. As a parameter,
I can provide a "d" for the day on a date like this %DATE("ddd"). Three "d"s is
for the abbreviated weekday name. So "Saturday" gives me "Sa".
The Problem:
In Windows 10 64bit this %DATE("ddd") (or also possible: %DATE="ddd") results
in: Sa, which is ok.
On top of wine this %DATE("ddd") results in "Sa.", which means there is a dot
behind the uppercase letter S and the lowercase letter a.
This is really interesting, but not ok. The added point is the problem.
To get deeper into this problem and provide more info to you please give me
some input...
--
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=45575
Bug ID: 45575
Summary: Skyrim: No controller input when multiple controllers
are connected
Product: Wine
Version: 3.13
Hardware: x86-64
OS: Mac OS X
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: -unknown
Assignee: wine-bugs(a)winehq.org
Reporter: ahyattdev(a)icloud.com
Skyrim works fine when I have one wired Xbox 360 controller plugged in but when
I have another one also plugged into my machine that I am not using neither
controller works with the game.
I have tested what the behavior is on Windows and Skyrim works fine when
multiple Xbox controllers are connected. When running through Wine none of the
controllers give any input.
--
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=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.