Specify custom resolution in XCom

I found that the "servers are too busy" message was thrown basically any time an error prevented the game (Borderlands 2 in my case) from launching. It was certainly not in any way related to the Steam servers, and pretty unfortunate that it so misleadingly masks some specific problem with the system.

After much trial and error, based on clues on the Wine AppDB reports and such, I was able to get it running by installing various dependencies and stuff. Unfortunately, I failed to properly document my adventure, but here are a few things I did that you might want to try:

• With winetricks or directly with wine, install: vcredist vcrun2008 vcrun2010 msxml3 winhttp physx
• With your native package manager, install: lib32-mpg123 gpgme libassuan
• Make sure DirectX is installed in the wine environment
• Launch the game by running wine Borderlands2.exe from command line (no symlinks!)

For better performance, I also ended up creating a swapfile, and tweaking the wine registry to recognize all 2GB of my video card's RAM -- it defaulted to only addressing up to 128MB or something crazy like that.

Hope this helps! Good luck.

It turns out somebody at Feral is actually reading crash reports. I received an e-mail from them out of the blue today:

This issue is being caused because the installation path is on a separate location to the game preferences. Your preferences data is on the main boot drive of the machine, but the game installation is on a separate drive.

We are working on an update for the game that will allow it to be launched from an external location - this should be ready in the next couple of days. If you wish to workaround the issue yourself, please delete the game from the separate drive by dragging the application to the Trash, then run the Steam client on your main boot drive and download the game to that drive. Once installed, launch the game from the installed location on the main boot volume.

Since my boot drive is a small SSD, I had installed the game on a separate drive to save space. Moving it to the boot drive fixed the crash.

Hopefully this helps anyone else who is running into the same problem.

(Note: As of almost two months later, the update they mentioned has not materialized)