I have launched the game through steam with the following launch options

PROTON_USE_WINED3D=1 PROTON_NO_ESYNC=1 PROTON_NO_FSYNC=1 PROTON_DUMP_DEBUG_COMMANDS=1 %command%

then ran the two protontricks commands recommended in the wiki and they seem to complete without error. There is a warning about wine 32-bit prefixs

./protontricks 9420 dlls d3dx9
./protontricks 9420 dlls xact

After these two steps game runs fine when launching from steam. However trying to launch from the generated run file produces a black screen. The black screen seems to be a mechanically working menu since I can click in game buttons. Just not visually.

Step 8 of the wiki says "in which you edit out steam.exe" which I have not done as I am not quiet sure what it means. So may be the problem.

I am running this on the manjaro distro with amd opensouce gpu drivers.

If anyone has encountered this before I would greatly appreciate if you have a solution

@kubkolienka sorry for the slow reply I have been tied up with family matters.

I have tried removing the PROTON_USE_WINED3D=1

This causes this error to pop up when running the run file. When running from steam it makes the intro cut scene run about a frame a second

I am running using the opensource video-linux drivers for amd

I then tried changing the DEF_CMD too DEF_CMD=("/home/nogthar/.faforever/bin/ForgedAlliance.exe"). Seems to still load into a blank window. When I hover the mouse over the window it makes the audio noises of the buttons and shows the correct mouse cursor.

I appreciate the help and please let me know if you have any other ideas

@kubkolienka Here is the run file as generated. This is without the change to DEF_CMD

#!/bin/bash
#Run game or given command in environment

cd "/home/nogthar/.local/share/Steam/steamapps/common/Supreme Commander Forged Alliance"
DEF_CMD=("/home/nogthar/.local/share/Steam/steamapps/common/Supreme Commander Forged Alliance/bin/SupremeCommander.exe")
PATH="/home/nogthar/.local/share/Steam/steamapps/common/Proton - Experimental/files/bin/:/usr/bin:/bin" \
	TERM="xterm" \
	WINEDEBUG="-all" \
	WINEDLLPATH="/home/nogthar/.local/share/Steam/steamapps/common/Proton - Experimental/files/lib64//wine:/home/nogthar/.local/share/Steam/steamapps/common/Proton - Experimental/files/lib//wine" \
	LD_LIBRARY_PATH="/home/nogthar/.local/share/Steam/ubuntu12_64/video/:/home/nogthar/.local/share/Steam/ubuntu12_32/video/:/home/nogthar/.local/share/Steam/steamapps/common/Proton - Experimental/files/lib64/:/home/nogthar/.local/share/Steam/steamapps/common/Proton - Experimental/files/lib/:/usr/lib/pressure-vessel/overrides/lib/x86_64-linux-gnu/aliases:/usr/lib/pressure-vessel/overrides/lib/i386-linux-gnu/aliases" \
	WINEPREFIX="/home/nogthar/.local/share/Steam/steamapps/compatdata/9420/pfx/" \
	SteamGameId="9420" \
	SteamAppId="9420" \
	WINEDLLOVERRIDES="steam.exe=b;dotnetfx35.exe=b;beclient.dll=b,n;beclient_x64.dll=b,n" \
	STEAM_COMPAT_CLIENT_INSTALL_PATH="/home/nogthar/.local/share/Steam" \
	WINE_LARGE_ADDRESS_AWARE="1" \
	GST_PLUGIN_SYSTEM_PATH_1_0="/home/nogthar/.local/share/Steam/steamapps/common/Proton - Experimental/files/lib64/gstreamer-1.0:/home/nogthar/.local/share/Steam/steamapps/common/Proton - Experimental/files/lib/gstreamer-1.0" \
	WINE_GST_REGISTRY_DIR="/home/nogthar/.local/share/Steam/steamapps/compatdata/9420/gstreamer-1.0/" \
	MEDIACONV_AUDIO_DUMP_FILE="/home/nogthar/.local/share/Steam/steamapps/shadercache/9420/fozmediav1/audiov2.foz" \
	MEDIACONV_AUDIO_TRANSCODED_FILE="/home/nogthar/.local/share/Steam/steamapps/shadercache/9420/transcoded_audio.foz" \
	MEDIACONV_VIDEO_DUMP_FILE="/home/nogthar/.local/share/Steam/steamapps/shadercache/9420/fozmediav1/video.foz" \
	MEDIACONV_VIDEO_TRANSCODED_FILE="/home/nogthar/.local/share/Steam/steamapps/shadercache/9420/transcoded_video.foz" \
	"/home/nogthar/.local/share/Steam/steamapps/common/Proton - Experimental/files/bin/wine64" c:\\windows\\system32\\steam.exe "${@:-${DEF_CMD[@]}}"

@fractal switching to proton 4.11-13 seemed to be the solution. Now when running the run file in terminal or having it launched by the faf client it works.

Thanks @kubkolienka and @fractal for your time! I really appreciate the help!

In the replay https://replay.faforever.com/14521056 around the 27 min mark I get a t2 air factory and give it a way point to the left. I had torp bombers queued in the factory and when they were built out of the factory they got stuck in the air instead of flying to the way point. I was wondering if this was a known bug or if there is some way to mitigate air getting stuck when built. Thanks for the help in advance!