search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.88k stars 1.04k forks source link

Grim Dawn (219990) #466

Open PadreAdamo opened 6 years ago

PadreAdamo commented 6 years ago

No issues with Grim Dawn across AMD hardware. Launches perfectly.

Desidiosus commented 5 years ago

@mvdstam My follow-up comments on reddit have a link to a Proton version with the flickering patch applied to DXVK 1.0.1, which has a bit better performance than the 0.96 version, so there's no need to use the old version.

The patched 1.0.1 is available here. If you actually look at the commits, K0bin is the real MVP for making the flicker fix work with 1.0. The only thing I did was add Grim Dawn support.

rosshadden commented 5 years ago

I can't launch Grim Dawn. I get the dialog for 32bit vs 64bit, but when choosing either nothing happens. Launching Steam from a terminal does give some (hopefully helpful) output when it crashes (included below). I have tried on every version of Proton from 3.7 to 4.2, including the betas.

It's hard to tell which of the errors are specific to this and which may be safely ignored, but these stick out:

[S_API FAIL] SteamAPI_Init() failed; no appID found.
Either launch the game from Steam, or put the file steam_appid.txt containing the correct appID in your game folder.
Proton: Missing or invalid openvrpaths.vrpath file! [Errno 2] No such file or directory: '/home/ross/.config/openvr/openvrpaths.vrpath'
shadercachemanager/shadercacheimplsteamdepot.cpp (75) : Assertion Failed: Platform disambiguator mismatch!
ERROR: ld.so: object '/home/ross/.local/share/Steam/ubuntu12_64/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
ERROR: ld.so: object '/home/ross/.local/share/Steam/ubuntu12_32/gameoverlayrenderer.so' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS32): ignored.

The full error given: https://gist.github.com/rosshadden/66d20b2b5823068a5bb1f8a838bea57c My system information: https://gist.github.com/rosshadden/fba3b2e3378b01835af987f8d84672a0

Update: Tried with steam-native as well, and I get similar errors (added to gist above). The only difference I found was that steam-runtime had this error and native did not: wine: cannot find '/home/ross/.local/share/Steam/legacycompat/iscriptevaluator.exe' (and sure enough, that file exists and is readable by everyone).

rosshadden commented 5 years ago

Apparently I skipped a proton version. Based on this comment I tried proton 3.16-4 and it launched. After running it with this version of proton, I tried with 4.2 and it worked as well... Nothing other than trying 3.16-4 was done since when it did not work, so either something random is happening or there are some artifacting side-effects going on that bleed across proton versions.

garpu commented 5 years ago

I've had it crash a couple times with me, as well, but I had the /x64 flag set. If I don't set it, it seems to launch OK. Perhaps coincidence?

greydmiyu commented 5 years ago

I'm already using dx9. With dx11 there flickering textures on previous versions of the game too.

Are you also putting +fullproc on the command line? Here's the Launch Options I use for Grim Dawn. No flickering, no noticable issues with FPS.

/d3d9 +fullproc

lieff commented 5 years ago

@greydmiyu Nope, I do not have +fullproc, and quick googling says there no such option for Grim Gawn: https://steamcommunity.com/app/219990/discussions/0/535152276590715701/#c535152276591233289 But I'll check it soon.

jesusredondo commented 5 years ago

I have been messing with the dxvk modified versions posted above. Unfortunately I don't have Proton 4.2 yet (I still don't know how to manage/update Proton versions, if possible through steam). So all test has been performed in 3.16 Beta

The updated dxvk version (1.0) in reddit works as fine as is the 0.96 posted in the video above.

FPS is great, no more Flickering,everything looks fine except... there is a small stutter every 2-3 seconds which is very annoying, such a pity.

As other mentioned before, disabling dx11 halves performance (even at lowest resolutions, and considerind I am using a 1080ti, something must be wrong) so I have discarded that option.

Using the dxvk modified version is not 100% playable without the stutter every 3-4 seconds. If anyone has been able to make it run smooth... could you please share Proton folder? Thanks

