TomBombadillo
Published
A previous report mentioned a fix for AMD users by way of Mesa. I don't know if the fix has been accepted yet, but until then, you can set the fix in the game's launch options.
glx_extension_override=-GLX_OML_swap_method %command%
If you want a little extra performance, this might help.
glx_extension_override=-GLX_OML_swap_method %command% r_useThreadedRenderer 2 r_usePortals 1 r_useOptimizedShadows 1 +com_allowconsole 1
Brink doesn't perform as well as I think it should, given that other games on the same engine run quite smooth (native or Wine/Proton). I don't know if it's me or the game itself, but I do recommend you turn some of the fancier settings off.
Hit a payphone first thing and see if the save file bug affects you, before you waste your time like I did.
Some large black flickering pixels appeared around the edges of some objects during the first run of the game. Tweaking my graphics settings did not help. This seems to have gone away on its own, but I have yet to reach another nighttime segment to be sure.
This is the real reason I made this report. I'm using a kernel with fsync support enabled, but the game needs to use esync instead or it can't create save files. Using these launch options fixed the issue for me: "PROTON_NO_FSYNC=1 PROTON_NO_ESYNC=0 %command%"
The game would hang every time I tried to exit. The launch options also fixed this.
