zpangwin
Published
Out of the box, this is in a terrible state. After you get the initial problems fixed, it works great
dsound.dll from lutris script, wine registry tweaks
forced french language, audio looping, audio out of sync during cinematics. all resolved by steps below.
These were resolved using steps below
Alt+Tab doesn't work correctly (game remains on top of other windows). However, Linux Workspaces still work fine (Ctrl+Alt+left/right arrows).
if using controller, steam version of the game has predefined, uneditable mappings which you cannot disable in-game or via steam. you can disable using registry tweaks in wine which allows using 3rd party remapping s/w like antimicro. See link to my antimicro setup for more info.
Steps to fix issues:
0. Have protontricks, winetricks, and wine installed. If using custom steam paths, change in both the commands AND the reg file. For reg file, use your absolute linux path prefixed with "Z:" e.g. "Z:/home/xxx/etc"
1. From terminal run the following to create backups of registry, fix bad registry paths, use protontricks to setup reg entries for dsound, then use a more reliable version of dsound.dll. Should resolve forced french audio, looping audio, & audio out-of-sync.
cd $HOME/.steam/steam/steamapps/compatdata/15130/pfx;
mkdir reg-backups;
cp -a -t reg-backups *.reg;
sed -Ei 's/Wow6432Node\\{2}(Wow6432Node\\{2}Ubisoft\\{2})/\1/g' system.reg;
find ./drive_c -type l -iname dsound.dll -delete;
protontricks 15130 dsound d3dx9 arial d3dcompiler_47;
wget --output-document= ./drive_c/windows/syswow64/dsound.dll https://github.com/legluondunet/MyLittleLutrisScripts/raw/master/Beyond%20Good%20and%20Evil/dsound.dll;
2. Download bge.reg file or create yourself but use windows-style line endings. Contains reg settings I reverse-engineered from the settings app to fix flicking artifacts + the NoBands fix. Save to ~/.steam/steam/steamapps/compatdata/15130/pfx/drive_c/bge.reg
3. Regedit seemed to ignore terminal args for me so had to manually import from the gui. Run WINEPREFIX="$HOME/.steam/steam/steamapps/compatdata/15130/pfx" wine regedit then from the top-left of regedit, choose Registry > Import Registry File > and select bge.reg
Extras:
- My full notes - incl fix for SettingsApplication.exe
- My BGE profile for antimicro - incl how to disable native gamepad mappings & use custom ones
Thanks to Franco & mattmacks for their tips
Mostly worked out of the box. Couple minor annoyances and oddities but not stuff most people would care about.
If I played the game for a long period of time, certain parts of the audio would "drop out" (stop working). You'd still get some audio like combat sound effects but other sound effects, bg music, sometimes dialog would stop playing. This seemed to happen randomly after playing for several hours at a stretch and the only way to resolve it was to exit and restart the game.
In Fullscreen mode, game would remain on top of screen when using Alt+Tab. Using Linux Workspaces (Ctrl+Alt+ Left/Right arrow keys) worked fine though.
Saves work as designed. But I HATE DS2's save system and very much preferred DS1's save system (DS1 gave you 5-6? saves PER GAME. DS2 you get ONE save PER GAME; can't "go back a couple saves ago")
The actual issue I had was that this game completely ignored my Steam cloud settings and continued to use them even after they were disabled in the per-game AND global steam settings (and yes, I restarted steam first). As a workaround, block access to the cloud folder: cd ~/.steam/steam/userdata/<steam_id>; rm -r 388410; sudo mkdir -m 0500 388410; Then I put local save dir (~/.steam/steam/steamapps/compatdata/388410/pfx/drive_c/users/steamuser/My Documents/My Games/Darksiders2) under git version control.
Note for other git users: if you want to restore without exiting to desktop, you need to do so while in-game (pause menu is ok, but "Continue" menu is too late). Pause Menu > "Exit Game" really reloads last save from disk (watch when loading icon appears).
Had a couple of hard freezes (had to physically reboot system) but they were infrequent (2-3 times in ~150 hrs played?). Seemed to become worse after playing for an extended period of time. As I had to close & relaunch the game periodically due to the sporadic audio issue I mentioned, this issue pretty much disappeared.
If you leave the game paused for awhile (>10 min?) it starts to behave weirdly... menu works fine but when unpaused game would be (temporarily) frozen/unresponsive. This happened frequently for me and the while it would fix itself anywhere from a couple seconds to a minute or so later, the time it took seemed to correspond to how long I left it paused... I wasn't running anything else and this behavior was consistent for ~ 150 hrs of play.
This game does NOT like Linux Virtual Terminals (e.g. Ctrl+Alt+F1 etc). If you have one open before launching, the game won't launch. Opening one, I think causes game to exit. Rebooting the system seems to fix launching.
I did not choose to force a specific proton version (not sure which one it used but my drop-down shows "Proton Experimental" or "Proton 5.13-4" as the most likely candidates).
Initially I had played without any launch options and it worked just fine (which is why I'm submitting as a non-tinker report). That had worked fine for me under Fedora 33 and under LMDE-4. I also tried with PROTON_USE_D9VK=1 %command% to see if that would fix some of the weird stability problems; didn't help but also didn't hurt anything. My stability problems weren't game breaking and were relatively minor so I just used the workarounds described above and was able to mostly forget about them. Only other thing that was weird was that the game awarded me a the cheevo that's supposed to be for "completing everything" when I was reloading a game (pause > exit game > continue)...about halfway through my first play-through. other than that, gameplay was great and everything worked pretty much as you'd expect.
Takes a little work but runs great afterwards; including cinema scenes
Already had xboxdrv installed. Out of the box, I got crashes and error message. Deleting the {SteamDir}/steamapps/compatdata/462780 folder got me up and running with everything but cinematic scenes. The Media Foundation fix mentioned by others did NOT fix this issue for me. Installing Proton-GE did.
- If you had setup any custom launch settings, get rid of them; they aren't needed and caused my game to crash when using Proton-GE.
- Go to https://github.com/GloriousEggroll/proton-ge-custom/releases and find the lastest release. I used the latest MF (Media Foundation) version
Proton-5.11-GE-3-MFbut probably any recent version would be fine. - Open a terminal and
cd ~/.steam/root/compatibilitytools.d - Run
wget https://github.com/GloriousEggroll/proton-ge-custom/releases/download/5.11-GE-3-MF/Proton-5.11-GE-3-MF.tar.gzto download the file - Run
tar -xvf Proton-5.11-GE-3-MF.tar.gzto extract it - Close & restart Steam then go to
Libary> right-click on Darksiders Warmastered Edition >Properties. - Check the checkbox for "Force the use of a specific Steam Play compatibility tool"
- From the drop-down below the checkbox pick
Proton-5.11-GE-3-MF(if you don't see it, check for a scrollbar) - Click Close button to save the changes.
- Delete your prefix folder 462780 (e.g.
rm -r "${SteamDir}/steamapps/compatdata/462780". SteamDir defaults to~/.local/share/Steam. If you added a custom download folder, then from yourDarksiders Warmastered Editionit will be located at../../compatdata/462780. Skipping this step will cause game to crash. - Run the game. A fresh prefix folder will be created automatically.
At this point the game should launch, detect controller automatically if present, and cinematic scenes will actually play. Sound/Video/Controller/Gameplay seemed fine. Alt+Tab worked fine too.
Proton-5.11-GE-3-MF GloriousEggroll
Proton-5.11-GE-3-MF + MF fixes
Fullscreen, the game does not focus on its own window correctly after launching. Give it 10-20 sec to load. Make sure you have another window open (text editor, browser, terminal, doesn't matter what). Then click game window from taskbar. it will act like it's going to work but desktop/other window will be in focus instead of game. Ignore this and Alt-tab to some other window. Finally, click game window from taskbar again. The 2nd time, the selection will work and it will correctly set focus on game window as fullscreen.
Out-of-the-box, the cinema scenes didn't work and would cause the game to crash with error. I also had the fullscreen focus issue.
After tinker steps, both of the initial cinema scenes play correctly. The fullscreen focus issue remains but using the workaround I described it is only a minor annoyance.
Updated report; ignore my old report
New steps were tested on both Linux Mint 19.3 and LMDE 4.
Locations
PROTONDIR=$HOME/.steam/root/compatibilitytools.d
GAMEDIR="<SteamDir>/steamapps/common/Darksiders Warmastered Edition"
PFXDIR="<SteamDir>/steamapps/compatdata/462780"
New Tinker steps:
If you have any launch options set, clear them out for now. Exit game AND steam.
In terminal, first create variables for locations above (with YOUR paths) then:
cd "$GAMEDIR" wget https://lutris.net/files/tools/dll/mfplat/x32/mfplat.dll
mkdir -m=755 -p $PROTONDIR && chgrp $USER $_ && chmod g+s $_ && cd $_ wget https://github.com/GloriousEggroll/proton-ge-custom/releases/download/5.11-GE-3-MF/Proton-5.11-GE-3-MF.tar.gz tar -xvf Proton-5.11-GE-3-MF.tar.gz find . -type f -iname '*.py' -exec chmod a+x "{}" ; mv "$PFXDIR" "$PFXDIR.old"
Keep terminal open. Start Steam > Libary > right-click on Darksiders WME >
Properties>Generaltab > check box for "Force the use of a specific Steam Play compatibility tool". SelectProton-5.11-GE-3-MFfrom dropdown. Click Close button to save.Launch game & exit from main menu. Confirm recreated PFXDIR dir owner/group/perms.
In terminal:
cd "$PFXDIR/pfx/drive_c" wget https://github.com/z0z0z/mf-installcab/archive/master.zip unzip master.zip cd mf-installcab-master chmod a+x "installcab.py" export PATH="$PROTONDIR/dist/bin:$PATH" WINEARCH=win64 WINEPREFIX="$PFXDIR/pfx" ./install-mf-64.sh
This uses Proton's bundled wine binaries for better compatibility. If you used these scripts before, copy windows6.1-KB976932-X64.exe to the drive_c dir first to save downloading the file again.
At this point, cinema and intro scenes should be fixed.
Note: Proton 5.13-2 didn't work for me. Use Proton-5.11-GE-3-MF or read their rel notes to find one mentioning this game as working. Newest (Proton-5.21-GE-1) lists this as broken.
addendum to my report from yesterday. notice issue for wireless controllers which could lose unsaved progress
Proton-GE + Media Foundation fix
I am using xboxdrv for my wireless xbox 360 controller. Everything is detected and it works fine out-of-the-box, even before the Proton-GE + MF fixes I noted in my report from yesterday.
Noticed if the controller turns off from inactivity, the game exits (or crashes?) silently without warning AND WITHOUT SAVING. In theory, this should only impact wireless controllers and even then only if you are leaving it inactive for a long time.
After I realized what was happening, I tested to verify. Setting screensaver to 1 minute had no effect (just moved the mouse to dismiss but game stayed open). Then I set screensaver for 30 min and used a timer app and just left the game and controller sit. At ~15 min, the controller led turned off and the game promptly exited.
Since this has the potential to lose in-game progress and protondb still does not allow editing of submitted reports, I felt an addendum to previous report was warranted.
Workaround: Save before stepping away.
played with xbox driver already installed; used an xb360 controller and it seemed to pick it up without any effort on my end and worked perfectly. Only noticed some minor input lag in the menu; didn't notice one in game. Intro animation/video worked fine. I didn't play very long at all but what i did seemed stable and fluid.
Like with NNK1, NNK2 save games themselves worked fine. But once again I had the issue the game would completely ignore my global steam setting to disable steam cloud and every time I launched steam I would have to once again disable the cloud saves for this specific game. Regardless of whether steam was launched normally or in offline mode. Mildly irritating but irritating all the same.
I had an issue on initial launch where the game process hung in the background (no window was displayed at all but you could see the process using terminal/system-monitor). I eventually found that this is likey to only be encountered by a subset of NVIDIA users and I'm apparently just lucky... anyway, I eventually found that if I opened a terminal and ran:
pkill -9 -if 'wine|589360'
then whatever the stalled process was would get killed and the game would launch. After I reached main menu and exited the game, this was not necessary for any subsequent launches as long as I was forcing compatibility to Proton Experimental (also tried with Ge-Proton8-20 but when using that one, the pkill command was required every launch). More details can be found in my comment on the bug report here.
Assuming "typical gamer" means someone with the same hardware as me, then I assume they would run into the same issue with the hung process. I don't think most casual users would know how or like having to run a terminal command just to start the game. If they did not experience the same issue, either due to different hardware or the issue being resolved, then my answer would be yes, that most users would have an enjoyable experience assuming they like the content of the game itself - I had no other issues aside from those mentioned above.
After setting up ProtonGE + Steam input for controller, the game worked great aside from the mildly irritating issue with the cloud saves.
My xbox 360 controller was not automatically detected by game (e.g. just turn it on and it was picked up as is usually the case for other games that support controllers). However, when I launched steam in online mode, then went to the game's properties in Library and under the Controller section changed to "Enable Steam Input", I was able to download an official profile for my controller and play without any further issues related to the controller.
Saved games themselves worked fine. The only issue is that I have my cloud saves globally disabled and this game does not respect that setting. Every time I launched steam, I would have to go back to this game's properties and manually disable the cloud saves for this specific game (despite having a global setting of disabling steam cloud). It did this regardless of whether steam was launched normally or in offline mode. Which was kind of annoying.
bit of a wine noob but i just tried things on winehq page for prototype 1 and from posts on protondb for other games (e.g. arkham city)... still didn't work great. initially no sound (no stream in pavucontrol). after running protontricks below had sound (finally showed stream in pavucontrol) but in game the sound stuttered so badly it was honestly better off without sound. for some reason, highest res it let me select was 1280x720 despite that my display settings in cinnamon are at 1920x1080 and I am able to select 1920x1080 in the Windows version on same box (dual boot). Also, when in game even if I mute the sound, the menus are really messed up (partially visible text) and the game is prone to frequent crashes... I was able to play the initial scenes where they introduce controls but it would always crash for me before it got to the flashback part.
here's what I ran (use semi-colons to find end of each line... hopefully protondb will consider upgrading to markdown in the future):
sudo apt install -y git python3 python3-pip python3-setuptools python3-venv;
python3 -m pip install --user pipx;
~/.local/bin/pipx ensurepath;
pipx install protontricks;
protontricks 10150 xact;
protontricks 10150 winxp;
protontricks 10150 vcrun2005 dsound dmusic mdx d3dx9 d3dcompiler_43 win10;
My exact graphics card is a GeForce GTX 970. Didn't tweak anything aside from using AntiMicro (see https://linuxg.net/how-to-install-antimicro-on-ubuntu-18-10-and-ubuntu-18-04/) so I could play on my TV with a 360 controller (requires xboxdrv package from the central repos); you can get a copy of my config here (https://pastebin.com/3K1zyr9z) if you would like to use it as a template.
Game runs great even without me updating to the latest/recommended drivers (just did a clean install of Mint 19.1 in last 30 days and used default drivers). I had some minor issues (game hanging/freezing) but it was more toward end of game and i played the heck out of it. I say that freezing is a minor issue because a) it was the game process only, not the system, b) I had the same experience using WIn7 previously on the same box, and c) this happened fairly infrequently. My recommendation is that you open a terminal window before starting the game. Then if the game freezes, you can Alt+Tab to the terminal window (it will still let you type commands even if the game display remains onscreen) and you can run 'pkill -9 Risen' without the quotes to kill the game processes. Over the course of probably a week playing this a LOT, I had this happen maybe 5 times if that, and generally only after the process was running for 5+ hours or I had been reloading saves a lot.
As far as in-game performance, I didn't really have any issues. There were some sections where I would talk to NPCs and it would only have subtitles with no audio playing. This did not happen very often so I am not sure if it is a bug with the game itself or due to it running under Proton. In any case, NPC dialog usually worked but there were a few (missing audio) hiccups here and there.
Aside from that and the occasional game hang (possibly related to my drivers or just game code as those happened on windows too for me), this ran great with no tweaking required.
Strange that Risen 2 does not run from proton/steam, considering this game has a Gold rating on WineHQ and I see reports elsewhere online that the GOG version is running ok under wine. I might try again later / try importing the gog version via steam and report back on that. For reference: https://www.gamersonlinux.com/forum/threads/risen-2-dark-waters-guide.1717/ (and) https://www.gog.com/forum/risen_series/risen_series_for_linux
At first, I didn't set anything specific (not sure which version of Proton it used). The game launched out-of-the-box but some of the "videos" in the tutorial didn't play (audio for them still worked) and I was not able to connect to a Windows-hosted multiplayer session.
I tried a few protontricks things from this page as well as Proton-vGE 6.21-GE-2. And running with WINE_FULLSCREEN_FSR=1 gamemoderun %command%. This did solve the "video" not playing but not the multiplayer connectivity issue.
Per advice here, I forced steam to use 'Proton Experimental' (linked post describes process for enabling this). I didn't change my launch command and kept my existing compatdata and just launched it with Experimental. Was able to connect to the Windows-hosted session on the first try after that with no issues.
Works great or at least no worse than Windows
Couple crashes. Wasn't keeping count but less than 10 for the whole game. Did Ctrl+Alt+F2 and ran pkill then Ctrl+Alt+F7 to restore desktop and then relaunched. I had Steam Overlay and Steam Cloud Saves disabled.
Alt+Tab does NOT work correctly for this game (game always stays on top). I have other Proton and Wine games that it works fine for on the same system.
Proton version works well with mods but I have heard that native only partial supports them (possibly case-sensitivity related to scripts?). For save locations and more in-depth proton setup notes see my related post on gaming.stackexchange here
Same as previous report: doesn't start and no error messages displayed. Not seeing any processes matching 'pgrep -f Tiny' so seems like it just fails to start rather than process freezing before graphics are rendered.
I already had xboxdrv installed as I generally play with a controller so didnt have the issue some folks below reported in that regard. Out of the box, the game worked great except that spoken dialogue didn't play for me at all (sound effects such as weapons fire still worked, only voice dialogue did not). After perusing some of the comments here, I was able to fix it with the following (adjust path depending on install location): 0) pkill -9 -if warframe; 1) In the terminal, change PFX folder under compatdata dir for warframe - probably ~/.local/share/Steam/steamapps/compatdata/230410/pfx for most folks [mine was cd /gaming/steam/steamapps/compatdata/230410/pfx] 2) make sure you're in the pfx folder, then run: WINEPREFIX=$(pwd) winecfg 3) once the winecfg GUI comes up, Click on Libraries tab, enter "xaudio2_7" without the quotes in the textfield / dropdown where it says "New override for library" 4) Click the Add button 5) Click Apply then OK 6) Relaunch game 7) Enjoy
Since ProtonDB doesn't let me EDIT submissions that have been published, here's an UPDATE (my previous review was the one for this game from a couple days ago - -at submission time anyway-- that has same system specs and talks about "xaudio2_7" ; look for the one on MInt 19.1 on Nvidia 970).
After further testing, I have found that "FIX" for dialog audio also makes the game UNSTABLE AF... In the past hour, I have had 4 crashes during loading screens to either the initial hub/ship or an attempted co-op session. I had played yesterday and was able to do a mission in co-op but still had some crashes initially before we got in-mission. I would recommend just living without the dialog audio for now and wait for a future version of proton to fix it. Or possibly use the fix to have dialog for the single-player tutorials and then revert it afterwards (you can revert either via running winecfg again or simply delete the game's compdata folder and re-launch; proton will regenerate the folder using the default settings but no in-game settings/progress will be lost, just any custom wine settings). I would consider the status with the audio "fix" to be Bronze due to the crashes but Silver without them.