kisak-valve commented 5 years ago

Hello @jesusredondo, Proton versions managed by Steam are listed in the Tools section (Steam -> Library dropdown -> Tools).

jesusredondo commented 5 years ago

@kisak-valve Thanks a ton! Downloading proton 4.2... I will update with the outcome.

jesusredondo commented 5 years ago

Ok, proton 4.2 fixed everything. No need to include the modified dxvk dlls.

Thanks!

garpu commented 5 years ago

With 4.2, you're not getting the flickering on dx11? I just tried 4.2-1 without the modified dxvk, and it's still flickering for me. It comes and goes. It almost seems to be similar to the old Titan Quest missing texture bug in that sometimes when you restart, the bug is gone.

jesusredondo commented 5 years ago

Yes, I have just installed the 4.2.1. and it made the trick. No flickering at all. And the 3 second stutter is almost gone (almost). Very playable now. I have latest nvidia drivers (1080ti), I also updated the kernel to latest version ( somebody in protonDB fixed the flickering doing so).

Maybe I fixed the flickering by doing both things: Kernel upgrade and proton 4.2.

lieff commented 5 years ago

@greydmiyu no noticeable difference with +fullproc

For dx11, Proton 4.2 with unpatched dxvk do not works for me too.

garpu commented 5 years ago

https://github.com/doitsujin/dxvk/issues/405 Apparently with dxvk 1.1 the flickering is fixed?

tr37ion commented 5 years ago

It looks like #864 has a similar issue.

scottc commented 5 years ago

Popular unofficial Grim Dawn community mods. (Not steam workshop)

DISCLAIMER: I am not the author of these mods. Use at your own risk, no warranty provided, may destroy your save games, may cause data loss, get your steam account stolen, permanently banned, damage to hardware or personal injury.

At time of writing this post:

GrimInternals

0) Download GrimInternals.

1) Extract GrimInternals, as per the windows instructions. (Typically; "/home/__YOUR_USER__/.local/share/Steam/steamapps/common/Grim Dawn")

~Note: I extracted griminternals inside the /Grim Dawn/x64/ folder instead, because it cannot find the dlls inside the /x64/ folder otherwise.~ Note: this is no longer the case.

OK, I got it working tonight. For me, I had to make sure GrimInternals64.exe and GrimInternalsDll64.exe were located directly in my Grim Dawn folder. Having them in the x64 folder simply would not work.

@SherrifsNear https://github.com/ValveSoftware/Proton/issues/466#issuecomment-503800017

2) Can dump the proton run command via adding launch options to Grim Dawn: Properties > SET LAUNCH OPTIONS... PROTON_DUMP_DEBUG_COMMANDS=1 %command%

3) Run and then exit Grim Dawn.

4) Make a copy of the dumped run command, to home directory: cp "/tmp/proton_$USER/run" "$HOME/run_grim_dawn.sh"

5) Edit $HOME/run_grim_dawn.sh with text editor, and modify the DEF_CMD var file path to point at GrimInternals. And any other customizations as you see fit.

cd "/home/__YOUR_USER__/.local/share/Steam/steamapps/common/Grim Dawn"
DEF_CMD=("/home/__YOUR_USER__/.local/share/Steam/steamapps/common/Grim Dawn/GrimInternals64.exe")

Note: I also explicitly have the version of proton installed, under Library > Tools. Which appears under $HOME/.local/share/Steam/steamapps/common/Proton __VERSION__/

6) Make it executable: chmod +x ~/run_grim_dawn.sh

6) Run it:

cd ~
./run_grim_dawn.sh

If it fails to run, you can remove this line from the run command, to get errors printed to the console. To help troubleshoot. But comes with a small performance penalty.

WINEDEBUG="-all" \

Should also be able to add it as a Non-Steam game shortcut.

Item Color Filter

