Finally posting on the blog again! (Don't expect a weekly post or anything though; I'm mainly going to use this as a platform to share the things I've learned through troubleshooting, etc. I'll post content whenever I feel the need to.)
The only problem is that it doesn't actually work properly out of the box.
And so I stumbled upon a Steam Community post on this very topic. Except you don't need to (and in fact shouldn't) do most of the stuff it tells you to do.
-screen-fullscreen 0" (without the quotes). That's it. For whatever reason, the game doesn't load properly if it starts in full screen. Once it loads up, it will go into full screen and allow you to set the resolution for the game, etc.
The problem with their solution
chmod 777 /to temporarily elevate root, and then change it back to
755afterwards (the problem was that he was trying to create a shortcut on the filesystem root). First of all, if you run that command as a normal user, it will throw a permissions error, i.e.:
chmod: changing permissions of '/': Operation not permitted
Second, if you actually do change the permissions of a folder to 777 (or worse, do it recursively), then you are opening up that folder for any user on the system to be able to read or write from it, regardless of whether they own the file or not. If you do that on the filesystem root, the results could be catastrophic. Don't do that to yourself.
The moral of the story is this: don't go blindly copying and pasting commands from the internet without first knowing what the commands are doing to your system. Especially if they have a
sudotacked on the front.
Anyhow, I'd also like to mention performance issues on Linux, since no one else seems to be talking about it.
After a couple of performance tweaks, I'm getting around 60 FPS most of the time, with dips down to 45 FPS and minimum tearing, at the highest graphical settings, vsync off, at 1080p.