http://bugs.winehq.org/show_bug.cgi?id=17639
Summary: FEAR 1.08: Geometry errors / zbuffer precision problems Product: Wine Version: 1.1.16 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: liquid.acid@gmx.net CC: jb.faq@gmx.de
Encountering various graphical artifacts with FEAR 1.08.
Something that looks like random (garbage) polygons, which sometime pop in in the scene. Then artifacts that affect the floor and look like zbuffer precision issues.
Going to post some screenshots later.
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #1 from Tobias Jakobi liquid.acid@gmx.net 2009-03-15 13:24:26 --- Created an attachment (id=19969) --> (http://bugs.winehq.org/attachment.cgi?id=19969) geometry errors (1)
notice the polygon in the scene that doesn't belong there
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #2 from Tobias Jakobi liquid.acid@gmx.net 2009-03-15 13:24:41 --- Created an attachment (id=19970) --> (http://bugs.winehq.org/attachment.cgi?id=19970) geometry errors (2)
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #3 from Tobias Jakobi liquid.acid@gmx.net 2009-04-19 10:33:19 --- Reconfirming with wine-1.1.19
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #4 from Tobias Jakobi liquid.acid@gmx.net 2009-04-19 15:43:58 --- Created an attachment (id=20557) --> (http://bugs.winehq.org/attachment.cgi?id=20557) z-fighting on the floor
Notice the short black lines and dots on the floor. The effect is more apparant when in motion.
I think this visual errors are related to these FIXMEs: fixme:d3d:state_zfunc D3DCMP_NOTEQUAL and D3DCMP_EQUAL do not work correctly yet fixme:d3d:state_clipping Clipping not supported with vertex shaders
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #5 from Tobias Jakobi liquid.acid@gmx.net 2009-06-14 15:28:35 --- Reconfirming the geometry errors with a fresh wine git master (wine-1.1.23 doesn't work for and exists early for most 3D applications).
However I'm now on a Radeon HD3200 (integrated, RS780 chipset). I'm going to get a cheap NV card soon, so I can also continue tracking this issue on nvidia hardware. However currently it looks like that it doesn't really matter on which hardware/driver the game is run.
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #6 from Austin English austinenglish@gmail.com 2010-06-04 13:21:49 --- Does the demo have the same problem? http://www.gamershell.com/download_10167.shtml
is this still an issue in current (1.2-rc2 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #7 from Tobias Jakobi liquid.acid@gmx.net 2011-01-08 17:32:49 CST --- Just tested the demo (which finally works for me) and the random polygons still pop up here and there.
wine-1.3.10 mesa, libdrm and xf86-video-intel git master xorg-server-1.9.2.902
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #8 from Simon Beer simon.beer@gmx.de 2011-02-06 03:17:16 CST --- Created an attachment (id=33171) --> (http://bugs.winehq.org/attachment.cgi?id=33171) The not correctly working state_zfunc in Tomb Raider Legend
Tomb Raider Legend seems to be affected by that bug, when next gen effects enabled, too.
Console gives me a fixme:d3d:state_zfunc D3DCMP_NOTEQUAL and D3DCMP_EQUAL do not work correctly yet.
And everythings flickering
wine 1.3.13, Geforce 460, Driver 260.19.36
http://bugs.winehq.org/show_bug.cgi?id=17639
Simon Beer simon.beer@gmx.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.beer@gmx.de
--- Comment #9 from Simon Beer simon.beer@gmx.de 2011-02-06 04:07:46 CST --- Found something:
http://www.winehq.org/pipermail/wine-patches/2007-September/043856.html http://www.winehq.org/pipermail/wine-cvs/2007-September/036127.html
Seems to be a more major bug (feature lack) which may affect other applications as well.
So maybe there should be a non app specific bug entry to prevent dub entries.
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #10 from Tobias Jakobi liquid.acid@gmx.net 2011-02-06 08:34:06 CST --- See also bug #13869, which tracks a similar issue. Again it could be related to zbuffer precision.
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #11 from Henri Verbeet hverbeet@gmail.com 2011-02-06 08:41:17 CST --- I'm pretty sure this is another instance of a certain nvidia depth invariance bug, although they don't see it that way.
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #12 from Simon Beer simon.beer@gmx.de 2011-02-06 10:54:14 CST --- (In reply to comment #11)
I'm pretty sure this is another instance of a certain nvidia depth invariance bug, although they don't see it that way.
Is this a hardware, software or driver related bug? With my 9800gt i've the same problems.
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #13 from Henri Verbeet hverbeet@gmail.com 2011-02-06 11:07:56 CST --- (In reply to comment #12)
(In reply to comment #11)
I'm pretty sure this is another instance of a certain nvidia depth invariance bug, although they don't see it that way.
Is this a hardware, software or driver related bug? With my 9800gt i've the same problems.
I'm not sure if it's a hardware or driver issue, but nvidia's response was essentially that it's an optimization. This affects nv50 and newer cards, which includes 9800GT. Bug 24630 and the last couple of comments in bug 6351 are the same problem, where it's interesting to note that comment 84 from bug 6351 claims this happened in the Windows D3D driver at some point as well, but was fixed there.
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #14 from Tobias Jakobi liquid.acid@gmx.net 2011-02-06 11:13:56 CST --- @Henri: Please note that I'm currently testing this on a Intel GPU, so it doesn't seem to be limited to nvidia.
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #15 from Henri Verbeet hverbeet@gmail.com 2011-02-06 11:20:21 CST --- (In reply to comment #14)
@Henri: Please note that I'm currently testing this on a Intel GPU, so it doesn't seem to be limited to nvidia.
Actually, to clarify, that's just the z-fighting here and in e.g. TRL. The geometry corruption looks like a separate bug that could be a Wine bug.
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #16 from Tobias Jakobi liquid.acid@gmx.net 2011-02-06 11:32:54 CST --- I have all these problems on the Intel too: 1) Geometry errors / random polygons popping up (I have the impression that these polygons are part of certain shadow volumes) [in FEAR] 2) z-fighting [in FEAR] 3) z-fighting [in Splinter Cell]
Plus my "ants" problem (see https://bugs.freedesktop.org/show_bug.cgi?id=33066), which isn't a wine bug, but an issue in the intel driver (probably optimization pass related) that is triggered by wine's GLSL code (more specifically the fragment shader parts).
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #17 from Tobias Jakobi liquid.acid@gmx.net 2011-02-23 09:52:54 CST --- Interesting observation: After the latest changes to mesa git master the FEAR engine seems to work perfectly on my Radeom HD4750@r600g. Please note that this is currently with DX8 shaders enabled. Even more interesting is that I can't spot any of these geometry errors and z-fighting that I could see on my nVidia and Intel card. Visuals are on the same level as running the game on a native system.
http://bugs.winehq.org/show_bug.cgi?id=17639
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #18 from joaopa jeremielapuree@yahoo.fr 2012-06-10 17:57:18 CDT --- INVALID, then?
http://bugs.winehq.org/show_bug.cgi?id=17639
--- Comment #19 from joaopa jeremielapuree@yahoo.fr 2013-04-14 23:51:56 CDT --- Surely, this bug can be closed as UPSTREAM
http://bugs.winehq.org/show_bug.cgi?id=17639
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED CC| |focht@gmx.net Resolution|--- |UPSTREAM
--- Comment #20 from Anastasius Focht focht@gmx.net --- Hello folks,
--- quote --- After the latest changes to mesa git master the FEAR engine seems to work perfectly on my Radeom HD4750@r600g. --- quote ---
--- quote --- Surely, this bug can be closed as UPSTREAM --- quote ---
Thanks, resolving 'upstream' then.
Regards
https://bugs.winehq.org/show_bug.cgi?id=17639
Bruno Jesus 00cpxxx@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #21 from Bruno Jesus 00cpxxx@gmail.com --- Closing resolved upstream problem.
-
wine-bugs＠winehq.org