-
Notifications
You must be signed in to change notification settings - Fork 773
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Warcraft III: Reforged crashes back to desktop #1388
Comments
Download apitrace and put the files That said, most issues with Blizzard games tend to be caused by some Battle.net settings, not by the game itself. Are you using Lutris or just a standard wine setup? Might be worth trying the Lutris installer for Battle.net since the game was known to run at some point (see this report). I'm also getting sick of Blizzard games breaking all the time at this point. They are the only ones that constantly cause nothing but headache, take every single opportunity to stop working, and 90% of the time it's not even my bug. It's also straight-up impossible to debug many of them, so the chances of me being able to do anything here are very low and I'm just not interested. I'll take an apitrace if you manage to make one, but if that turns out to be impossible, then this will be a #wontfix #dontcare #playsomethingelse. Rant over. |
The game works without issue (beyond the myriad bugs of the game itself) for me with some wine tkg 4.16 version, radv 19.3.2 and latest dxvk. To launch the game without using the bnet launcher, use the |
Thank you for this information. This is really useful. When using this trick it always seems to launch, though it prompts me with a login screen and when I login nothing happens. The "Play Offline" and the "Custom Game" functionality at least seems to work reliably this way though. |
I'm running a vanilla wine-staging-5.0 installation without lutris. I've tried the Lutris version too and causes the same issue. The game starts, shows a black screen for ~10 sec. and then shows a distorted screen for ~ 10 sec. and then crashes back to the desktop with an error. I'm sorry it's a pain in the ass and I understand your frustration of the harshness of debugging things like that. |
I've been testing launching and the executable for the last ~ 20 minutes and came to the following conclusions:
|
I've made 2 traces. One where the game launches and one where the game crashes back to the desktop. Do you have any preference in where I upload them? |
Since the crash file is only a small trace: Warcraft III Crash.trace.zip |
Just pick some reasonably sane host like Mega, Google Drive, Dropbox, ... - whatever you have access to. What I don't like are the ones that want me to download malware, click on some scam ad, or advertize porn sites. |
You just missed my upload from the crash ;) Do you need a trace from the working situation too? If so then I'll need to upload it somewhere, so then I'll need some time. |
I pretty much only need the working one since everything else is utterly and completely useless since the trace ends before the game crashed. |
It just finished uploading: https://wetransfer.com/downloads/cdcea9a1b6f8012bc46ce85d2062238920200130224414/c4b7e3bdbeea7ef57e3182c17a444af020200130224414/b2ea30 |
My rig consists of: For me no issues with Battle.net Launcher, although sometimes it happens because Blizzard changes somethings with an update probably due to changes in their QT5 setup and that gets sorted as they suddenly realize ppl also play on Linux. From the Battle.net Launcher Beside the Blizzard games I also play Hope it helps with ideas. |
I'm not having any problems with other Blizzard games. StarCraft, StarCraft II and World of Warcraft Classic always launch fine via the Battle.net application. Only Warcraft III: Reforged is giving issues. Launching the executable also doesn't always work, but when launching the executable directly it works 8/10 times and when launching it via the Battle.net application only 1/10 times, only when using DXVK. Whenever I start the executable without DXVK (using WineD3D) and then it always started consistently (tried 20+ times). |
Which distro do you use? Have you tried installing DXVK without DXGI? |
I don't blame you for not wanting to deal with this. Even on the Windows side, users are having trouble getting the game to launch. It was running fine up until a few weeks ago, and then they made a change that broke the game on Windows 8 and it has been mostly crashing on load since then. |
My experience with the new Reforged release: Tried to run on 2 different PCs, in the end was successful both times.
TLDR: Ubuntu 18.04, wine5.0-staging, DXVK 1.46 kinda works, some tweaks perhaps needed (without dxgi, running with fullscreen parameters). |
Just tried and doesn't make a difference unfortunately. |
Update: Since Battle.net.exe was still active I just tried to completely kill it and after doing so and installing dxvk-1.5.3 without-dxgi it seems to run more reliable and launch 9/10 times. Though sometimes it still hangs with just displaying a black screen and a modified mouse cursor, but that's a lot better already. What's actually the difference when using the --without-dxgi parameter? |
Installing without DXGI worked for me. I'll add a Lutris script with this as a work around for now. |
https://github.com/doitsujin/dxvk/wiki/DXGI It's mentioned there for WoW. Cheers. |
Wine staging 5 (without esync) and without dxgi works. Thx 👍 |
wine staging 5, slackware, nouveau driver I used vanilla wine-staging 5 without installing dxvk. I use classic graphics with the reforged client and have not tested the remastered models. 50% of the time it shows a black screen with just the cursor. If this happens and I log out and back in, clicking the play button does not seem to launch the game, so I have to restart my computer. The other 50% of the time, it launches, and I am able to play. However, sometimes after some games there is a small chance that Battle.net will say it cannot verify my client. I've also seen the case where the game immediately crashes to the desktop and displays an error dialogue box. Overall, it is possible to play using vanilla wine staging 5. It just does not launch consistently. |
The reason it works with native wine dxgi is probably because the Blizzard programmers forgot some weird DXGI1_6 call or whatnot that wine supports (d3d12 perhaps?), and DXVK does not understand. There is a couple of those "unknown interface" in my dxgi log when starting World of Warcraft too, but it does not seem to instantly fail loading as WoW seems to fall back to D3D11 mode. This USED crash back when d3d12 was first implemented... now it just falls back to whatever starts d3d11 even if its forced to d3d12 with a launch option. If you use wine's dxgi, launching with -d3d12 option will run vkd3d, and launching with -d3d11 will use dxvk. |
Normally those are harmless if the game checks properly whether the requested interface is actually supported - I mean I could try stubbing it, but since DXGI 1.6 has some really weird functionality that we can't easily implement it might cause issues in other applications. It also doesn't explain why it apparently sometimes works.
That's normal since vkd3d does not work with DXVK's DXGI. This is also why Proton switched to wine's own implementation in 4.11. |
Yeah, but i distinctly remember if doing that back when WoW first came with D3D12 support, it would crash to desktop if i used DXVK's dxgi... It was no "fallback", but a rather harsh crash. This is no longer the case, and i just wondered if this was the game "fixing it", or if dxvk's dxgi now has some kind of fallback magic? :) I would not at all be surprised if those Blizzard toons somehow managed to forget some weird dxgi check thingy that is totally off, but survives when using Windows 10 cos its no problem :) |
After playing the game for almost a week now using wine's DXVK the game launches stable consistently. I've only had like 2 hangs during the entire week when launching the game somewhere between 30 - 40x the last week. The game can also crash in-game after a couple of hours, but it also happens rarely. |
@nvaert1986 Almost seems like some driver troubles that happened a few months back that (to ME atleast) seemed as if the caches were "old" (the more dxvk cache you had built up over time), the more stable it was. Deleting the game-dxvk.cache file + clearing out the $HOME/.nv folder with nvidia GLCache files would bring back the instability. Somewhat not a definate thing, but testing stuff over time seemed as this was the case. So, hopefully it improves "over time" when playing then :) (Although i think the latest nVidia 440.59 driver has some fixes that also might improve this). Keep testing :) |
Is anyone still having this issue? I haven't been able to reproduce this in a while and I'm wondering if blizzard fixed this on their own with the latest build. |
This issue seems to be resolved mostly when installing it with the --without-dxgi parameter. It launches like 9/10 times. It still hangs on boot rarely, but I guess that's more due to the game being bugged than a bug in the DXVK. I'll go ahead and close the bug. |
Warcraft III: Reforged was finally given a 'Retail' status and am having issues. All the steps below were performed on a clean wine prefix
Without DXVK
The game starts and runs without DXVK and starts every time without an error, but the game is unplayable because the textures are very dark and some textures are missing.
With DXVK
The first time when you install DXVK, start Battle.net and start the game, the game starts and runs fine (I've played over 6 hours yesterday), but when you try to start the game a second time, the game doesn't start anymore and crashes back to the desktop with an error. Even after a reboot the game still crashes back to the desktop.
Things I've tried
Software information
Warcraft III: Reforged
Build: 1.32.0.14481
Settings: Changing various items doesn't make a difference
System information
Apitrace file(s)
Log files
The text was updated successfully, but these errors were encountered: