Supreme Commander (9350)

CPU: Intel(R) Core(TM) i5-7600 CPU @ 3.50GHz
GPU: NVIDIA Corporation GeForce GTX 1060
Driver: 396.54-0ubuntu0~gpu18.04.1
OS: Linux Mint 19 MATE Tara (64 bit)
Kernel: 4.15.0-33-generic
RAM: 16 GB

When just launching the game without any workarounds I only get a blank grey square.

I'm able to get the game running using a number of workarounds.

First I had to change the game's launch options to the following:

PROTON_NO_ESYNC=1 %command%

After this change I could hear the in-game audio but only got a black screen.

Next I had to disable bloom render, since the retail version of Forged Alliance has the same issue as this with Wine+dxvk. So I just worked with the assumption that bloom render was patched in to the Steam version of Supreme Commander, which would explain the similar symptoms.

So I navigated to the games appdata folder:

/home/%USER%/.steam/steam/steamapps/compatdata/9350/pfx/drive_c/users/steamuser/Local Settings/Application Data/Gas Powered Games/SupremeCommander/

I opened the Game.prefs file in a text editor and added the following to the options_overrides section:

bloom_render = {
    default = 0
}

Now the game started and I could create a profile in-game. I went to the video options and set everything to maximum except setting fidelity at medium and leaving bloom render turned off.

These options can also be set directly in the Game.prefs file under the options sections under the profile section like this:

fidelity = 1,
bloom_render = 0

After these workarounds I was able to play the game, but there are still some issues.

The game tends to freeze when changing video settings through the built in options screen. The only way to recover is to kill the process and restart the game.

The game also often freezes when trying to exit normally. The only way to recover is to kill the process.

Start by reproducing the blank grey or black screen on the reported Linux setup, then test the documented PROTON_NO_ESYNC=1 launch option and bloom_render settings. Inspect the mentioned Game.prefs path and verify whether video-setting and normal-exit freezes remain. The issue does not name a source file, test, or specific requested fix.