http://bugs.winehq.org/show_bug.cgi?id=19010
Summary: W40K soulstorm regression from 1.1.23 to 1.1.24 : building are partly invisible Product: Wine Version: 1.1.24 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d AssignedTo: wine-bugs@winehq.org ReportedBy: sebastien.fievet@free.fr
Created an attachment (id=21906) --> (http://bugs.winehq.org/attachment.cgi?id=21906) trace generated with WINEDEBUG=+wine_d3d,+d3d
A regression was introduced by v1.1.24. It is visible from the login screen, and in game.
-The login screen displays the selected army's commander. With 1.1.24 his torso is invisible. Only the head, and members are rendered correctly. With 1.1.23 it works just fine.
-In game, with 1.1.24, buildings core is invisible. Only the boundaries are rendered correctly. With 1.1.23 it works just fine.
attached are 2 traces generated with WINEDEBUG=+wine_d3d,+d3d wine Soulstorm.exe. Wine was stopped after displaying the login screeN.
http://bugs.winehq.org/show_bug.cgi?id=19010
--- Comment #1 from Séb sebastien.fievet@free.fr 2009-06-20 05:30:59 --- Created an attachment (id=21907) --> (http://bugs.winehq.org/attachment.cgi?id=21907) trace generated with WINEDEBUG=+wine_d3d,+d3d
http://bugs.winehq.org/show_bug.cgi?id=19010
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression Summary|W40K soulstorm regression |W40K soulstorm: buildings |from 1.1.23 to 1.1.24 : |are partly invisible |building are partly | |invisible |
--- Comment #2 from Jeff Zaroyko jeffz@jeffz.name 2009-06-20 05:39:31 --- please post the results of your regression test http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=19010
--- Comment #3 from Séb sebastien.fievet@free.fr 2009-06-20 15:40:16 --- If i correctly did the regression testing, the "bad" commit should belong to Stephan Dösinger :
[b2f09fd20421d0a5e179b42332ca63bc5ac17d8a] wined3d: Emulate clipplanes in ARB if the NV extensions are not available.
Hope this helps!
http://bugs.winehq.org/show_bug.cgi?id=19010
--- Comment #4 from Jeff Zaroyko jeffz@jeffz.name 2009-06-22 03:44:28 --- does the patch from bug 19002 fix the issue?
http://bugs.winehq.org/show_bug.cgi?id=19010
--- Comment #5 from Séb sebastien.fievet@free.fr 2009-06-22 16:56:35 --- (In reply to comment #4)
does the patch from bug 19002 fix the issue?
yes, the one liner suggested by Stephan Dösinger fixed it.
http://bugs.winehq.org/show_bug.cgi?id=19010
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #6 from Ken Sharp kennybobs@o2.co.uk 2009-06-22 17:28:33 --- Duplicate.
*** This bug has been marked as a duplicate of bug 19002 ***
http://bugs.winehq.org/show_bug.cgi?id=19010
Ken Sharp kennybobs@o2.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Ken Sharp kennybobs@o2.co.uk 2009-06-22 17:30:31 --- Closing.
A regression test before opening this bug, as instructed, would have avoided this duplicate.
http://bugs.winehq.org/show_bug.cgi?id=19010
--- Comment #8 from Séb sebastien.fievet@free.fr 2009-06-23 03:45:16 --- (In reply to comment #7)
Closing.
A regression test before opening this bug, as instructed, would have avoided this duplicate.
Considering I : - took time to generate debug traces with 2 versions of wine, - ran the regressions test after being requested to do so, - tested a one line patch by copy-pasting in the source code - reported this patch actually fixes my issue,
I hardly understand what allows you to add such a useless comment, which doesn't solve anything. I am gratefull to Jeff Zaroyko to answer first. HIS comments were helpful.
http://bugs.winehq.org/show_bug.cgi?id=19010
--- Comment #9 from Austin English austinenglish@gmail.com 2009-06-23 11:00:28 --- (In reply to comment #8)
(In reply to comment #7)
Closing.
A regression test before opening this bug, as instructed, would have avoided this duplicate.
Considering I :
- took time to generate debug traces with 2 versions of wine,
- ran the regressions test after being requested to do so,
- tested a one line patch by copy-pasting in the source code
- reported this patch actually fixes my issue,
I hardly understand what allows you to add such a useless comment, which doesn't solve anything. I am gratefull to Jeff Zaroyko to answer first. HIS comments were helpful.
While those things are appreciated, it took time for Jeff to ask those questions of you, which you should've done already. The whole thing could've been avoided had you done the test *first*, as the instructions said.
It wasn't meant to be chastising, rather something to keep in mind for next time.