Is there anyway to set a tier cap when using the M28AI in the campaigns of Sup Com and FA? Booted up the first mission of Sup Com and before too long I was being swarmed by Tier 3 units which my paltry Tier 1 units could not counter!
Was planning to replay campaign with AI teammates. Then tried to use m28... sadly for some reason when ever i used it.. the units name are f*ck for some reason... i dont use any mods other than m28ai... is there a fix for this? or a mod problem?
Idk, I like to imagine the Striker as a light armored vehicle, not as a tank.
Hello everyone,
I'm trying to get Forged Alliance Forever (FAF) running on Linux Mint, but I'm stuck with a rather strange issue. I have been trying for several hours now to get a solution but for now I gave up. I have been bug hunting with ChatGPT and asked it to summarize everything. Maybe it helps someone else, who is a bit more knowledgeable in the field:
The important part: FAF itself starts and works normally, but when I launch a game, no game window appears at all. The FAF client immediately reports:
>
I have spent quite a few hours troubleshooting this and have already ruled out several obvious causes.
I'm therefore wondering whether this is a Linux/FAF launcher issue, or whether there is something specific about how FAF launches its patched ForgedAlliance.exe under Wine.
The Steam version of Supreme Commander itself runs successfully through Wine.
FAF launches the following executable:
/home/fringillus/.faforever/bin/ForgedAlliance.exe
The client reports commands such as:
Starting Forged Alliance with command:
[%USER_PROFILE%/.faforever/bin/ForgedAlliance.exe,
/init, init.lua,
/nobugreport,
/log, %USER_PROFILE%/.faforever/logs/game_27556111.log,
/gpgnet, 127.0.0.1:46543,
/mean, 1618.550048828125,
/deviation, 471.0350036621094,
/savereplay, gpgnet://127.0.0.1:40953/27556111/%CPU_NAME%.SCFAreplay,
/country, DE,
/numgames, 11,
/numgames, 1]
Immediately afterwards, FAF reports Exit Code 2.
There is no game window and, importantly, the expected game_*.log is not created.
I tested the actual Steam executable directly:
cd ~/.steam/steam/steamapps/common/Supreme\ Commander\ Forged\ Alliance/bin
wine SupremeCommander.exe
echo $?
This exits with:
0
So Wine is capable of launching the 32-bit Supreme Commander executable.
The executable is detected as:
PE32 executable (GUI) Intel 80386, for MS Windows, 7 sections
The FAF executable produces a DXVK log:
info: Game: ForgedAlliance.exe
info: DXVK: v1.10.3
and successfully detects my GPU:
info: NVIDIA GeForce RTX 3060 Ti:
info: Driver: 580.173.2
info: Vulkan: 1.4.312
So DXVK initializes and Vulkan detects the NVIDIA GPU correctly.
There is no obvious DXVK/Vulkan initialization failure in the log.
The Wine environment was also checked.
wine cmd /c echo %USERPROFILE%
returns:
C:\users\fringillus
and:
wine cmd /c echo %USER%
returns:
fringillus
The Steam installation path resolves correctly through Wine:
winepath -w ~/.steam/steam/steamapps/common/Supreme\ Commander\ Forged\ Alliance
returns:
Z:\home\fringillus\.steam\steam\steamapps\common\Supreme Commander Forged Alliance
~/.faforever/fa_path.lua contains:
fa_path = "/.steam/steam/steamapps/common/Supreme Commander Forged Alliance"
The FAF initialization files use this fa_path to mount the Steam installation:
MountDirectory(fa_path .. "/movies", '/movies')
MountDirectory(fa_path .. "/sounds", '/sounds')
MountDirectory(fa_path .. "/maps", '/maps')
MountDirectory(fa_path .. "/fonts", '/fonts')
The path is therefore not simply an untested/unknown Steam path.
One manually generated FAF test log contains:
info: Loading custom vault path: /My Games/Gas Powered Games/Supreme Commander Forged Alliance
followed by:
info: DISK: AddSearchPath: 'z:\home\fringillus\.faforever\gamedata\lobby_coop.cop', mounted as '/'
...
info: DISK: AddSearchPath: 'z:\home\fringillus\.faforever\sounds', mounted as '/sounds/'
It then successfully gets as far as:
info: Hooked /lua/userInit.lua with /schook/lua/userInit.lua
info: Hooked /lua/globalInit.lua with /schook/lua/globalInit.lua
debug: Lua user environment initialized with game version 3836, game type FAF
info: Compiled shader: /effects/cartographic.fx
info: Compiled shader: /effects/frame.fx
info: Compiled shader: /effects/mesh.fx
...
info: SHADERS COMPILED
So the FAF executable can actually initialize a substantial part of the game engine.
There are warnings such as:
warning: Search path element "Z:\.steam\steam\steamapps\common\Supreme Commander Forged Alliance\movies" does not match any files
warning: Search path element "Z:\.steam\steam\steamapps\common\Supreme Commander Forged Alliance\sounds" does not match any files
warning: Search path element "Z:\.steam\steam\steamapps\common\Supreme Commander Forged Alliance\maps" does not match any files
warning: Search path element "Z:\.steam\steam\steamapps\common\Supreme Commander Forged Alliance\fonts" does not match any files
However, this appears to be related to the way the game constructs its search paths, because the actual files are accessible through the fa_path used by the FAF initialization scripts.
There is also:
warning: SND: Error initializing 3D audio.
Global Settings not loaded
and:
warning: Movie "/movies/thqlogo.sfd" doesn't exist.
warning: Error opening movie /movies/thqlogo.sfd
The game nevertheless continues through shader compilation.
The FAF directory contains:
ForgedAlliance.exe
ForgedAlliance_d3d9.log
ForgedAlliance.dxvk-cache
init.lua
init_faf.lua
init_nonxt.lua
SupComDataPath.lua
SupComDataPathFAF.lua
...
The FAF executable is:
/home/fringillus/.faforever/bin/ForgedAlliance.exe
whereas the Steam installation contains:
/home/fringillus/.steam/steam/steamapps/common/Supreme Commander Forged Alliance/bin/SupremeCommander.exe
Both are 32-bit Windows PE executables.
I have already gone through the following:
%USERPROFILE%%USER%fa_path.luainit.lua, init_faf.lua, init_nonxt.luaAt this point I don't think repeatedly changing the Wine prefix or Steam path is likely to be productive.
What could cause the FAF-specific ForgedAlliance.exe to terminate with Exit Code 2 immediately under Wine, while:
SupremeCommander.exe runs normally through Wine,Could there be a known incompatibility between the current FAF Linux launcher/scripts and the patched ForgedAlliance.exe?
I'm especially interested in whether there is a way to obtain the actual Windows/Wine exit status or crash information from the FAF executable, since the normal game_*.log isn't created when the client launches it.
Any ideas or debugging suggestions would be very much appreciated.Hello everyone,I'm trying to get Forged Alliance Forever (FAF) running on Linux Mint, but I'm stuck with a rather strange issue.The important part: FAF itself starts and works normally, but when I launch a game, no game window appears at all. The FAF client immediately reports:Forged Alliance Crashed with exit code 2I have spent quite a few hours troubleshooting this and have already ruled out several obvious causes. The most interesting finding is that the exact same FAF installation works without problems on a separate Windows partition on the same machine.I'm therefore wondering whether this is a Linux/FAF launcher issue, or whether there is something specific about how FAF launches its patched ForgedAlliance.exe under Wine.SystemOS: Linux Mint
Architecture: x86_64
GPU: NVIDIA GeForce RTX 3060 Ti
NVIDIA driver: 580.173.2
Vulkan: 1.4.312
DXVK: 1.10.3
Wine: installed and working
FAF client: 2026.7.0
FAF game version: 66 / game executable version 3836
Steam installation of Supreme Commander: Forged AllianceThe Steam version of Supreme Commander itself runs successfully through Wine.What happensFAF launches the following executable:/home/fringillus/.faforever/bin/ForgedAlliance.exe
The client reports commands such as:Starting Forged Alliance with command:
[%USER_PROFILE%/.faforever/bin/ForgedAlliance.exe,
/init, init.lua,
/nobugreport,
/log, %USER_PROFILE%/.faforever/logs/game_27556111.log,
/gpgnet, 127.0.0.1:46543,
/mean, 1618.550048828125,
/deviation, 471.0350036621094,
/savereplay, gpgnet://127.0.0.1:40953/27556111/%CPU_NAME%.SCFAreplay,
/country, DE,
/numgames, 11,
/numgames, 1]
Immediately afterwards, FAF reports Exit Code 2.There is no game window and, importantly, the expected game_*.log is not created.The Steam game itself worksI tested the actual Steam executable directly:cd ~/.steam/steam/steamapps/common/Supreme\ Commander\ Forged\ Alliance/bin
wine SupremeCommander.exe
echo $?
This exits with:0
So Wine is capable of launching the 32-bit Supreme Commander executable.The executable is detected as:PE32 executable (GUI) Intel 80386, for MS Windows, 7 sections
DXVK / VulkanThe FAF executable produces a DXVK log:info: Game: ForgedAlliance.exe
info: DXVK: v1.10.3
and successfully detects my GPU:info: NVIDIA GeForce RTX 3060 Ti:
info: Driver: 580.173.2
info: Vulkan: 1.4.312
So DXVK initializes and Vulkan detects the NVIDIA GPU correctly.There is no obvious DXVK/Vulkan initialization failure in the log.Wine environment / pathsThe Wine environment was also checked.wine cmd /c echo %USERPROFILE%
returns:C:\users\fringillus
and:wine cmd /c echo %USER%
returns:fringillus
The Steam installation path resolves correctly through Wine:winepath -w ~/.steam/steam/steamapps/common/Supreme\ Commander\ Forged\ Alliance
returns:Z:\home\fringillus\.steam\steam\steamapps\common\Supreme Commander Forged Alliance
FAF's configured game path~/.faforever/fa_path.lua contains:fa_path = "/.steam/steam/steamapps/common/Supreme Commander Forged Alliance"
The FAF initialization files use this fa_path to mount the Steam installation:MountDirectory(fa_path .. "/movies", '/movies')
MountDirectory(fa_path .. "/sounds", '/sounds')
MountDirectory(fa_path .. "/maps", '/maps')
MountDirectory(fa_path .. "/fonts", '/fonts')
The path is therefore not simply an untested/unknown Steam path.Interesting log outputOne manually generated FAF test log contains:info: Loading custom vault path: /My Games/Gas Powered Games/Supreme Commander Forged Alliance
followed by:info: DISK: AddSearchPath: 'z:\home\fringillus\.faforever\gamedata\lobby_coop.cop', mounted as '/'
...
info: DISK: AddSearchPath: 'z:\home\fringillus\.faforever\sounds', mounted as '/sounds/'
It then successfully gets as far as:info: Hooked /lua/userInit.lua with /schook/lua/userInit.lua
info: Hooked /lua/globalInit.lua with /schook/lua/globalInit.lua
debug: Lua user environment initialized with game version 3836, game type FAF
info: Compiled shader: /effects/cartographic.fx
info: Compiled shader: /effects/frame.fx
info: Compiled shader: /effects/mesh.fx
...
info: SHADERS COMPILED
So the FAF executable can actually initialize a substantial part of the game engine.There are warnings such as:warning: Search path element "Z:\.steam\steam\steamapps\common\Supreme Commander Forged Alliance\movies" does not match any files
warning: Search path element "Z:\.steam\steam\steamapps\common\Supreme Commander Forged Alliance\sounds" does not match any files
warning: Search path element "Z:\.steam\steam\steamapps\common\Supreme Commander Forged Alliance\maps" does not match any files
warning: Search path element "Z:\.steam\steam\steamapps\common\Supreme Commander Forged Alliance\fonts" does not match any files
However, this appears to be related to the way the game constructs its search paths, because the actual files are accessible through the fa_path used by the FAF initialization scripts.There is also:warning: SND: Error initializing 3D audio.
Global Settings not loaded
and:warning: Movie "/movies/thqlogo.sfd" doesn't exist.
warning: Error opening movie /movies/thqlogo.sfd
The game nevertheless continues through shader compilation.FAF executable vs Steam executableThe FAF directory contains:ForgedAlliance.exe
ForgedAlliance_d3d9.log
ForgedAlliance.dxvk-cache
init.lua
init_faf.lua
init_nonxt.lua
SupComDataPath.lua
SupComDataPathFAF.lua
...
The FAF executable is:/home/fringillus/.faforever/bin/ForgedAlliance.exe
whereas the Steam installation contains:/home/fringillus/.steam/steam/steamapps/common/Supreme Commander Forged Alliance/bin/SupremeCommander.exe
Both are 32-bit Windows PE executables.The most important control testI have now also installed FAF on a second Windows partition on the same physical computer.There, FAF starts games normally.This means that the game account, FAF installation itself, and the hardware are not inherently incapable of running FAF.The problem appears to be specific to the Linux/Wine environment or to the way the Linux FAF installation launches the FAF-specific executable.Things already testedI have already gone through the following:Wine installation/environment
%USERPROFILE%
%USER%
Wine path conversion
Steam installation path
fa_path.lua
FAF Lua initialization files
Steam game executable directly through Wine
32-bit executable compatibility
DXVK initialization
Vulkan
NVIDIA driver
GPU detection
FAF's generated executable
FAF logs
FAF game logs
FAF's Steam data mounting
manual examination of init.lua, init_faf.lua, init_nonxt.lua
reinstalling/testing FAF
comparison against a working Windows installationAt this point I don't think repeatedly changing the Wine prefix or Steam path is likely to be productive.My current questionWhat could cause the FAF-specific ForgedAlliance.exe to terminate with Exit Code 2 immediately under Wine, while:the Steam SupremeCommander.exe runs normally through Wine,
DXVK/Vulkan initializes correctly,
FAF's Lua/game initialization gets quite far when tested manually,
and FAF works normally on Windows on the same hardware?Could there be a known incompatibility between the current FAF Linux launcher/scripts and the patched ForgedAlliance.exe?I'm especially interested in whether there is a way to obtain the actual Windows/Wine exit status or crash information from the FAF executable, since the normal game_*.log isn't created when the client launches it.Any ideas or debugging suggestions would be very much appreciated.