https://bugs.winehq.org/show_bug.cgi?id=46803
Bug ID: 46803 Summary: Diablo 1 GOG.com crash Product: Wine Version: 4.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: xzgamertag@mail.com Distribution: ---
Created attachment 63823 --> https://bugs.winehq.org/attachment.cgi?id=63823 Log
Diablo crashes immidiately after skipping intro, while using hi-res, latest version. When I try to run Diablo (Classic) version, it requires original CD to proceed.
https://bugs.winehq.org/show_bug.cgi?id=46803
xzgamertag@mail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Ubuntu
https://bugs.winehq.org/show_bug.cgi?id=46803
Olivier F. R. Dierick o.dierick@piezo-forte.be changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick@piezo-forte.be Severity|major |normal
--- Comment #1 from Olivier F. R. Dierick o.dierick@piezo-forte.be --- Bug triage notification: Issue in one application is normal. Read severity description in: https://wiki.winehq.org/Bugs#severity
Please provide full terminal output: https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a._terminal...
Have you tested the workarounds from the AppDB for retail version of the game? https://appdb.winehq.org/objectManager.php?sClass=version&iId=3498 They are : winxp mode and/or custom wined3d.dll. Note that workarounds are not fixes. Please report if they make a difference, but leave the bug open in any case.
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.
https://bugs.winehq.org/show_bug.cgi?id=46803
--- Comment #3 from Rafael Augusto patoplc@live.com --- Sorry for the double post, but I forgot to comment that setting the Wine mode to Windows XP did nothing to solve the issue. I did not test the custom dll yet.
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.
https://bugs.winehq.org/show_bug.cgi?id=46803
pattietreutel katyaberezyaka@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |katyaberezyaka@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=46803
Anders Nylander nylander.anders@yandex.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nylander.anders@yandex.com
--- Comment #5 from Anders Nylander nylander.anders@yandex.com --- Note that it's possible, with caveats, to start the game when using a Wayland compositor (The hi-res, latest version that is), though this is likely a lucky coincidence of various factors, like Wayland protocol security rules preventing the game from swapping modes, which makes it possible for the game to display the splash screen after the initial video, followed by the game intro, followed by the game menu. There are other rendering bugs that, er, renders the game unplayable in this state, though that's different from this bug.
If however, I enable the virtual desktop feature in winecfg and set it to 640x480 (native game res) then start the game, it crashes immediately when skipping the first intro video. This is the same issue that xzgamertag is running into.
So it's likely related to how the game behaves when swapping between different modes for the purpose of playing videos vs. rendering the splash screen and main menu.
https://bugs.winehq.org/show_bug.cgi?id=46803
Ivan ivan88@centrum.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |ivan88@centrum.cz
--- Comment #6 from Ivan ivan88@centrum.cz --- Classic version somewhat runs. I usually create prefix with winetricks -q directplay vcrun2005 vcrun2008 vcrun2010 vcrun2012 vcrun2013 vcrun2015 msxml3 ie8, but I doubt any of these is required. Anyway, set Windows version to 10, install GOG setup.exe. Then, to get around no CD error, use mkisofs to create ISO with DIABDAT.MPQ on it (original retail CD may work too), mount it. Then set renderer to GDI and enable virtual desktop (e.g. winetricks ddr=gdi vd=640x480). Launch Diablo.exe from install root (not from dx subdirectory, that appears to be the enhanced version) and while it sometimes crashes, usually it does not and it is possible to play. Of course, menu options are invisible and moreover layout depends on whether there are characters created or not, but you can learn it on Windows.
Battle.net (this mode seems unavailable in enhanced version) requires open port 6112, i.e. most people will have to set port forwarding on their ADSL/cable/whatever modem/router. Battle.net UI is partially visible. IPX/SPX does not seem to work. Now obviously IPX/SPX is dead, but back in the day it was used to start effectively single player session with multiplayer character that could be used later on Battle.net.
https://bugs.winehq.org/show_bug.cgi?id=46803
Georg georg.schuemann@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |georg.schuemann@web.de
--- Comment #7 from Georg georg.schuemann@web.de --- I can confirm this on wine 5.0.4-staging.
However I wanted to try the wined3d workaround, which only compiles for wine-4.0.2-stable (afaik). So I compiled a 32 bit 4.0.2 wine.
When using wine4.0.2 with the self compiled wined3d I get a buffer overflow, once the intros end, however if I use wine4.2 without the custom wined3d I actually get in the menu (which is a black screen). But when you Alt-TAB out of the game it actually shows in the preview Windows (at least in GNOME3) how the menu looks like, so you can navigate with the keyboard. The actual game starts and seems to be working fine, except that it looks horrible with a widescreen resolution :(
So maybe this bug was added in some wine version, I guess I can test a few, to check in which one it first occurred.
https://bugs.winehq.org/show_bug.cgi?id=46803
Paul Gofman gofmanp@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |gofmanp@gmail.com
--- Comment #8 from Paul Gofman gofmanp@gmail.com --- While I can't understand exactly what this bug is about from the above discussion, maybe my comment here for the similar bug (https://bugs.winehq.org/show_bug.cgi?id=48788#c2) can help to structure these issues somehow.
https://bugs.winehq.org/show_bug.cgi?id=46803
Saulius K. saulius2@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |saulius2@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=46803
mike homerhomer@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |homerhomer@gmail.com
--- Comment #9 from mike homerhomer@gmail.com --- I was able to play the game after
1. Setting ddraw.dll to native 2. Installing times32 font
The title screen is mess but seems to play okay once in the game.
https://bugs.winehq.org/show_bug.cgi?id=46803
Alexander Vereeken Alexander88207@Protonmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Alexander88207@Protonmail.c | |om
--- Comment #10 from Alexander Vereeken Alexander88207@Protonmail.com --- (In reply to mike from comment #9)
I was able to play the game after
- Setting ddraw.dll to native
- Installing times32 font
The title screen is mess but seems to play okay once in the game.
Thank you!
-
wine-bugs＠winehq.org -
WineHQ Bugzilla