http://bugs.winehq.org/show_bug.cgi?id=35675
Bug ID: 35675 Summary: Bad textures in World of Tanks Product: Wine Version: 1.7.13 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: mzettik@gmail.com
Created attachment 47636 --> http://bugs.winehq.org/attachment.cgi?id=47636 Screenshots of bad textures on tanks
I'm running World of Tanks with latest wine 1.7.13. WoT after update to 8.11 sometimes bad show textures on tanks (in garage and in game too). In 8.10 no problems. I wrote to WoT bugs, but they not officialy support linux and I cannot send info from dxdiag - not works. I test completly reinstall WoT (via Play on Linux) and still bad textures Screenshots in attachements...
http://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #1 from Marek Zettík mzettik@gmail.com --- Created attachment 47637 --> http://bugs.winehq.org/attachment.cgi?id=47637 Screenshots of bad textures on tanks
http://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #2 from Marek Zettík mzettik@gmail.com --- Created attachment 47638 --> http://bugs.winehq.org/attachment.cgi?id=47638 Screenshots of bad textures on tanks
http://bugs.winehq.org/show_bug.cgi?id=35675
Marek Zettík mzettik@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mzettik@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=35675
Jarkko K jarkko_korpi@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jarkko_korpi@hotmail.com
--- Comment #3 from Jarkko K jarkko_korpi@hotmail.com --- Wine is currently at 1.7.17
Could you upgrade? More important would be attach debug log.
You can do it via console wine gamename.exe >> debug.log 2>&1
http://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #4 from Marek Zettík mzettik@gmail.com --- 1.7.17 crashing after click on "Play" while showing fullscreen. 1.7.18 is ok, but textures no good (as in 1.7.13)...
http://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #5 from Marek Zettík mzettik@gmail.com --- Created attachment 48433 --> http://bugs.winehq.org/attachment.cgi?id=48433 log for wine 1.7.17
http://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #6 from Marek Zettík mzettik@gmail.com --- Created attachment 48434 --> http://bugs.winehq.org/attachment.cgi?id=48434 log for wine 1.7.18
Test only garage - sometimes white/blue tanks
http://bugs.winehq.org/show_bug.cgi?id=35675
A.T. xtcdj15@yahoo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xtcdj15@yahoo.com
--- Comment #7 from A.T. xtcdj15@yahoo.com --- Created attachment 48557 --> http://bugs.winehq.org/attachment.cgi?id=48557 screenshot with bugged rendering
i have the same problem since wot 9.0 update. In 9.0 Wargaming changed some texture formats, shaders, the way shadows are rendered (WG dev : "old tanks had the shadows drawn directly into the textures, while they are calculated in real time now"),etc ....something new that triger this bug in wine.
Some time texture missing (solid blue/lilac), and sometime wrong textures and ilumination is maped on the tanks.
I found a way to workaround this but it seriously cripple the performance. After playing a bit with regedit keys (http://wiki.winehq.org/UsefulRegistryKeys) I found that setting StrictDrawOrdering to "enabled" seems to solve the texture problems, but FPS go down alot.
Wine 1.7.19 nvidia GTX660 2GB VRAM, latest drivers available
http://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #8 from A.T. xtcdj15@yahoo.com --- Created attachment 48558 --> http://bugs.winehq.org/attachment.cgi?id=48558 screenshot with bugged rendering 2
wrong textures
http://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #9 from A.T. xtcdj15@yahoo.com --- Created attachment 48559 --> http://bugs.winehq.org/attachment.cgi?id=48559 screenshot with bugged rendering 3
another one with wrong textures
http://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #10 from A.T. xtcdj15@yahoo.com --- "fixme:d3d:resource_check_usage Unhandled usage flags 0x8."
this one keep repeating in wine console output.....same with StrictDrawOrdering "enabled" and with "diasbled", no other d3d related messages on console.
https://bugs.winehq.org/show_bug.cgi?id=35675
Alexander angavrilov@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |angavrilov@gmail.com
--- Comment #11 from Alexander angavrilov@gmail.com --- Since it's already 1.7.26 and nobody seems to be interested, I tried to narrow down why StrictDrawOrdering actually helps this by a simple but tedious process of commenting out the relevant checks one by one and testing if the bug reappears. The result is that the only relevant thing to this bug is the flush done in surface_upload_data; and unlike some of the others, it doesn't even seem to affect FPS. Since I have no idea how Direct3D and its Wine implementation works, I hope this information is useful to someone who does, and results in a proper fix.
In the meantime I've got myself a tiny workaround patch that seems to suppress the bug and doesn't have any measurable performance impact.
https://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #12 from Alexander angavrilov@gmail.com --- Created attachment 49589 --> https://bugs.winehq.org/attachment.cgi?id=49589 Workaround patch
It simply turns permanently on just the relevant part of StrictDrawOrdering.
https://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #13 from Alexander angavrilov@gmail.com --- Created attachment 49596 --> https://bugs.winehq.org/attachment.cgi?id=49596 log with WINEDEBUG=+d3d_surface (bzip2)
Since the patch shows the issue is somewhere in the D3D surface code, I produced a log of that as the game loads and then a couple of switches between tanks are done in hangar (this is when the bug most commonly appears). The log contains inserted comments starting with '==============' that describe what is being done.
To reduce the size of the log I filtered out very frequent repeating spam of this kind:
trace:d3d_surface:surface_invalidate_location surface 0x4e6bc28, location WINED3D_LOCATION_DISCARDED | WINED3D_LOCATION_SYSMEM | WINED3D_LOCATION_USER_MEMORY | WINED3D_LOCATION_DIB | WINED3D_LOCATION_BUFFER | WINED3D_LOCATION_TEXTURE_RGB | WINED3D_LOCATION_TEXTURE_SRGB | W. trace:d3d_surface:surface_load_location surface 0x4e6bc28, location WINED3D_LOCATION_RB_MULTISAMPLE. trace:d3d_surface:surface_load_location Location already up to date. fixme:d3d:wined3d_debug_location Unrecognized location flag(s) 0xfffffc00.
and
trace:d3d_surface:surface_modify_ds_location surface 0x4e6c150, new location 0x100, w 1280, h 1024.
https://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #14 from Alexander angavrilov@gmail.com --- Created attachment 49597 --> https://bugs.winehq.org/attachment.cgi?id=49597 log filtered for only surface_upload_data
Furthermore, if you filter the log specifically for the calls to surface_upload_data and look at what happens when switching tanks, you can see sequences that look very much like texture uploads at different mipmap levels. Looking closer, it is evident that subsequent uploads of the same dimensions often reuse the source memory buffer address; and sometimes there are two uploads to the same surface.
If this is evidence of temporary memory buffers and possibly surfaces being reused to load multiple distinct textures in sequence, any unexpected asynchronous behavior of the actual upload, whether introduced by Wine code or the GL driver, may cause the wrong pixel data to be uploaded to a texture, leading to the exact behavior seen in this bug. The explicit pipeline flush forced by StrictDrawOrdering would suppress this race condition and the bug, as supported by tests.
https://bugs.winehq.org/show_bug.cgi?id=35675
Jaro jaromir@mailinator.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jaromir@mailinator.com
--- Comment #15 from Jaro jaromir@mailinator.com --- Your log contained WINED3DFMT_DXT1, and WINED3DFMT_DXT5, textures those shouldnt work at all with native wine.
https://bugs.winehq.org/show_bug.cgi?id=35675
Matteo Bruni matteo.mystral@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |matteo.mystral@gmail.com
--- Comment #16 from Matteo Bruni matteo.mystral@gmail.com --- (In reply to Jaro from comment #15)
Your log contained WINED3DFMT_DXT1, and WINED3DFMT_DXT5, textures those shouldnt work at all with native wine.
Jarkko, as you have already been told multiple times, please refrain from leaving comments when you have no idea of what you're talking about.
Thanks.
https://bugs.winehq.org/show_bug.cgi?id=35675
Bartosz gang65@poczta.onet.pl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gang65@poczta.onet.pl
https://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #17 from Bartosz gang65@poczta.onet.pl --- Created attachment 53585 --> https://bugs.winehq.org/attachment.cgi?id=53585 Screenshot from wine 1.8.1 and World of Tanks 0.9.13.
The issues is still exisiting with wine 1.8.1 and World of Tanks 0.9.13. Unfortunately with wine 1.9.3 the game is crashing for me, just after start.
https://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #18 from Bartosz gang65@poczta.onet.pl --- How we could proceed with this bug? Is it possible to create final fix for that?
https://bugs.winehq.org/show_bug.cgi?id=35675
Sebastian Lackner sebastian@fds-team.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sebastian@fds-team.de
--- Comment #19 from Sebastian Lackner sebastian@fds-team.de --- (In reply to Bartosz from comment #17)
Unfortunately with wine 1.9.3 the game is crashing for me, just after start.
That sounds like a regression, please open a new bug report for it.
https://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #20 from Bartosz gang65@poczta.onet.pl --- For me such texture issues happens on NVidia hardware. On Intel everything is working perfectly.
https://bugs.winehq.org/show_bug.cgi?id=35675
Max Devaine maxdevaine@volny.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maxdevaine@volny.cz
--- Comment #21 from Max Devaine maxdevaine@volny.cz --- (In reply to Bartosz from comment #20)
For me such texture issues happens on NVidia hardware. On Intel everything is working perfectly.
Hello, too bad textures, too nvidia card (GTX660)
https://bugs.winehq.org/show_bug.cgi?id=35675
Jimmy Garpehäll epaaj89@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |epaaj89@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=35675
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #22 from joaopa jeremielapuree@yahoo.fr --- Is still a bug in current wine(3.20)?
https://bugs.winehq.org/show_bug.cgi?id=35675
Christian bugs.winehq@mohk.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs.winehq@mohk.de
--- Comment #23 from Christian bugs.winehq@mohk.de --- (In reply to joaopa from comment #22)
Is still a bug in current wine(3.20)?
No, this bug is long gone.
https://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #24 from joaopa jeremielapuree@yahoo.fr --- @Christian Did you try with a Nvidia GPU. It looks like the problem occurred with such a GPU.
https://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #25 from Christian bugs.winehq@mohk.de --- (In reply to joaopa from comment #24)
@Christian Did you try with a Nvidia GPU. It looks like the problem occurred with such a GPU.
I use an NVIDIA GeForce GTX 750 Ti with 396.54 and have no graphical issues as described in the original post.
https://bugs.winehq.org/show_bug.cgi?id=35675
--- Comment #26 from joaopa jeremielapuree@yahoo.fr --- Good news. Reported fixed then. Can an administrator close this bug as FIXED.
https://bugs.winehq.org/show_bug.cgi?id=35675
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED
--- Comment #27 from Jeff Zaroyko jeffz@jeffz.name --- Reported fixed.
https://bugs.winehq.org/show_bug.cgi?id=35675
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #28 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 3.21.