0) Download Item Color Filter and check that you have the latest version. (outdated versions may break in-game text descriptions) 1) Extract the Item Color Filter, as per the windows instructions. (Typically; "/home/__YOUR_USER__/.local/share/Steam/steamapps/common/Grim Dawn") 2) Play Grim Dawn. 3) Manually update after each Grim Dawn release.

GDItemAssistant

I haven't had any luck with GDItemAssistant which depends on dll injection.

GDStash

As per @lieff 's comments below: https://github.com/ValveSoftware/Proton/issues/466#issuecomment-483631990

java -Xms1024m -Xmx1024m -jar GDStash.jar

You can also put this in a shell script (.sh) file with executable permissions chmod +x, and then add to steam library for convenience.

#!/bin/sh
java -Xms1024m -Xmx1024m -jar GDStash.jar
lieff commented 5 years ago

GDStash works for me. Both variants: installed inside wine prefix or linux native. Native runs like this: java -Xms1024m -Xmx1024m -jar GDStash.jar

Pardlerum commented 5 years ago

@scottc thanks for taking the time to post that in such detail - I miss auto-pickup! Will try and implement when I get back from work...

Pardlerum commented 5 years ago

Just can't get GrimInternals working on my setup. A few changes from @scottc description above: (1) Needed to chmod +x the files after expanding; and (2) Rather than manually editing the path details in Steam use the 'Change...' button to locate the GrimInternals64.exe file. This populates the "Target" and "Start In" elements with your details...

..but although GrimInternals obviously runs it always gives a "Can't find Grim Dawn!" error for me. I presume there is some Windows path it's looking for beyond the launch folder. Any assistance greatly appreciated...

scottc commented 5 years ago

@Pardlerum

..but although GrimInternals obviously runs it always gives a "Can't find Grim Dawn!" error for me. I presume there is some Windows path it's looking for beyond the launch folder. Any assistance greatly appreciated...

It would be looking relative to the current "working directory".

New instructions https://github.com/ValveSoftware/Proton/issues/466#issuecomment-483628753

Pardlerum commented 5 years ago

Thanks for the update @scottc. Working! I am very happy. :)

lieff commented 5 years ago

Latest proton 4.2-3 and Nvidia 418.56 now works with dx11 without glitches.

beaverusiv commented 5 years ago

Hmm, using @scottc's instructions I can get GD to load from the GrimInternals bash script but Ctrl+F5 does nothing.

scottc commented 5 years ago

Hmm, using @scottc's instructions I can get GD to load from the GrimInternals bash script but Ctrl+F5 does nothing.

Have you edited the shell script to use GrimInternals?

DEF_CMD=("/home/YOUR_USER/.local/share/Steam/steamapps/common/Grim Dawn/x64/GrimInternals64.exe")

Does it mention GI version in the bottom right hand corner of character select?

v1.1.1.2 (x64) (GI v1.77)

If GI is working, but the configuration UI is not. As a workaround, you can edit the GrimInternals.ini file for configuration changes before launching the game.

I believe most of the run-time dependencies are similar between grim dawn and grim internals. Can try turn on WINEDEBUG console messages by removing WINEDEBUG="-all" \. For additional information.

beaverusiv commented 5 years ago

Yes, the proper .exe is set in DEF_CMD. No, the GI version does not show up :/

I have tried without suppressing debug output but I see nothing that indicates an error. If I misspell GrimInternals64.exe it throws an error so it is definitely looking for that file.

It does have these lines when starting:

info:  Game: Grim Dawn.exe
info:  DXVK: v1.0.3-4-g46908d47
info:  Found built-in config: Grim Dawn.exe

The same thing happens for steam-native and steam-runtime.

beaverusiv commented 5 years ago

Update: commenting out SteamGameId="219990" \ seemed to fix it for me. Note SteamGameId, not SteamAppId.

Hopefully this helps if someone else has problems.

AndyHoang commented 5 years ago

