
Redeyed
Published
Worked out of the box with default proton version. I literally just hit play and it worked.
Infinite loading after menu
First start the game just hangs. Using latest stable version (6.3) the game goes to the initial menu but hangs when pressing start. Using proton version 4.11 the game loads indefinitely after using "protontricks 893180 -q wmp9" to try to make it behave.
Without tinkering, the games never connects to a lobby.
Plays perfectly, 220 fps. No audio issues. Latest proton handles sound better than 5.X, and i have rumble too in the gamepads.
PROTON_NO_ESYNC=1 %command%
With no tinkering, I had flickering artifacts on the grass, and streaks on some objects. Lowering settings did not make them disappear.
please see this comment https://www.reddit.com/r/SteamDeck/comments/yr1j5k/comment/kpnnsiz/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
Game is unplayable without tinkering because proton forgets to install direct X , and you have to install it manually. Other than that, runs fine.
I had to add %command% -onethread to start the game, otherwise the game would crash on startup. So it was a bit tricky to set up in my case. Once done, eveything works fine. Also, if using the WINED3D trick, the lighter would not emit light.. In short:: use "%command% -onethread" and nothing else.
The wide screen fix is almost mandatory at this point. You can find it here: do not forget to use the launch options I provided.
WINEDLLOVERRIDES="d3d8=n,b" %command%
If not launched using the 32 bit option(eg. 102476832), you will have serious color banding. BEWARE: 32 bit resolutions are listed BEFORE 16 bit ones.
I had JPG errors thown at me because Ryzen are a new architecture the gamne doesnt know. Use a patched versio of rlmfc.dll for that.
After some tinkering the game runs great, but the first steps might be painful.
This report is for the EGS version of the game. I installed EGS using Lutris, then the game, then added a non-steam game in Steam that pointed to the .exe file, using the default version of proton.
I had to use the game in windowed fullscreen mode for it to be stable.
Go to the settings.ini file and set AsyncComputeDisable to 1. Game was very unstable before that..
I needed to do the following to get the program to work properly. Its quite the same as TheKing reported, but I also needed to alter the volume in alsamixer:
Protontricks:
protontricks 221680 sound=alsa
protontricks 221680 winecfg
Wine configuration Audio tab changes:
Input device: “In: Rocksmith USB Guitar Adapter”
Voice input device: “In: Rocksmith USB Guitar Adapter”
Speaker configuration: “Out: default”
Pavucontrol: Configuration tab: Set Rocksmith Adapter Profile to Off.
Alsamixer:
Set the volume of Rocksmith Adapter to around 75%, otherwise the calibration will not work.
3d engine is meh. Texture pop-in, loading textures, lod loading in your face, loading times, stuttering. That aside, its SS4.
Use OpenAL in the game options, or no sound. Also, use directx11, or crash on alt-tab.
Use openAl, or no sound.
Texture pop-in, minor stuttering, shitty antialisaing.
Direct X install fails during installation
The game wont start afterwards.
A workaround is to use the Lutris scriupt here https://lutris.net/games/the-maw/. It will install Steam using wine, then install the game from a "Wine" Steam. That allows the game to install and play properly. Wine Steam is super glitchy, but the game plays fine.
Use ext4, and everything should work fine. See below.
Please note that you must install the game on a ext4 partition (just like other games like gtaV or fall guys) and not a ntfs one, in order for proton to work properly. Don't ask me why, baffles me, but the filesystem makes a difference. On a ntfs partition the game would go to the main menu, play the first cutscence, and then hang or black screen on versions 3.X of proton. On newer versions, it would just instacrash.
On a ext4 partition everything works fine out of the box. Tested with both steam and gog versions.
The main game and the tutorial run fine. Both have been tested several hours. Performance is smooth, and the 3dfx Glide plugin works nicely.
The only thing that doesn't work is massive tearing during cut-scenes (the video ones, not the in-game ones). Video is still distinguishable, but barely. Changing renderer from opengl to another value doesnt help.
Also, alt-tabbing to desktop crashes the game.