Ook
Published
Won't start no matter what version of Proton I use
protontricks --verbose 1715130 --force vcrun2019
I tried protontricks --verbose 1715130 --force vcrun2019 as many other recommend, but it did not help. I've tried every version of proton steam shows as available, as well as several GE version. You click Play, it flashes and goes back to Play. The game just won't start. IDK what to do to get past this point. Crysis 2 and 3 work perfectly. Crysis 1 remastered won't start.
Works very well
From time to time the mouse would cause the POV to spin in a circle very fast. Switch to windowed mode via alt-enter to restore mouse movement to normal.
- Works great but only with Proton version 4.2-9. Otherwise it on startup and won't run.
- Sometimes, when entering battle, the mouse input will suddenly accelerate to 100x normal speed, making it unusable. This is a very old problem, I've seen this for years. When it happens, Alt-Enter to switch to windowed mode, or better yet just run it in Windowed mode. This returns/keeps mouse input normal.
- Player eyes are pitch black. No color. Except for Morrigan. Not sure why.
None
The only thing I had to do was make sure to use GE 7.18. It used to run with 6.21, but a recent launcher update broke that. Works flawlessly with GE 7.18
Performance is adequate. Not stellar, but on medium it plays well enough.
Note: Different people here post somewhat different launch options. Not all of them work! To get it to work for me required exactly the following: WINEDLLOVERRIDES=”xaudio2_7=n,b” PROTON_NO_ESYNC=1 %command%
I know a lot of people do different things to get sound working, but alas, none of them work for me. The game is dead silent.
I can't get sound to work no matter what I do. Remove openal32.dll, doesn't work. Launch options that others describe, doesn't work. Edit BIOEngine.ini as others describe, doesn't work. Different versions of proton, including GE and Experimental, doesn't work. There is sound in the menu, but once the game itself starts, it is dead silent.
Once I figured out how to get sound working, it runs great.
This is an update to my previous report. The ONLY thing that worked to get sound working was to rename OpenAL32.dll in ~/.steam/steamapps/common/Mass Effect/Binaries. NOT the one in system32, NOT the one in syswow64. This file, and only this file, seems to be the culprit. No INI file tweaks were needed, no command line options were needed nor did they work when I tried them. Simply rename this one file and sound magically started working.
Different people describe different fixes for the no-sound problem. Find the one that works for you, as apparently no one thing works for everyone. Read ALL of the reports of what people did, maybe one will work for you?
Getting the Launcher to run without crashing is tricky. If I start with Proton version 6.x, experimental or GE, then it will never work. If I delete the prefix and start with Proton 5.0.10, then the Launcher will run. The prefix it creates doesn't have a Documents directory under users/steamuser. It has "My Documents" linked to users/steamuser/Documents, but this Documents directory does not exist. So if I symlink my real /home//Documents to the users/steamuser/Documents, then the Launcher will run, the game can be run from the launcher, and it will see all of my old saves (Don't do this if you don't know exactly what you are doing). But even with this, it will crash if I click the Downloads button. If you just press the big triangle-play button, the game will launch.
I think there is still something wrong with the prefix that Steam/Proton creates. I have a old prefix that I created a long time ago. If I use my own wine, in this case Wine-staging 6.18, the Launcher works and is rock solid. I can add all kinds of content, and run the game anytime I want. I wish I knew what was different about this old prefix. At the end of the day, I can get it to work through Steam, but if I want stability I have to run it from outside of Steam with an old prefix.
PS Installing dotnet and this-or-that pre-requisite did not help.
Origin won't start, but crashes with a "serious error".
Can't get Origin to run. Not sure why, it works in my own wine prefixes. Something about the prefix steam creates, the wine version Steam uses, keeps it from running. And of course, no Origin, no The Sims 4.
When you install the game via Steam it automatically adds "PROTON_USE_WINED3D=1" as a launch option. I saw no reason to change this.
I had to increase the open file limit to get The Sims 4 to work. Once I did that, it works great! With the default open file limit of 4096, it would not work. At all. I increased it to 16384, and all of the problems went away.
If you experience crashing, or it just won't start, try increasing your open file limit. Instructions can be found here (https://wiki.winehq.org/FAQ#Too_many_open_files.2C_ulimit_-n_probably_needs_to_be_increased). WARNING - do this with extreme caution as you can break your installation if you are not careful.
I have played all the way to Act II, 83 hours in game. If I use the second launch option, which I think is DX9, I get black screen on startup. I have to use the first launch option to get it to work. Performance is excellent thanks to DVXK. HOWEVER, it also crashes regularly with DVXK errors in the console, and so far I have not found a solution to this other than to not use DVXK. Also, if I set focus away from game and back again, it will lock up or otherwise stop responding. I have not found any tweaks to get around this, therefore according to the rating system, I have to give this a SILVER rating. It is playable, but save often because it will crash often.
