[Bug 59631] New: wine-staging-11.6: flickering images in Battle.net Launcher
http://bugs.winehq.org/show_bug.cgi?id=59631 Bug ID: 59631 Summary: wine-staging-11.6: flickering images in Battle.net Launcher Product: Wine-staging Version: 11.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: -unknown Assignee: wine-bugs@list.winehq.org Reporter: dimich.dmb@gmail.com CC: leslie_alistair@hotmail.com, z.figura12@gmail.com Distribution: --- Created attachment 80699 --> http://bugs.winehq.org/attachment.cgi?id=80699 Wine console output Images in Battle.net Launcher flicker with wine-staging-11.6. The issue does not occur with wine-staging-11.5. The issue does not occur with mainline wine-11.6. (Additional patch is required to run Battle.net Launcher with non-staging wine: https://bugs.winehq.org/show_bug.cgi?id=56486). Probably related parts of wine-staging-11.6 output: 0248:fixme:dxgi:dxgi_factory_CreateSwapChainForComposition iface 02BBB6F0, device 02BA0060, desc 005FEBE0, output 00000000, swapchain 538594DC stub! 0248:fixme:dxgi:wined3d_swapchain_desc_from_dxgi Ignoring alpha mode 0x1. 0248:fixme:d3d:wined3d_swapchain_init The application requested more than one back buffer, this is not properly supported. Please configure the application to use double buffering (1 back buffer) if possible. 0248:fixme:d3d:wined3d_swapchain_init Unimplemented swap effect 0x3. 0248:fixme:dxgi:d3d11_swapchain_GetDesc Ignoring ScanlineOrdering and Scaling. 0248:fixme:dxgi:d3d11_swapchain_SetColorSpace1 iface 02CFFD48, colour_space 0 stub! 0248:fixme:dxgi:d3d11_swapchain_Present1 Ignored present parameters 005FE7A0. 0248:fixme:dxgi:dxgi_device_EnqueueSetEvent iface 02BA0038, event 000002D0 stub! 0248:fixme:dcomp:visual_SetContent iface 00BAD2E0, content 02CFFD48 semi-stub! 0248:fixme:d3d11:d3d11_device_GetCreationFlags iface 02BA0060 stub! ... 0430:fixme:dxgi:d3d11_swapchain_GetDesc Ignoring ScanlineOrdering and Scaling. 0430:fixme:d3d11:d3d11_multithread_SetMultithreadProtected iface 02BA0088, enable 0x1 stub! 0430:fixme:dxgi:dxgi_surface_GetDC iface 0CA91058, discard 0, hdc 02D37CA4 semi-stub! ... Wine-staging-11.5 doesn't contain these lines except "d3d11_swapchain_Present1 Ignored present parameters". The issue doesn't seem to affect application functionality and looks visual only. OS: Arch Linux Kernel version: 6.19.11-arch1-1 Nvidia driver: 595.58.03 -- 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=59631 --- Comment #1 from Dmytro Bagrii <dimich.dmb@gmail.com> --- Created attachment 80700 --> http://bugs.winehq.org/attachment.cgi?id=80700 eglinfo -- 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=59631 --- Comment #2 from Dmytro Bagrii <dimich.dmb@gmail.com> --- Created attachment 80701 --> http://bugs.winehq.org/attachment.cgi?id=80701 vulkaninfo -- 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=59631 --- Comment #3 from Dmytro Bagrii <dimich.dmb@gmail.com> --- Created attachment 80702 --> http://bugs.winehq.org/attachment.cgi?id=80702 Screen record -- 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=59631 Dmytro Bagrii <dimich.dmb@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dimich.dmb@gmail.com -- 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=59631 kollardavid.kolibry@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kollardavid.kolibry@gmail.c | |om --- Comment #4 from kollardavid.kolibry@gmail.com --- I am also having issues with Battle.net on wine-staging 11.6 (Arch's build), but it's more severe than just flickering. I am unable to launch it, because I get stuck on the spinner before the main window, as if it got stuck on logging in. I am using 11.5 for the time being -- 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=59631 --- Comment #5 from Alistair Leslie-Hughes <leslie_alistair@hotmail.com> --- I cannot reproduce either issue listed here. Wayland vs X? log with +loaddll,dcomp -- 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=59631 --- Comment #6 from Dmytro Bagrii <dimich.dmb@gmail.com> --- Created attachment 80742 --> http://bugs.winehq.org/attachment.cgi?id=80742 Xorg log -- 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=59631 Dmytro Bagrii <dimich.dmb@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #80699|0 |1 is obsolete| | --- Comment #7 from Dmytro Bagrii <dimich.dmb@gmail.com> --- Created attachment 80743 --> http://bugs.winehq.org/attachment.cgi?id=80743 Log with WINEDEBUG=+loaddll,+dcomp -- 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=59631 --- Comment #8 from Dmytro Bagrii <dimich.dmb@gmail.com> --- (In reply to Alistair Leslie-Hughes from comment #5)
Wayland vs X?
Xorg 21.1.21, no compositors etc. Fluxbox window manager, but the same behavior with no any window manager.
log with +loaddll,dcomp
Attached log with WINEDEBUG=+loaddll,+dcomp : https://bugs.winehq.org/attachment.cgi?id=80743 I would try to find what commit introduced the issue, but don't know how to bisect staging patchset efficiently. Is there a guide? -- 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=59631 --- Comment #9 from Koli <kollardavid.kolibry@gmail.com> --- Created attachment 80744 --> http://bugs.winehq.org/attachment.cgi?id=80744 Log battle.net stuck startup with loaddll & dcomp -- 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=59631 --- Comment #10 from Koli <kollardavid.kolibry@gmail.com> --- I am on Wayland, KDE. Looks like a crash loop of a background process based on how the last chunk dlls just keep repeating -- 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=59631 --- Comment #11 from Alistair Leslie-Hughes <leslie_alistair@hotmail.com> --- (In reply to Dmytro Bagrii from comment #8)
(In reply to Alistair Leslie-Hughes from comment #5)
Wayland vs X?
Xorg 21.1.21, no compositors etc. Fluxbox window manager, but the same behavior with no any window manager.
log with +loaddll,dcomp
Attached log with WINEDEBUG=+loaddll,+dcomp : https://bugs.winehq.org/attachment.cgi?id=80743
I would try to find what commit introduced the issue, but don't know how to bisect staging patchset efficiently. Is there a guide?
When applying all patches, use following command. patchinstall.py --backend=git-am --all --force-autoconf Then you can bisect as normal. -- 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=59631 mata <sutupud@yahoo.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sutupud@yahoo.com --- Comment #12 from mata <sutupud@yahoo.com> ---
When applying all patches, use following command.
patchinstall.py --backend=git-am --all --force-autoconf
Then you can bisect as normal.
Not really, since Battle.net requires staging patches to start, so to bisect successully you'd neet to start with wine-staging-11.5 already patched, that should be the first known good commit. Then rebase the changes from 11.6 on top of that, and then you can bisect with that as the first known bad commit. What I can say is that I happen to also run arch with kernel 6.19 and Nvidia 595. The launcher works with wine-staging-11.6 when using the option wine Battle.net.exe --in-process-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.
http://bugs.winehq.org/show_bug.cgi?id=59631 Maciej Stanczew <maciej.stanczew@proton.me> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maciej.stanczew@proton.me --- Comment #13 from Maciej Stanczew <maciej.stanczew@proton.me> --- I'm on KDE Plasma with Wayland, and my symptoms are that Battle.net window's contents are not rendered at all – so not sure if it's the same issue (but it does work with '--in-process-gpu', so I'm leaning towards it being the same). Bisection result: b70caa17726c3532b210a5ddf53af8024bc35b34 is the first bad commit commit b70caa17726c3532b210a5ddf53af8024bc35b34 (HEAD) Author: Alistair Leslie-Hughes <leslie_alistair@hotmail.com> Date: Sun Mar 22 22:37:38 2026 +1100 Added dcomp-DCompositionCreateDevice2 patchset Some commit combinations that I checked: 1dbc94083d1 (11.5) + 5bfda368 (11.5) = good 1dbc94083d1 (11.5) + b70caa17 = bad 6e073d28dee (11.6) + 666d822d (11.6) = bad 6e073d28dee (11.6) + 666d822d (11.6) + '-W dcomp-DCompositionCreateDevice2' = good -- 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=59631 --- Comment #14 from Dmytro Bagrii <dimich.dmb@gmail.com> --- (In reply to Alistair Leslie-Hughes from comment #11)
patchinstall.py --backend=git-am --all --force-autoconf Then you can bisect as normal.
But since the issue is introduced by one of staging patches, I have to bisect wine-staging, not wine repository itself. There are only 10 commits between 11.5 and 11.6 in wine-staging, but they add/modify multiple patches at once. (In reply to mata from comment #12)
The launcher works with wine-staging-11.6 when using the option wine Battle.net.exe --in-process-gpu
In my case '--in-process-gpu' has no effect, images still flicker. -- 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=59631 Ker noa <blue-t@web.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |blue-t@web.de --- Comment #15 from Ker noa <blue-t@web.de> --- Disabling he acceleration in bnet solves the flicker for me. -- 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=59631 --- Comment #16 from Dmytro Bagrii <dimich.dmb@gmail.com> --- (In reply to Ker noa from comment #15)
Disabling he acceleration in bnet solves the flicker for me.
Indeed, no flicker if "Use browser hardware acceleration" unchecked. And less CPU usage by CrGpuMain :) However, the window seems to redraw with longer delay after being moved or overlapped by another window. -- 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.
participants (1)
-
WineHQ Bugzilla