Hi,
I tried to run GD today after not playing it for several months and I noticed something weird.
I used o run it on Wine 2.16-staging without any problems (linux mint 18 64bit on a 32bit prefix in Wine). But since I also play Neverwinter Online which got fixed with version 3.0-rc05 becuz of graphics not fully rendering, I changed my Wine version to 3.0-rc06 (which indeed fixed the issue on NWO).
However, when I start up Grim Dawn, it starts up perfectly, but then at the logon screen the 3D graphics seem to not render for some reason. You can see in the including screenshots what I mean.
Also, it takes about 10 seconds before the text appears on the buttons. When I log into the game I can see the mini-map, the action bar, the quest text etc, but for the rest just a black screen (see screenshot).
I m running it through PoL (PlayOnLinux) in a 32bit prefix set to Windows 7 (also tried it with setting it to WinXP) and it has always worked like that. The only thing that changed since last time I played is that my grapics driver (Nvidia) got updated to version 384.111 (kinda had to becuz of the Spectre and Meltdown issues) and updated Wine version from 2.16-staging to 3.0-rc06.
All other games (i.e Devillian and Neverwinter Online) work perfectly in these settings. I am running Linux Mint 18.3 (upgraded from Linux Mint 18 when GD still worked) with POL version 4.2.12. I also tried a new clean prefix with the last Wine version that worked (2.16-staging) but it still had the same issues after installing it through Steam.
Has anyone else noticed similar issues, and does anyone by any chance know how I could fix this issue. I really love this game and bought it when it was kickstarted a few years ago and it has had some issues of not working over the course of time, but there always was some sort of fix and/or workaround to get it to work again. Now I’m just lost at what the issue might be this time. If anyone can provide help or insight in the matter, please do let me know.
Well DX11 is supported by Wine 3.0. Neverwinter Online makes use of DX11 and that works flawlessly. It used to work just fine with 2.16-staging (staging server also supported DX11). Thing is, Steam by default installes the correct version of DX, so I doubt it could be a DX issue. But thnx for the suggestion.
The DX11 support in Wine isn’t all the way there yet. There are still a lot of games that don’t run correctly with it.
I’m running on 2.21-staging at the moment. It won’t run at all with DX11. I have to use /d3d9 in the Steam options. You should at least try it and see if it works that way. That at least helps debug the problem.
Is it possible you were running in DX9 mode under 2.16 without realizing it?
Grim Dawn also has never run well under regular Wine. It’s always needed Staging. And there is no Staging for 3.0, and it doesn’t look like there will be one soon.
(Also, this is a problem with Wine, or with your installation of Wine. It’s not a problem with Grim Dawn.)
Well thats where you are wrong my friend. In the beginning GD always ran fine without the need for a staging Wine version. I’ve run it a very long time on Wine version 1.9.5 (and also on earlier versions of Wine). When I started the use of the staging version of Wine I noticed a small increase in performance even.
As stated I even installed it in a clean wine (32bit) prefix using both WinXP and Win7 using the 2.xx-staging version of Wine (and also 1.9.5 which always used to work perfectly) and it had the same results. It occured after an update of the game itself. I hadn’t used Steam for a while and when I started it up it updated the game and that’s when the problem first occured. I also have tried it with the /d3d9 option in Steam and there was no difference at all. In the Wine 2.xx-staging versions, even with CSMT enabled Neverwinter Online was still missing textures on the character. With version 3.xx those issues have completely been resolved.
It seems with the new stable Wine 3.0 release a staging candidate is no longer required for extra DX10 or DX11 functionality
Wine 3.0 Released
January 18, 2018
The Wine team is proud to announce that the stable release Wine 3.0 is now available.
This release represents a year of development effort and over 6,000 individual changes. It contains a large number of improvements that are listed in the release notes. The main highlights are:
Direct3D 10 and 11 support. <<<<
The Direct3D command stream. <<<<
The Android graphics driver.
Improved DirectWrite and Direct2D support.
Once again, because of the annual release schedule, a number of features that are being worked on have been deferred to the next development cycle. This includes in particular Direct3D 12 and Vulkan support, as well as OpenGL ES support to enable Direct3D on Android.
So again, I don’t think it’s a DX11 related problem. If it’s a problem with Wine the problem should be resoved when reverting back to a Wine version that last worked. Also, it is the ONLY game that has issues. All other Windows based games run flawlessly. If it was a Wine problem those issues should imho also arise in other games, which it doesn’t.
Attached you can see GD pics from the early stages (2013) when staging Wine versions didn’t even exist yet. So that’s proof that GD didn’t need any staging versions to work.
I seem to have solved the problem. Even though it still doesn’t work very well with Wine 3.0-rc06, it does work with Wine 2.12-staging with csmt enabled and putting all settings to high. At least I’m able to play the game again.
