Linux Support

tatsu

make sure steam is running.

i dunno what to say works utterly brilliant for me.

nine2

step 1. uninstall linux

foodlfg

step 1. uninstall linux

hehe funneh!
just support monopolistic giga corporations with you everyday life decisions.
that are cannot be controlled by society at all. in fact, people are exposed to their decisions. they directly associate with corruption. it makes sense.
https://www.youtube.com/watch?v=Ag1AKIl_2GM

foodlfg

@tatsu said in Linux Support:

make sure steam is running.

i dunno what to say works utterly brilliant for me.

how does your Proton 5.13 run file look like?
this is mine. the PATH variable is noticeably shorter in it:
https://gist.github.com/foodlfg/d104c6d42e14d6929a0e8626c8edaeb6#file-supcom-proton513-run-file

BigMamaMurder

I was hoping for some fix for the missing effects but alas it's still the same.

foodlfg

@Whatsisname
what is about your Proton 5.13 run file btw?
working fine?

vitautart

Hi, can't understand what's wrong with my setup. I tried to follow instructions, on first launch it exits with code 1, says that wine can't find freetype2 fonts family, so I install 32 version of it, and error gone.

Now when I try to create game, It does nothings, logs give me exit with code 0. Like this

2020-11-08 13:29:58.803 INFO 4686 --- [ Thread-110] c.f.client.fa.ForgedAllianceService : Starting Forged Alliance with command: [/home/vitautart/apps/faf/client/1.2.2/run, /home/vitautart/.faforever/bin/ForgedAlliance.exe, /init, init.lua, /nobugreport, /log, /home/vitautart/.faforever/logs/game_13067128.log, /gpgnet, 127.0.0.1:21521, /mean, 1892.75, /deviation, 301.084, /savereplay, gpgnet://127.0.0.1:33127/13067128/vitautart.SCFAreplay, /country, UA, /numgames, 7] in directory: /home/vitautart/.faforever/bin
wineserver: using server-side synchronization.
Setting breakpad minidump AppID = ****
Steam_SetMinidumpSteamID: Caching Steam ID: ****************** [API loaded no]
2020-11-08 13:30:00.506 INFO 4686 --- [pool-3-thread-2] com.faforever.client.game.GameService : Forged Alliance terminated with exit code 0
2020-11-08 13:30:00.832 INFO 4686 --- [ Thread-110] c.f.client.fa.relay.ice.IceAdapterImpl : ICE adapter terminated normally

System: ArchLinux
WM: dwm
Proton 5.13

Vanilla FA works fine in steam.

foodlfg

@vitautart
yeh. i have the same problem with Proton 5.13
Steam generates a different run file for Proton 5.13 than for the previous ones.
if you want to track down the issue, i would start there.

meanwhile. use an older Proton version.

btw the wiki is not saying to use Proton 5.13, it is not in the compatible list...
it says "Proton 5.0-9 (recommended)"

vitautart

@foodlfg
Thanks. Downgraded proton version in steam to 5.0, and all works. Seams like there is some bugs with 5.13 proton run script.

tatsu

guys that happens if you close steam.

callcifer

Anyone else getting crashes with replays? Pretty much every replay crashes for me at random times, sometimes 10 minutes in to the replay, sometimes 30.

This is with Proton 5.0 and Nvidia 455.38 drivers.

tatsu

no. no replay crashes for me.

proton : 5.13-1
nvidia : 450

it's probably the nvidia 455 driver. that sound a bit too hot off the press.

callcifer

I'm pretty sure I've had the replay crashes for a while now, long before 455 but I've never tried Proton 5.13, let me test with that.

callcifer

@tatsu said in Linux Support:

guys that happens if you close steam.

This is also very weird because with Proton 5.0 and below you never had to have Steam running.

EDIT: This can be fixed by removing "steam.exe" from the last line of your "run" file.

callcifer

OK with Proton 5.13 I have no crashes so far, 40 minutes into a game.

I've also just realized I've been playing with D3D9 all this time! I just switched to D9VK and the game is soo much smoother!

Now, my only remaining issue is all the missing effects but I guess there is no solution to that

tatsu

@callcifer said in Linux Support:

EDIT: This can be fixed by removing "steam.exe" from the last line of your "run" file.

mmhhh TY

@callcifer said in Linux Support:

I just switched to D9VK

how'd you do that?

foodlfg

@tatsu said in Linux Support:

guys that happens if you close steam.

no, it is not because of that. as i said:

if i just run the run 5.09 file from terminal the original game launches.
if i run the 5.13 file nothing happens. it is working with launching from Steam, but not from terminal or from the client.

i ran the two files after each other. one worked the other one does not.
if steam had not been running then the first one would not have worked either.

only 5.09, 4.xx run file generates properly for me.
5.13 does not

foodlfg

@callcifer
it is hard to test for long games but as for me:

Proton 5.09 - 2x long setons games, 2x crashed at 30min
Proton 4.11 - tested today with palying a 1+ hour long setons game. worked fine and it worked back then too.

expect crashes. and test for it.
the game is not 100% stable with Wine / Proton.
we dont know why.

callcifer

OK there seems to be some confusion. Here's where I stand.

Actual gameplay is stable for me with both 5.0 and 5.13.
Replays almost always crash with 5.0 but never with 5.13.

@foodlfg said in Linux Support:

if steam had not been running then the first one would not have worked either.
only 5.09, 4.xx run file generates properly for me.
5.13 does not

This is not correct in my experience. Before 5.13 I never had to have Steam running to play FAF. What has changed with 5.13 is that Steam generates a slightly different run file. With 5.0 and earlier the last line of the file ended with:

bin/wine" "${@:-${DEF_CMD[@]}}"

but with 5.13 it became

bin/wine" steam.exe "${@:-${DEF_CMD[@]}}"

So instead of executing SupremeCommander.exe directly with wine, 5.13 instead calls steam.exe which in turn launches the game. That's why 5.13 doesn't work if Steam isn't running. Still, as I've said, you can fix this very easily by removing steam.exe from that line and everything will work correctly.

@foodlfg said in Linux Support:

the game is not 100% stable with Wine / Proton.
we dont know why.

Again, not in my experience. I've had zero stability issues with Proton 3.16 and 5.13. The only problematic ones for me were 4.11 (caused desyncs) and 5.0 (caused replay crashes).

@tatsu said in Linux Support:

I just switched to D9VK

how'd you do that?

With Proton 5.0 and above Proton defaults to D9VK instead of Wine D3D9 so you don't have to do anything special. If DXVK_HUD=1 shows you the DXVK hud in game then you are using D9VK. Of course, you can try to force enable D9VK with PROTON_USE_D9VK=1

tatsu

oh ok if it's default then perfect.