[Bug 42588] New: Vietcong - graphics glitches since Wine 2.1
https://bugs.winehq.org/show_bug.cgi?id=42588 Bug ID: 42588 Summary: Vietcong - graphics glitches since Wine 2.1 Product: Wine Version: 2.1 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: minor Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: havran.jan(a)email.cz Distribution: ArchLinux Created attachment 57517 --> https://bugs.winehq.org/attachment.cgi?id=57517 Vietcong - terminal log In version 2.1 was introduced new bug that causes graphical glitches like flickering soldiers. I can confirm this bug in wine versions 2.1, 2.2 and 2.3. In versions 2.0 and below it worked probably fine - this bug is not 100% reproducible - sometimes soldiers are flickering and glitches are shown very often, sometimes just for few milisecond, but i am pretty sure that this was introduced in version 2.1 Tested on Intel and AMD GPUs, Vietcong 1.60 with VCStarter 1.7 Beta -- 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=42588 --- Comment #1 from Jan Havran <havran.jan(a)email.cz> --- Created attachment 57518 --> https://bugs.winehq.org/attachment.cgi?id=57518 vietcong - invisible vietcong soldier I managed to take a screenshot of flickering soldier -- 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=42588 --- Comment #2 from Jan Havran <havran.jan(a)email.cz> --- Created attachment 57519 --> https://bugs.winehq.org/attachment.cgi?id=57519 vietcong - visible vietcong soldier Screenshot showing how soldier should look like -- 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=42588 Jan Havran <havran.jan(a)email.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |havran.jan(a)email.cz -- 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=42588 --- Comment #3 from Jan Havran <havran.jan(a)email.cz> --- I tried compile wine from source (git) and figured out that this bug is caused by this patch: https://source.winehq.org/git/wine.git/commitdiff/15d53761a5fbfc12fc5f9974c0... -- 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=42588 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |15d53761a5fbfc12fc5f9974c02 | |9dace00eab33d CC| |hverbeet(a)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.
https://bugs.winehq.org/show_bug.cgi?id=42588 Béla Gyebrószki <gyebro69(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gyebro69(a)gmail.com --- Comment #4 from Béla Gyebrószki <gyebro69(a)gmail.com> --- Created attachment 57600 --> https://bugs.winehq.org/attachment.cgi?id=57600 screenshot showing glitches in the options menu (Darkstar One) The same commit causes graphical glitches in the 'Options' and 'Load game' menus in Darkstar One (GOG.com version). Most of the game options are missing (invisible). There is also flickering in the options menu. It seems only those menus are affected, I didn't encounter similar issues during game play. The problem doesn't exist with the previous commit. 15d53761a5fbfc12fc5f9974c029dace00eab33d is the first bad commit commit 15d53761a5fbfc12fc5f9974c029dace00eab33d Author: Henri Verbeet <hverbeet(a)codeweavers.com> Date: Tue Jan 31 15:47:10 2017 +0100 wined3d: Do not pin system memory in wined3d_buffer_load_location(). The demo version can be used to reproduce the problem: https://archive.org/download/DarkstarOne/Darkstar%20One.exe Darkstar One.exe (920 MB) md5sum: 479cb30712e6fa23b4dd161d26fa30e2 wine-2.3-241-gc3b108e OpenGL vendor string: NVIDIA Corporation OpenGL renderer string: GeForce GT 730/PCIe/SSE2 OpenGL core profile version string: 4.5.0 NVIDIA 378.13 -- 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=42588 --- Comment #5 from Henri Verbeet <hverbeet(a)gmail.com> --- Created attachment 57626 --> https://bugs.winehq.org/attachment.cgi?id=57626 patch Does this patch 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=42588 --- Comment #6 from Béla Gyebrószki <gyebro69(a)gmail.com> --- (In reply to Henri Verbeet from comment #5)
Created attachment 57626 [details] patch
Does this patch help?
The patch works for Darkstar One. -- 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=42588 --- Comment #7 from Jan Havran <havran.jan(a)email.cz> --- (In reply to Henri Verbeet from comment #5)
Created attachment 57626 [details] patch
Does this patch help?
I am afraid that this patch does not work for Vietcong. -- 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=42588 --- Comment #8 from Henri Verbeet <hverbeet(a)gmail.com> --- (In reply to Jan Havran from comment #7)
I am afraid that this patch does not work for Vietcong. Does the game have a demo with the same issue?
-- 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=42588 --- Comment #9 from Jan Havran <havran.jan(a)email.cz> --- (In reply to Henri Verbeet from comment #8)
(In reply to Jan Havran from comment #7)
I am afraid that this patch does not work for Vietcong. Does the game have a demo with the same issue?
In short: no. Long version: the game has demo, but because of bug 9337 it crashed after the intro of first mission. For full game I use community tool "VCStarter", which is somehow workaround for bug 9337 - unfortunatelly this tool is only for version 1.60, but demo is version 1.0. Vietcong use D3D8, but what I understand VCStarter converts D3D8 calls into D3D9 calls (among other things). In intro in demo version i did not see any glitches. Do you need to see some debug logs? -- 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=42588 --- Comment #10 from Henri Verbeet <hverbeet(a)gmail.com> --- Created attachment 57656 --> https://bugs.winehq.org/attachment.cgi?id=57656 debug patch (In reply to Jan Havran from comment #9)
Do you need to see some debug logs?
Could you verify that the attached debug patch makes the issue go away, and if it does, create a debug log with WINEDEBUG="+tid,+seh,+d3d8,+d3d9,+d3d"? -- 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=42588 --- Comment #11 from Jan Havran <havran.jan(a)email.cz> --- Created attachment 57664 --> https://bugs.winehq.org/attachment.cgi?id=57664 debug log (In reply to Henri Verbeet from comment #10)
Could you verify that the attached debug patch makes the issue go away, and if it does, create a debug log with WINEDEBUG="+tid,+seh,+d3d8,+d3d9,+d3d"?
I applied this patch (without the previous one, or should i apply it too?) on 15d53761a5fbfc12fc5f9974c029dace00eab33d and it works. I tried to make gameplay as short as possible because of 5MB attachment limit, but i believe that i "captured" behaviour where it usually make the issue. -- 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=42588 Henri Verbeet <hverbeet(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #57656|0 |1 is obsolete| | --- Comment #12 from Henri Verbeet <hverbeet(a)gmail.com> --- Created attachment 57672 --> https://bugs.winehq.org/attachment.cgi?id=57672 debug patch Nothing immediately obvious in that log unfortunately, and the fact that it isn't clear whether the issue would have occurred without the patch makes things harder. Could you create the same log with the attached patch instead? The issue is supposed to occur this time. -- 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=42588 Jan Havran <havran.jan(a)email.cz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #57664|0 |1 is obsolete| | --- Comment #13 from Jan Havran <havran.jan(a)email.cz> --- Created attachment 57679 --> https://bugs.winehq.org/attachment.cgi?id=57679 debug log Patching the file on commit 15d53761a5fbfc12fc5f9974c029dace00eab33d failed, so i patched in on commit 6a05069a43f1a8f0e69c4cedd134f8d7400b8a95. Without debug logging it works as expected - issues occurs. But with debug logging i found strange behaviour: -when i run wine with "WINEDEBUG="+tid,+seh,+d3d8,+d3d9,+d3d" with redirected logging into file - NO issues occurs (at least i didnt noticed - debug log attached), maybe it runs too slow? I have no clue... -wine with "WINEDEBUG="+tid,+seh,+d3d8,+d3d9,+d3d" with redirected logging into /dev/null - issues occurs -wine with "WINEDEBUG="+tid,+seh,+d3d8,+d3d9" (WITHOUT d3d) with redirected logging into file - issues occurs (I did not attached this log because I think it is useless without d3d debug) I also tried to redirect logging into tmpfs, but with no effect. -- 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=42588 Henri Verbeet <hverbeet(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression -- 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=42588 --- Comment #14 from Henri Verbeet <hverbeet(a)gmail.com> --- Does this still happen with current 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=42588 --- Comment #15 from Jan Havran <havran.jan(a)email.cz> --- Thanks for reminder (I wanted to test it before 3.x stable release, but I forgot on it). Seems like this bug is gone for wine-3.0rc5 (i am unable to reproduce it even for wine-2.18, which is the oldest wine version to which i am able to downgrade on my system - maybe because of the (fixed) freetype2 bug). So it was probably fixed somewhere between 2.3 and 2.18. Tested on Intel and AMD GPUs, Vietcong 1.60 with VCStarter 1.7 Beta, Mesa 17.3.1, Linux 4.14.11. -- 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=42588 Henri Verbeet <hverbeet(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #16 from Henri Verbeet <hverbeet(a)gmail.com> --- Reported 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=42588 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #17 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 3.0-rc6. -- 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=42588 Alex Henrie <alexhenrie24(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=44863 -- 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=42588 Alex Henrie <alexhenrie24(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugs.winehq.org/sho | |w_bug.cgi?id=43246 -- 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 (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla