https://bugs.winehq.org/show_bug.cgi?id=46803
Rafael Augusto patoplc@live.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |patoplc@live.com
--- Comment #2 from Rafael Augusto patoplc@live.com --- Created attachment 63825 --> https://bugs.winehq.org/attachment.cgi?id=63825 Crash log for the GOG.com version of Diablo I
I can confirm the bug also happens for me. Tried several display modes to no avail. I also tried winetricks d3dx9 and d3dcompiler_43, but not the custom wined3d.dll.
Either way, if the custom dll has some content that can solve the problem in Wine, maybe there could be a way to add this to the staging dlls instead of a game-specific one. (Although I am completely inexperienced in the internal subjects of Wine dlls and have no idea how difficult it would be.)
Also, the version available on GOG is said to be patched to work with modern OSs, unlike the 1990s version that was the only one available prior to this week's GOG launch of Diablo 1.
I will attach my exception log to this thread as well. Terminal output doesn't show much, but I do get a GUI-based stack trace.
My OS for this attempt was Linux Mint 19.1, 64-bit, on an old HP Pavilion dv6 laptop with an ATI Mobility Radeon HD 4570. Wine version used was 4.3-staging.
I believe the new GOG version should be added to the AppDB, as it is distinct from previous ones.