http://bugs.winehq.org/show_bug.cgi?id=27630
Summary: Vampire The Masquerade: Bloodlines: Regression causes graphics corruption Product: Wine Version: 1.3.23 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: companheiro.vermelho@gmail.com CC: stefan@codeweavers.com
Created an attachment (id=35323) --> (http://bugs.winehq.org/attachment.cgi?id=35323) Screenshot showing the corruption
Vampire The Masquerade: Bloodlines runs perfectly on wine-1.3.22, but in wine-1.3.23, there is a corruption, specially in the menu but also in the game.
After a git bissect, the appointed culprit is commit 68b15bc5ffe6ddf5d08cbc13479eaf718ad5e39f
Author: Stefan Dösinger stefan@codeweavers.com Date: Tue Apr 19 21:24:26 2011 +0200
wined3d: Give GL_ARB_map_buffer_range another try.
See the attached screenshot for an example of the corruption. It is actually pretty hard to capture a screenshot of the corruption because it keeps flashing and changing between the correct image and the corrupted image.
I'm not using any override, but, as it should be obvious, I'm using ARB (on regedit, the key "UseGLSL" is "disabled"). Without setting this the game barely runs.
Running Ubuntu 11.04 i386 with a ATI Radeon HD 5450 card and using proprietary driver fglrx version 8.84.6.
According to glxinfo, this driver has the GL_ARB_map_buffer_range extension, but apparently it is broken...
http://bugs.winehq.org/show_bug.cgi?id=27630
Eduardo companheiro.vermelho@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
http://bugs.winehq.org/show_bug.cgi?id=27630
--- Comment #1 from Eduardo companheiro.vermelho@gmail.com 2011-06-28 00:46:19 CDT --- Sorry about spam, but I would like to confirm that reverting the patch from the current git and recompiling indeed does solve the problem.
http://bugs.winehq.org/show_bug.cgi?id=27630
Stefan Dösinger stefandoesinger@gmx.at changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |stefandoesinger@gmx.at
--- Comment #2 from Stefan Dösinger stefandoesinger@gmx.at 2011-06-28 05:50:49 CDT --- Hmm yeah, there used to be a bug in this regression on fglrx. Do you have a Nvidia card with this extension to test this game there?
I'm away from home right now, but when I'm back I'll see if the driver bug is what I suspect(incorrect handling of the GL_MAP_UNSYNCHRONIZED_BIT flag) and report it to AMD.
http://bugs.winehq.org/show_bug.cgi?id=27630
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wylda@volny.cz
--- Comment #3 from Wylda wylda@volny.cz 2011-06-28 14:26:53 CDT ---
Do you have a Nvidia card with this extension to test this game there?
Hi Stefan, i can't confirm for nVidia. Menu is displayed correctly here in both cases (UseGLSL set to enable and disable).
OpenGL renderer string: GeForce GT 240/PCI/SSE2 OpenGL version string: 3.3.0 NVIDIA 275.09.07 OpenGL shading language version string: 3.30 NVIDIA via Cg compiler OpenGL extensions: ... GL_ARB_half_float_vertex, GL_ARB_imaging, GL_ARB_instanced_arrays, GL_ARB_map_buffer_range, GL_ARB_multisample, GL_ARB_multitexture, GL_ARB_occlusion_query, GL_ARB_occlusion_query2, ...
http://bugs.winehq.org/show_bug.cgi?id=27630
Roman m01brv@mail.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |m01brv@mail.ru
--- Comment #4 from Roman m01brv@mail.ru 2011-06-29 04:47:08 CDT --- This bug affects DeusEx http://appdb.winehq.org/objectManager.php?sClass=version&iId=3775
After the game started, press Esc to call the main menu, then go to the Load menu. After that I see crazy blinking artifacts in the Load dialog and sometimes in the whole screen picture (especially when I try to actively move the mouse).
Reverting the commit identified here fixes the issue. I have Intel video card.
http://bugs.winehq.org/show_bug.cgi?id=27630
Wylda wylda@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |i30817@gmail.com
--- Comment #5 from Wylda wylda@volny.cz 2011-07-01 05:15:24 CDT --- *** Bug 27665 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=27630
Prokhor trycatchwiki@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #6 from Prokhor trycatchwiki@gmail.com 2011-07-02 19:22:39 CDT --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=27630
--- Comment #7 from Eduardo companheiro.vermelho@gmail.com 2011-07-05 01:48:54 CDT --- Today I installed the Open Source ATI driver and the bug did NOT occur (however the game was unplayable with ARB and some objects were invisible with GLSL, but that's another issue...).
So apparently this bug is present in fglrx and intel drivers (Roman, which card exactly are you using?). This bug should be reported to the drivers, but I have absolutely no idea on how to report it... Stefan, maybe could you write a small test case to demonstrate this bug so we can report it upstream?
Aside from reporting the bug, should the commit stay or should it be reversed while the drivers aren't fixed?
http://bugs.winehq.org/show_bug.cgi?id=27630
--- Comment #8 from Stefan Dösinger stefandoesinger@gmx.at 2011-07-05 02:48:50 CDT --- Writing a test for fglrx is on my todo list, maybe today or tomorrow. I have a rough idea what may be wrong, but that'd no guarantee that my test is going to work. Catching timing bugs in stripped down test cases is very difficult.
Usually we don't reverse commits because of broken drivers. In this case however we have a separate problem on nvidia cards, and we already disabled GL_ARB_map_buffer_range once.
http://bugs.winehq.org/show_bug.cgi?id=27630
--- Comment #9 from Roman m01brv@mail.ru 2011-07-06 04:44:19 CDT --- (In reply to comment #7)
So apparently this bug is present in fglrx and intel drivers (Roman, which card exactly are you using?).
It's integrated Mobile Intel GL960 Express Chipset (GMA X3100).
http://bugs.winehq.org/show_bug.cgi?id=27630
--- Comment #10 from Roman m01brv@mail.ru 2011-07-08 04:04:36 CDT --- I have some extra info. I use in my DeusEx a more modern D3D9 driver then its default D3D (seemingly 7th) and the D3D9 section in the settings file DeusEx.ini contains the following line:
BufferTileQuads=True
If I set this to False, the bug is largerly suppressed (although not completely eliminated). Now there is no corruption of the text inside the Load dialog, but the whole screen still gets corrupted for a few seconds. Apparently this occures when the green blurred "Ion Storm" logo is moving behind the dialog window (it's part of the starting animation). When it moves away, the corruptions go away too.
Maybe, there is another D3D9 setting that can remove the rest of the corruptions.
When I use the standard D3D driver, the bug seem not to occur.
http://bugs.winehq.org/show_bug.cgi?id=27630
--- Comment #11 from Stefan Dösinger stefandoesinger@gmx.at 2011-07-26 16:47:18 CDT --- Henri sent a patch fixing some issues with that extension on fglrx. Can you retest?
http://bugs.winehq.org/show_bug.cgi?id=27630
--- Comment #12 from Eduardo companheiro.vermelho@gmail.com 2011-07-27 00:35:54 CDT --- Yes! Current GIT is fixed for me! Waiting for confirmation to close the bug. Nice work guys!
http://bugs.winehq.org/show_bug.cgi?id=27630
--- Comment #13 from paulo i30817@gmail.com 2011-07-27 02:25:52 CDT --- Confirmed from the wine apt repository update (wine-1.3.25)
http://bugs.winehq.org/show_bug.cgi?id=27630
--- Comment #14 from Roman m01brv@mail.ru 2011-07-27 03:22:41 CDT --- (In reply to comment #11)
Henri sent a patch fixing some issues with that extension on fglrx. Can you retest?
Is this patch in the last issued version (1.3.25) or in the git?
http://bugs.winehq.org/show_bug.cgi?id=27630
Stefan Dösinger stefandoesinger@gmx.at changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #15 from Stefan Dösinger stefandoesinger@gmx.at 2011-07-27 03:24:48 CDT --- reported fixed
http://bugs.winehq.org/show_bug.cgi?id=27630
--- Comment #16 from Roman m01brv@mail.ru 2011-07-28 03:54:59 CDT --- Although the bug is already closed I confirm that my problems are fixed too (in 1.3.25)
http://bugs.winehq.org/show_bug.cgi?id=27630
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #17 from Alexandre Julliard julliard@winehq.org 2011-08-05 12:37:55 CDT --- Closing bugs fixed in 1.3.26.