LINUX SUPPORT IS HERE

[BlackYps]

it turns back to normal behavior when the minimap is off, Resources option doesn't matter.
Normal splitscreen works fine actually. It's the cartographic option, that causes weird behavior. When I switch one of the split views to cartographic it shows the same behavior like when the minimap is enabled. Because the minimap is always in cartographic this even makes sense in a certain way.

I guess that this problem and the inability to render certain effects is caused by the same underlying problem.

[Cyborg16]

Question: what is your game launch command for Downlord's client?

If I use the following:

Code: Select all

steam -applaunch 9420

... then the game is launched by Steam but exits immediately:

Code: Select all

Failed to setup initial search path.

Program : Z:\PATH\SteamLibrary\steamapps\common\Supreme Commander Forged Alliance\bin\SupremeCommander.exe
Cmd line arguments : /init init.lua /nobugreport /log /home/USER/.faforever/logs/game.log /gpgnet 127.0.0.1:38573 /mean 1509.47 /deviation 91.1863 /savereplay gpgnet://127.0.0.1:37027/9746775/Cyborg16.SCFAreplay /country GB /clan GB /numgames 1110

Callstack:
    unavailable.

Last 100 lines of log...

warning: Can't open lua file "Z:\PATH\SteamLibrary\steamapps\common\Supreme Commander Forged Alliance\bin\init.lua"


My interpretation of the above is that Steam always launches the game from its install path instead of using the current directory (/home/USER/.faforever). Is there some way to force Steam to use the right directory?

[tatsu]

@Cyborg16 follow my signature (for automation) or this link (for DYI) : https://github.com/foodlfg/Supreme-Comm ... tall-guide

[Cyborg16]

Interesting script Tatsu. Anyway, I managed to extract what I need, so thanks! For others (this assumes you already have Steam, Forged Alliance, and one of the FAF clients installed):

• In Steam, set the Forged Alliance launch options to:

  Code: Select all

  PROTON_NO_ESYNC=1, PROTON_DUMP_DEBUG_COMMANDS=1, PROTON_USE_GALLIUM_NINE=1, PROTON_GALLIUM_NINE_MODULEPATH="/usr/lib/i386-linux-gnu/d3d/d3dadapter9.so.1:/usr/lib/x86_64-linux-gnu/d3d/d3dadapter9.so.1" %command%

• Launch Forged Alliance. While it is running, copy the 'run' script from

  Code: Select all

  /tmp/proton_USER/run

  to some FAF directory (I used ~/.faforever)
• Close the game and open the FAF client. Under settings, set the game location to

  Code: Select all

  PATH/SteamLibrary/steamapps/common/Supreme Commander Forged Alliance

  and command line to

  Code: Select all

  /home/USER/.faforever/run %s

  (or wherever you copied the 'run' script)

[foodlfg]

if you are interested in how you should set up the client on Linux without the script, read about it in the faf wiki:
https://wiki.faforever.com/index.php?ti ... _FAF_Linux

[tatsu]

that is a guide for the python client and for an outdated build. I don't think a custom python build that supports ICE is in the repos. also it says to use wine not proton, which doesn't work great.

I dunno why you linked this at all. it's critically outdated.

@Cyborg16 yeah I'd hoped more tech-saavy people would just be able to read through my script and glean what they need.

for the ...less tech saavy, I imagine it could be quite helpful.

[foodlfg]

it's not since like a half a year. read again.
as for the python part, it's outdated, true, but it is stated at the beginning of the article. it's there for historical reasons.

[Cyborg16]

You're right foodlfg; I should have looked there.

I'm having problems setting keyboard shortcuts: Alt + almost any key results in some kind of mouse grab (in a few cases opening debug windows). From memory this may not be a Linux issue but do you remember the solution?

[tatsu]

it's not a linux "issue" it's just those are system-level keybings. for ubuntu the solution is simple, simply open your keybindings and change alt + F2 ect ect ect... to other keybindings or unbind them. I imagine under other linuxes as well.

you can also change the keybind to something not already taken by the OS in the game.

[Cyborg16]

It's not Alt+F2. It's things like Alt+S, Alt+U, and many more. I think they may be SupCom debug bindings?