@scottc Thanks you I follow and its work for me with latest grim internal v1.1.2.2
Event better I try to improve it so that we can run it inside the steam instead running the script [https://i.imgur.com/ZkukHuW.jpg](me playing)

And now we can play it on steam

blutigJK commented 5 years ago

I'm having issues getting GrimInternals to run. Followed the steps above from @scottc and it doesn't want work even though GrimInternals64.exe process is running. It seems to spit out this error when loading to the main menu.

Timed out waiting for game mapping!
002d:fixme:system:SystemParametersInfoW Unimplemented action: 59 (SPI_SETSTICKYKEYS)
002d:fixme:system:SystemParametersInfoW Unimplemented action: 53 (SPI_SETTOGGLEKEYS)
002d:fixme:system:SystemParametersInfoW Unimplemented action: 51 (SPI_SETFILTERKEYS)
info:  Presenter: Actual swap chain properties:
  Format:       VK_FORMAT_B8G8R8A8_UNORM
  Present mode: VK_PRESENT_MODE_IMMEDIATE_KHR
  Buffer size:  1920x1080
  Image count:  3

Here's the full log from the terminal.

Taking out SteamGameId="219990" \ doesn't seem to change anything either.

kisak-valve commented 5 years ago

Hello @blutigJK, @beaverusiv, your comments were removed due to the request and link of copyrighted content. This is legally problematic.

SherrifsNear commented 5 years ago

blutigJK, did you ever solve this problem? I am having the same issue. GrimInternals64.exe runs no problem, but it isn't actually enabled in-game.

blutigJK commented 5 years ago

@SherrifsNear Unfortunately not. Older versions also straight up don't work as they need older versions of the game to work. I'm currently waiting for the Steam Summer sale myself to buy the DLCs before I pick up Grim Dawn again as the two builds I want to play with require the DLC classes. Hopefully someone can chime in by then with a potential fix or I eventually figure it out.

SherrifsNear commented 5 years ago

OK, I got it working tonight. For me, I had to make sure GrimInternals64.exe and GrimInternalsDll64.exe were located directly in my Grim Dawn folder. Having them in the x64 folder simply would not work.

lucifertdark commented 5 years ago

I copied what AndyHoang & SherrifsNear posted & it's working for me too, thanks guys. :D

scottc commented 5 years ago

Thanks @SherrifsNear for fix.

GloriousEggroll commented 5 years ago

Hi all, for those using Grim Internals, feel free to try my proton build. It has detection for grim internals and will ask you if you'd like to run it before running the game, and will run it ootb without hassle.

https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/4.11-GE-1

*Also, I recommend copying the Grim Internals files into just the game's main folder.

Grim Internals launches the 64 bit version of the game regardless of which folder it's in, so there is no point in using the Play Grim Dawn (x64) option that steam gives.

If you wish to use Grim Internals and have both options work, you will need to copy the Grim Internals files to both the game's main folder and the x64 folder. griminternals0

griminternals

griminternals1

cryzed commented 5 years ago

I run this on Arch Linux using Steam with the latest Proton. I have a recent Intel i7-7770k CPU and a NVIDIA GTX 1060. Outside of fights, even with graphical settings all maxed, the game runs at a stable 60 FPS -- in most cases even during the fights. However as soon as I use the Demolitionist's skill "Blackwater Cocktail" and hit a group of enemies, the frames drop to around 1 FPS for several seconds initially. This keeps happening and doesn't get better.

Just to test, I also set the lowest graphical settings possible and tried again: even there the game freezes up for several seconds. This is specifically happening in the Sewers during the early-game mission for Barnaby. Anyone else had this experience?

cryzed commented 5 years ago

I found the issue: it was the sound SFX. After muting it, the stutters disappeared entirely when using the skill. I suspect this happened in combination with my specific Pulseaudio configuration (/etc/pulse/daemon.conf) which had some non-standard high-quality values:

resample-method = soxr-vhq
flat-volumes = no
default-sample-format = s24le
default-sample-rate = 192000
alternate-sample-rate = 192000

I assume this caused Pulseaudio to have to resample a bunch of sound effects that all occurred at once during an explosion, causing the game to stutter. When I revert this configuration to its much less demanding defaults, the stutters are gone even with the sound SFX slider enabled.

What's strange is that even setting the resample-method to speex-float-1, to my understanding a very cheap resampler, doesn't fix the issue -- so I suspect it has something to do with the target sample format. Anyways, my workaround for now will be to change these settings before playing -- however, maybe it's worth looking at how these sound effects are forwarded to Pulseaudio, maybe there's a way to optimize this: but I am not well-versed in audio at all.

cryzed commented 5 years ago

I did some more experiments and simply setting: default-sample-rate and alternate-sample-rate to their defaults was enough.

AndyHoang commented 4 years ago

Not sure how its ended up, but to use GrimInternals on proton, I have to use GloriousEggroll custom proton build, the old way from @scottc make the game constantly crash (try latest griminternals and proton (4.11.8). Hope someone can double check with me Normal grimdawn worked like usual (v 4.1.5.1)

ruvaldak commented 4 years ago

Heavy microstuttering/stuttering when using Linux 5.4rc7 kernel on Manjaro. Switching back to 5.3 solves most of the stuttering, though changing anything including proton version seems to bring it back until a reboot. May just be my machine though.

jazztickets commented 4 years ago

So the game has an in-game clock that you can click or hover over to see the real world time (the button is right above your character level). However, the time is being displayed in UTC instead of localtime. The hardware clock in BIOS is set to UTC (as it should be), and the timezone is correct in linux as shown by timedatectl. The timezone in regedit is also correct (HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation)

Anyone else experiencing this?

lucifertdark commented 4 years ago

Just checked & everything is the same for me in the way of settings but I'm getting the correct time on the in-game clock.

shoober420 commented 4 years ago

Whitelist Request

System Information

Works great out of the box using the x64 exe!

ziabice commented 4 years ago

Tested the game with Proton 5.0-2 and 5.0-3, it seems to works well (I haven't played too much).

Important: when started, the game has long loading times during which it shows only a black screen. Don't be fooled like me believing it crashed, it (maybe) is just compiling shaders.

Launched the game selecting "Play Grim Dawn" from the menu that appears when you press the "Play" button into the Steam Client game library.

My specs: GPU: AMD RX 580 4GB Driver: Mesa 19.3.4 Distro: Manjaro CPU: Ryzen 2600, 16GB RAM

wfstuff commented 4 years ago

Whitelist Request

System Information

I confirm:

Issues

wfstuff commented 4 years ago

P.S. I played about 65 hours through the whole base game. I did almost all quests I found and explored all areas I found. Had no problems at all. (I had installed all expansions, but did not play the expansions, yet.)

kisak-valve commented 4 years ago

Hello, is anyone seeing an issue with this game and Proton 4.11 that would block it from being whitelisted?

garpu commented 4 years ago

For what it's worth, I've been playing it on the 5.0 tree, and it's just fine. I didn't have a problem with 4.11 when I was using it.

wfstuff commented 4 years ago

After updating to 5.x I had the feeling that some mouse clicks did not register when moving. After downgrading to 4.11 it did not occur. Not really sure about it though, could also be the area I was in or just clicking on the wrong area etc. Checking on protondb.com it seems at least another person had the same problem, quote: "I would click somewhere and sometimes it wouldn't register. Was annoying, but not gamebreaking."

I'm still playing on 4.11 (because it just works) and almost finished the Malmouth expansion. Still no problems at all. Not a single crash or glitch in over 80h of play time. The only minor issue I have with the game is that sometimes square areas of the map are revealed. But it seems to be a general game bug: https://steamcommunity.com/app/219990/discussions/0/405693392915991830/ https://steamcommunity.com/app/219990/discussions/0/1483232961039531181/

ziabice commented 4 years ago

@wfstuff I played nearly 5 hours last weekend using Proton 5.0-4 and everything worked perfectly, never had the feeling that mouse clicks were not registered.