https://bugs.winehq.org/show_bug.cgi?id=46148
--- Comment #16 from Zebediah Figura z.figura12@gmail.com --- Kevin, I'm sorry things are difficult for you. Rest assured they are difficult for us too.
I have never built Wine from source, and am unlikely to be able to do so soon. If there is an apt-get command to get a version without that patch, I'll happily test that. Or if someone can provide a build they want me to test, with installation instructions, I can do that. If I had clear build instructions (including how to omit the patch in question) I could even give that a shot; but I find the instructions on the web site to be a nearly impenetrable maze of alternatives, with conditions for choosing a path and instructions for what to do often using jargon that means nothing to me.
Well, it'd be nice to know what in specific is difficult to understand about the build instructions, rather than a generic "it's an impenetrable maze of alternatives". I won't deny that they could use improvement, but, being on the other side of all of the jargon, I don't really know how.
Staging build instructions exist here: https://wiki.winehq.org/Wine-Staging. In this case you'd want to use the '--all -W wined3d-Improved_RCP_Support' options to patchinstall.sh. Yes, these instructions more clearly could use improvement (and visibility), but we only have so much time on our hands (and we prefer to spend it developing).
Anyway, since this seems to be the easiest way we'll get through this, I've compiled 32- and 64-bit wined3d.dll.so libraries with the RCP patch reverted:
http://www.cs.grinnell.edu/~figuraze/wined3d-bug-46148.tar.gz
Please try replacing your existing wined3d.dll.so with these (backing them up first, I imagine, and replacing the -32/-64 extension as appropriate). Hopefully this will work.