https://bugs.winehq.org/show_bug.cgi?id=46148
--- Comment #5 from Zebediah Figura z.figura12@gmail.com --- (In reply to Kevin Grittner from comment #4)
(In reply to Zebediah Figura from comment #3)
Well, it'd be nice to know if this is a Staging bug or a regression in upstream Wine. As far as I am aware WoW needs several Staging patches to run, but if these are known then the most helpful thing to do would be to compile Staging with only those patches, and check if the regression is still present.
I'm not clear on whether you are requesting that I try this, or suggesting to the Wine developers. I've never built Wine from source, so it might take a bit to get set up for that.
Well, I certainly can't, as I don't have the game ;-)
Unless of course there is any intuition from the D3D developers as to what might have changed.
I was hoping that someone would have some idea what changes in this Wine Staging release might cause this.
If I did, I would have shared them. As things stand, we haven't really made any modifications to d3d-related patches (or, IIRC, any patches?) that would have caused this regression. On the other hand, we may have messed up a rebase somewhere.
I think it's probably more likely that something was broken upstream, but I have no intuition as to what that might be, as this seems to be a D3D bug and I have not worked on that area. Hence my request for comment from the D3D developers.
Hopefully this staging release will be held back from GA until this is resolved.
I'm not sure what you mean by GA, but given the wide field of applications that Wine (and by extension Wine-Staging) supports, we don't defer releases for a regression in one of them.