Cervox
Published
Audio is not consistently working. When it does work, it keeps working, but it takes a lot of waiting to get to that point.
Audio seems to take a while to properly start loading, guns start off sounding weird and music is just not there. Takes time for all of it to start working, and I don't know what to do to make it work.
When you load into the game, all the textures will start at a very low resolution, then slowly the higher resolution textures get streamed in.
When in borderless windowed mode and trying to alt tab, doom kept trying to regain control of my mouse. And when you go into the steam overlay, the game still recognizes mouse movement, which can lead to misclicks.
I recommend this over the native version, everything is simply better here.
Trying to mute the audio ingame will not actually mute it, instead giving you some... Weird echo-y sound effects. Muting it outside of the game using your systems sound mixer will do the trick.
Fullscreen needs a work around for it to work properly. First, make sure in the game settings you're running at your native resolution in fullscreen. Then, outside of the game run the command "protontricks --gui" and then select echo. Then Select the default wine prefix > Run winecfg > Graphics > Emulate a virtual desktop. Then type in your native resolution and hit apply and close out of everything. If you use different values things will get buggy.
Cutscenes dont play. This is fixed with https://github.com/z0z0z/mf-install. Dont worry about messages about using a different wine version or it configuring the prefix, steam will correct it upon launch.
You'll need to install an extra thing to get elite dangerous up and running, don't worry, its simple, just copy and paste. Look into getting protontricks installed. Now, when running elite for the first time at all it will silently crash, this is expected, we still need to do this at least once so that the prefix is generated, allowing protontricks to mess with it. Once that is done, open a terminal and type in "protontricks 359320 -q dotnet472 win7". Let it run and ignore any errors. Once its finished the game will be able to launch! Now, you'll notice similar commands such as the one I gave you, except its "dotnet40". The long story short of it is, if you use "dotnet472" you'll get more performance then just with "dotnet40", in my case 5-10 fps more. No idea how or why, it just does, and if your still concerned, its what the lutris installer for elite dangerous installs. Now, in the event you've already installed "dotnet40" and want to upgrade to "dotnet472" the procedure is simple as well. We're just going to delete the prefix you have right now and make a new one. So type in the terminal "protontricks --gui" and select elite dangerous. Press ok to any warnings. Then make sure that "Select the default wineprefix" is selected and hit ok. Then select "Delete ALL DATA AND APPLICATIONS INSIDE THIS WINEPREFIX" and hit ok and say yes. Once thats done, launch elite again, it will silently crash like before but it will regenerate the wine prefix. Then run "protontricks 359320 -q dotnet472 win7" like before. Enjoy!
Few issues otherwise the game runs fine. The issues are: Changing volume using the volume slider on my headset displays a visual volume slider to tell me my volume level. If I do this while the game is in focus, the entire thing just gets this minor lag and it generally becomes advisable to relaunch. Same with alt tabbing I believe. I've just settled on pressing super and down the actions I need to, which doesn't result in any issues. Same goes with tabbing back in, its easier for me to use the super menu to tab back in then it is to alt tab back in. Oh, and sometimes the game will go black and not respond to my actions, forcing me to kill the process. But its not often enough to the point where its unplayable. Last time it happened it was when i was shutting down the game. I suppose it struggled to shut down.
Works fine on 4.11. Upgrading from 4.2-9 to 4.11 I got some errors about rundll32 or something, but I just ignored them and the game ran fine, and I haven't seen those errors since. Still need dotnet472 and win7 patches for it to work at all though.
I'm not sure what I did, but the game began full system locking my laptop. To the point where I had to hold the power button to forcefully restart the entire thing. Trying to downgrade to 4.2-9 was a similar pain in the ass with a few too many little things going wrong for me to explain. I specifically recall that one time if I had the elite dangerous window selected, my entire computer would lag by a few seconds, even mouse movement became laggy! Horrendous issues showing up on both proton versions. No idea what caused this.
The game simply just runs better on proton 4.2-9 instead of 4.11-1 with all the tweaks needed below. Hopefully 4.11 will improve but I can't recommend it if you want a stable and better framerate experience.
Those of you who wish to try the dotnet472 tweaks from a while ago and that are on ubuntu based systems will need to run "sudo winetricks --self-update" for the argument to work again.
Unlike trying to play the game using proton 5.0-10 with dotnet40, playing on 5.13 has been a flawless experience. Would recommend.
https://github.com/redmcg/wine-mono/wiki <-- Follow the simple instructions here to get the game running.
Every once in awhile there's just a single frame where things like lights get blocky before it goes back to normal. Nothing gamebreaking.
On first run when you're working to change your video settings (like changing to borderless window and raising the resolution to 1080p in my case) after you hit apply the elite dangerous window will shrink. Just relaunch the game and everything will be displayed properly again. Can't seem to reproduce it though afterwords, which is good.
Using Proton-6.16-GE-1 over Proton 6.3-6 fixes micro stuttering and makes the game 100% playable now, video playback and all.
Proton-6.16-GE-1 GloriousEggroll
https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/6.16-GE-1
Sometimes the game soft-locks when loading into a level, but it doesn't happen enough for it to be a serious issue. I just force close the game and reopen.
Video playback works normally, no audio crackling or anything like that. I've only played/used the Dx11 mode and it works quite fine.
Works out of the box flawlessly with Glorious Eggroll Proton. Alt Tab works just fine too
Proton-5.9-GE-6-ST GloriousEggroll
https://github.com/GloriousEggroll/proton-ge-custom/releases
I'm using a self compiled dxvk on version 1.7.1 with Sporif's async patch to not endure stutters.
The minor stuttering makes it unenjoyable, but not impossible to play
Every few seconds the game will stutter, really annoying.
A fun intro video does not play without mf-install, however this video plays after the main menu and going into a game, not before it. So you can make the prefix then do the mf-install.
Crashed once, but I'm chalking that up to the game being in early access.
When first downloading the game, it would not launch. I had to delete the prefix and let proton re-create it for it to finally launch. Also, when linking your epic games account, the game will try to launch a browser for you to sign into. Chrome does not work, i had to switch my default browser to firefox for it to work.
Disabling esync makes sound not be distorted. D9VK makes the game run properly.
Controller does not work, but keyboard does. After relaunching a few times I began to experience audio static.
I used to use GloriousEggrolls proton version but I kept having some stuttering issues that weren't related to shader compilation, so I swapped to the normal version of proton (4.11) and added the following launch command: WINEDLLOVERRIDES="xaudio2_7=n,b" %command% and its simply ran beautifully. Frametimes are so much better on 4.11 then using Eggrolls package, which was proton-4.11-GE-1. The only two issues are 1. Sometimes if I launch the game the audio gets crackly, but you hear that its happening before you even login so its as simple as relaunching the game, then it goes away. You also still have the bug where the game will crash if you don't have a controller plugged in, so I followed the instructions here to fix it: https://gitlab.com/GloriousEggroll/warframe-linux/wikis/Ubuntu-Install-Instructions Step 7 spesifically. And if the game still crashes after a few minutes I just run the following command in the terminal and it fixes itself "xboxdrv --daemon --detach". Otherwise it runs great!
Just a note, for some reason the launcher does not display a progress bar when its downloading new content/updates, and stays stuck at "checking for new content". When in reality it is actually downloading all the updates and stuff like that, it's just for some reason not displaying this.TLDR: Launcher visually gets stuck on "Checking for new updates". Nothing broke, its actually downloading updates, its just not giving you a progress bar.
This solution is an alternative to using both either the WINEDLL override or using glorious eggroll's custom proton to get audio working. I do this since I experienced diminished audio quality when using the WINEDLL override. First, install winetricks (and if you're on an ubuntu based system run "sudo winetricks --self-update" afterwords and say yes to prompts.) then install protontricks. Then run this command "protontricks 230410 -q faudio". Viola, audio.
You need to go into the audio settings within the game and switch the reverb from advanced to legacy to fix audio popping/crackling issues with transmissions and the like.
The launcher has a lot of black artifacts/boxes by default, this can be fixed by opening the launcher settings, turning off launcher gpu acceleration, then restarting the launcher.
Occasionally when launching the game a crash reporter will pop up saying something broke, but whatever prompted it to show up does not seem to affect the game itself, which runs just fine.
The game will have constant dxvk shader compilation stutters (Every time a new effect or visual is rendered for the first time, the game will stutter as it compiles the effect for the first time, but will save the result to a cache to reuse later).
You can either deal with it and wait for it to get better as you play along and compile all the shaders, or you can go down the rabbithole of compiling DXVK with async enabled. Which reduces stuttering immensely.
The resources to do so can be found here:
https://github.com/Sporif/dxvk-async
https://github.com/Tk-Glitch/PKGBUILDS (Of interest to you will be the dxvk-tools folder and possibly the mostly portable gcc folder. If the latter folder is of interest to you, know that you only need to compile mingw, no need for gcc here.)
Runs great, perfect.
Retro arcade audio doesn't play, but this is insignificant. Its a mini-game you can skip over or never interact with in the first place.
If you use the go live feature with discord, the games frametime gets a bit worse and audio from discord gets mildly distorted from time to time. Its not horrible though and you can live with it.
