[Bug 43761] World of Warcraft d3d11 textures rendering regression and other... Wine Staging 2.17

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=43761

--- Comment #4 from zefkerr <zefkerrigan at gmail.com> ---
Created attachment 59284
  --> https://bugs.winehq.org/attachment.cgi?id=59284
At this point the game totally hung on the progress bar and I had to kill the
process.

When I run the game in d3d11 mode from a terminal it normally starts up and
works, but it instantly hangs completely, as soon as at least the edge of the
broken textures appears on the screen.  If you run the game through a shortcut,
and not through the terminal, then the game does not hang when a broken
textures appears on the screen. And if I left the game when there were broken
textures within sight, then when I entered the game, I generally will not see
the image in the game any further than the progress bar, because in this case
the game hangs up every time when you enter the game world progress bar reaches
100%. I repeat, under the same conditions the game does not hang if it was
launched via a shortcut. The game hangs only if it was launched via the
terminal.
Please note that not all textures are broken, but only some of their individual
varieties. For example, if we draw an analogy, then after upgrading to Wine
Staging 2.17 in Witcher 3, the textures of the surface of the ground, stones on
the ground, paths, etc. appeared. But, at the same time, similar textures
disappeared in WoW. I do not presume to say whether this can be related to the
recent innovation or not:
https://dev.wine-staging.com/patches/186/

-- 
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.