Yeah, I know what ya mean. Sometimes it breaks shit too but there have been one or two times that it has fixed shit that was broken in the standard version.
Anyway, I was just proposing it as an idea to test and see if maybe it fixes the GD issue and if it doesn’t, well, you can always opt right back out of it.
For completions sake here is the output of journalctl at the relevant time:
Nov 11 17:04:34 arch-desk audit[13799]: ANOM_ABEND auid=1000 uid=1000 gid=100 ses=2 pid=13799 comm="steamwebhelper." exe="/usr/bin/wine-preloader" sig=11 res=1
Nov 11 17:04:34 arch-desk kernel: audit: type=1701 audit(1541955874.337:89): auid=1000 uid=1000 gid=100 ses=2 pid=13799 comm="steamwebhelper." exe="/usr/bin/wine-preloader" sig=11 res=1
Nov 11 17:04:34 arch-desk systemd[1]: Started Process Core Dump (PID 13800/UID 0).
Nov 11 17:04:34 arch-desk audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@5-13800-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 11 17:04:34 arch-desk kernel: audit: type=1130 audit(1541955874.344:90): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@5-13800-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 11 17:04:34 arch-desk systemd-coredump[13801]: Process 13799 (steamwebhelper.) of user 1000 dumped core.
Stack trace of thread 13799:
#0 0x000000007bc429c0 n/a (/usr/lib32/wine/ntdll.dll.so)
Nov 11 17:04:34 arch-desk audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@5-13800-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 11 17:04:34 arch-desk kernel: audit: type=1131 audit(1541955874.531:91): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@5-13800-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Nov 11 17:04:54 arch-desk /usr/lib/gdm-x-session[710]: (II) NVIDIA(0): Setting mode "DP-0: nvidia-auto-select @3440x1440 +0+0 {ViewPortIn=3440x1440, ViewPortOut=3440x1440+0+0}"
Nov 11 17:05:16 arch-desk org.gnome.Shell.desktop[754]: Window manager warning: Invalid WM_TRANSIENT_FOR window 0x3a00005 specified for 0x3a0003d (Steam - Sh).
OK I found the solution to the game not launching and having a stack overflow.
In my Grim Dawn prefix I added ‘gameoverlayrenderer’ to the overrides and set it to disabled.
Game launches as normal now.
How to do this? Instructions, please.
I would assume in winecfg you go to the libraries tab, add that one from the list and set it as disabled.
And … it works … i’m surprised it’s that easy to fix this issue, really!
Note: “gameoverlayrenderer” isn’t on the list so i typed it and then edited it to disabled. Went as far as the game menu when testing it and stopped there: will have to go to work in under 30 minutes and i really must get ready for another day’s work, so no time to experiment further.
Same issue, here. Not having the stack overflow with proton, but proton’s got other issues. oddly enough, I tried a clean WINEPREFIX for the sake of testing, and the gameoverlayrenderer fix didn’t work.
In the old WINEPREFIX, where the fix did work, under default in library it’s disabled. Under Steam.exe, it’s set to native. Not sure why it would work in one prefix, but not another, but this is the only difference I can think of.
Played 2 runs of Crucible with no apparent issues.
This “fix” worked for me.
Worked for me too. Thanks for finding that!
Edit: tanks Blaizor!
Don’t thank me: thank Blaizor.
But it’s good to know it works for others as well.
Is anyone else getting texture flickering with dxvk? I’m using wine-staging 4.0 with dxvk 1.0. It almost looked like the old HKCU/Software/Wine/Direct3D/CheckFloatConstants issue. If so, is there a workaround that isn’t using dx9? (Nvidia 1050ti, 418.30)
I get flickering too on AMD hardware - I’m just resigned to DX9.
Foo. 
Here, I was hoping there was some setting to tweak. I can’t produce the flicker reliably, either. I don’t think it’s this issue: https://github.com/doitsujin/dxvk/issues/405
Luckily, I’ve gotten the game running flawlessly with Proton, but has anyone gotten Grim Internals to work with the game?
Just so you are aware Grim Internals apparently only works with the x86 version of the game currently. As for if it will work under Linux, regardless, I don’t know.
Thanks for the heads up, I’ll keep trying to get it going and if I do, I’ll share my results!
Has anyone gotten mods to work in the Steam version of Grim Dawn?
Which directory are they installed to?
The directories for Steam Proton:
~/.local/share/Steam/steamapps/common/Grim Dawn/
~/.local/share/Steam/steamapps/compatdata/219990/pfx/
I haven’t played with mods for GD yet, other than GrimInternals. For more information you can look at the Github thread for GD:
I get the linux version run smoothly with Grim internal latest version.
Thanks
(I also posted this
https://github.com/ValveSoftware/Proton/issues/466#issuecomment-491263945
for how to add it add steam games)