http://bugs.winehq.org/show_bug.cgi?id=55981
Matthew mawesome960@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mawesome960@gmail.com
--- Comment #17 from Matthew mawesome960@gmail.com --- This seems to be the thread for the issue I ran into earlier this week trying to get the Warcraft 3 map editor running. It's a 32-bit application that uses DirectX9, I was using the version from version 1.30 of the game (downloaded off the Hive and using my old CD keys).
Running without dxvk resulted in the application getting around two frames per second and being borderline unusable. The logs contained a fixme "Doing a copy of a mapped buffer (expect performance issues)", which I traced to unix_wgl.c in the opengl32 dll wine source code. If that's the same root cause as other issues in this thread, it sounds unavoidable for now.
Using DXVK caused the application to crash shortly after opening with a "DxvkMemoryAllocator: Memory allocation failed" message in the logs; research suggested that was related to 32-bit applications running out of address space for vulkan objects and was essentially unavoidable for my situation.
I eventually got the application working by making a fresh win32 wine prefix and running under that. It ran fine and it works for me for now.
Mostly posting this because I saw the recent Brodie Robertson youtube video "Maybe Fedora Linux Was Right All Along" which raised the possibility of all gaming being funneled through WoW64, and wanted to bring up the warcraft 3 world editor as an example of software for which that still doesn't work and workarounds like dxvk also don't work. The video was ambiguous over whether win32 Wine prefixes would be dropped entirely; I got the impression they weren't but wasn't sure.