https://bugs.winehq.org/show_bug.cgi?id=46803
--- Comment #4 from Rafael Augusto patoplc@live.com --- Created attachment 63827 --> https://bugs.winehq.org/attachment.cgi?id=63827 Diablo 1 error logs with WINEDEBUG=+all
I created a clean WINEPREFIX, set to 32-bit winxp. This did not work, but at least I managed to get the log for install errors that happen ("Ran out of global variables"), as well as for the actual Diablo 1 launch with WINEDEBUG=+all. Since these files are huge, I had to put them in a .tar.xz so that I could upload them here.
Also, upon some investigation, I realized that the author of the custom wined3d.dll, Yegor Timoshenko, says Wine Staging 3.20+ does not play well with his DLL. As of today, the latest available version is 4.2 for his DLL, so I cannot test it with my Wine install until he makes a 4.3 version of his DLL.
He also changed his repo from GitHub to GitLab: https://gitlab.com/yegortimoshenko/wined3d.dll.
Lastly, in the README for this repo, Mr. Timoshenko suggests using GDI as a renderer for the 1996 Diablo:
wine REG ADD HKEY_CURRENT_USER\Software\Wine\AppDefaults\Diablo.exe\Direct3D /V DirectDrawRenderer /T REG_SZ /D gdi
I do not know whether he is aware of the new GOG version of how his DLL might interface with it. I will be submitting this version to the AppDB as "Garbage" for now, until people have more information on needed fixes.