Linux Support

Launch options:
PROTON_NO_ESYNC=1, PROTON_DUMP_DEBUG_COMMANDS=1 %command%
These I copied from tatsu's video

then my steamplay PROTON version:

(this was adviced in tatsu's video)

When I try proton 4.11-3 I suprisingly get "better" results

The game launches and what was a grey box for proton 5.0-9 is now the only portion of the screen that works.

@PA4SAM what graphics card & what driver version are you using?

also what linux distribution and what Desktop Environment?

(from your screenshot it looks like ubuntu 20.04 with ubuntu's gnome 3)

also just in case could you confirm that you right-clicked on forged alliance in the games list (and not another game),
selected "properties" and under "general" found the launch options put :

 PROTON_NO_ESYNC=1, PROTON_DUMP_DEBUG_COMMANDS=1 %command%

?

most likely is that you haven't installed any graphic driver.

could you also try with only one screen plugged in?

Microsoft buys Bethesda
https://www.youtube.com/watch?v=W7qI6kR2Ua4

i laughed when i commented under John Carmack tweet about this and all the MS NPCs appeared. I had to mute them because im not interested in their confused world.
https://twitter.com/foodlfg/status/1308078362972295176

Hello it is quite delayed but I found the solution to my problem.
I'll post it here now in case anybody has the same problem in the future.

Proton 5.0-9 didn't work for me however 4.11-13 did kind of work as I showed in the previous post. I (wrongly) assumed that the fact that most of the screen was black meant I couldn't click there. But it turns out you can, so the solution is to make a username and confirm it by clicking around in the black until you hit the confirm button. Then go to settings (by clicking around in the black) and change your primary adapter settings to any non windowed resolution (again by clicking around in the black) that will fix the visual glitch. From there you can actually set up the settings and resolution you want, which will carry over when you launch using the FAF client.

So @tatsu nothing is wrong with the tutorial, it seems maybe proton has some trouble with my unusual graphics card (quadro K1100M). You might however add some comment referring to this post in the description because I assume I won't be the only one who will experience this problem.

As for your previous troubleshooting questions:

1. yes I do have a graphics driver this was not the issue (it is a good thing to check if you have the same problem though. I'm no linux expert but I used this stackexchange post to figure it out.
2. Unplugging one screen made no difference.
3. I followed your tutorial to the letter so naturally I had the launch options put in correctly already. One thing I found that is nice though is that you can setup steamplay to launch with a particular version of proton on the same screen. Just go to the bottom of the same tab that contain the launch options and set it to the protonversion that you want. That way I can still have the new proton 5.0-9 version as my default and only use 4.11-13 for FA. For anybody with the same problem you do have to change out the generated runfile when you switch protonversions. So if you follow this fix and launching from faf doesn't work anymore, that is because the runfile is still the 5.0-9 version while steam is setup for the 4.11-13 version.

One thing I wonder about but couldn't figure out is if you could force faf to launch full screen instead of windowed mode from the launch options. If this is possible all the clicking around in the dark could be circumvented.

the best approach here is to set that proton version for FA-only. (yes in steam you can set individual versions for each and every game. just go into it's properties).

you can comment the link to this post in my youtube vid.

Big truble after update FAF client

and in console

zugduk@debian:~/faf$ ./downlords-faf-client
2020-09-28 15:35:38.253  INFO 21533 --- [JavaFX-Launcher] o.s.boot.SpringApplication               : Starting application on debian with PID 21533 (started by zugduk in /home/zugduk/faf)
2020-09-28 15:35:38.256  INFO 21533 --- [JavaFX-Launcher] o.s.boot.SpringApplication               : The following profiles are active: linux,prod
2020-09-28 15:35:38.334 ERROR 21533 --- [JavaFX-Launcher] o.s.b.d.LoggingFailureAnalysisReporter   : 

***************************
APPLICATION FAILED TO START
***************************

Description:

An attempt was made to call a method that does not exist. The attempt was made from the following location:

    org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:108)

The following method did not exist:

    'org.springframework.core.type.AnnotationMetadata org.springframework.core.type.AnnotationMetadata.introspect(java.lang.Class)'

The method's class, org.springframework.core.type.AnnotationMetadata, is available from the following locations:

    jar:file:/home/zugduk/faf/lib/spring-core-5.1.8.RELEASE.jar!/org/springframework/core/type/AnnotationMetadata.class
    jar:file:/home/zugduk/faf/lib/spring-core-5.2.7.RELEASE.jar!/org/springframework/core/type/AnnotationMetadata.class

The class hierarchy was loaded from the following locations:

    org.springframework.core.type.AnnotationMetadata: file:/home/zugduk/faf/lib/spring-core-5.1.8.RELEASE.jar


Action:

Correct the classpath of your application so that it contains a single, compatible version of org.springframework.core.type.AnnotationMetadata

2020-09-28 15:35:38.335 ERROR 21533 --- [JavaFX-Launcher] o.s.b.d.LoggingFailureAnalysisReporter   : 

***************************
APPLICATION FAILED TO START
***************************

Description:

An attempt was made to call a method that does not exist. The attempt was made from the following location:

    org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:108)

The following method did not exist:

    'org.springframework.core.type.AnnotationMetadata org.springframework.core.type.AnnotationMetadata.introspect(java.lang.Class)'

The method's class, org.springframework.core.type.AnnotationMetadata, is available from the following locations:

    jar:file:/home/zugduk/faf/lib/spring-core-5.1.8.RELEASE.jar!/org/springframework/core/type/AnnotationMetadata.class
    jar:file:/home/zugduk/faf/lib/spring-core-5.2.7.RELEASE.jar!/org/springframework/core/type/AnnotationMetadata.class

The class hierarchy was loaded from the following locations:

    org.springframework.core.type.AnnotationMetadata: file:/home/zugduk/faf/lib/spring-core-5.1.8.RELEASE.jar


Action:

Correct the classpath of your application so that it contains a single, compatible version of org.springframework.core.type.AnnotationMetadata

@ZugDuk
from which version to what version did you updated btw?

it is not that important tho. just download the client from github, extract and play, no need to update.
https://github.com/FAForever/downlords-faf-client/releases/tag/v1.2.1

i just did it and it works.

THANKS !!
Install to the clear folder is worked perfectly!

Yes you need to delete old files. If you just unpact the tar.gz old files might be left over that are then still loaded (those old files being wrong verison and therefore causing issues)

Hello, I recently installed FAF client on Linux Mint 19.3 w/Cinnamon. I was able to successfully play stock Forged Alliance on steam with Proton and those launch options. After following instructions I am able to get the client working for FAF. FAF appears to point to the correct location for the game install. However in spite of all of this, when I try to create a match or join one through the client, nothing happens. I don't even get an error message or any real indicator that something happened.

@Davebowman Game/Client log please.

@Davebowman
maybe this one?
https://wiki.faforever.com/index.php?title=Setting_Up_FAF_Linux#The_FAF_client_doesn.27t_launch_the_game

i might have done something wrong or forgot when setting up u can have a look at this video as well https://www.youtube.com/watch?v=Rv3ZXA4FNFk

@axel12 said in Linux Support:

@Davebowman Game/Client log please.

All I have is a client log: https://pastebin.com/HA0Y5M72

There is an iceadapterlogs folder too, do you want that as well?

@foodlfg said in Linux Support:

@Davebowman
maybe this one?
https://wiki.faforever.com/index.php?title=Setting_Up_FAF_Linux#The_FAF_client_doesn.27t_launch_the_game

Steam is installed and active, Forged Alliance is installed as well and it works with Proton stock.

@axel12 said in Linux Support:

i might have done something wrong or forgot when setting up u can have a look at this video as well https://www.youtube.com/watch?v=Rv3ZXA4FNFk

This is what I used as a guide. I followed it to the letter (except for uninstalling old client, since I have no old client).

2020-10-01 13:02:11.772 INFO 11646 --- [pool-3-thread-5] com.faforever.client.game.GameService : Forged Alliance terminated with exit code 2

@Davebowman The client starts the exe without wine /home/bowman/.faforever/bin/ForgedAlliance.exe
You must have missed the steps:

1. Make steam build a script
2. Copy that script from temp folder to a save location.
3. Enter that script under executable format in the client settings.

I am not sure if the steps are missing in the video but if so the video would be incomplete.

Read "Copy the Steam RUN script" in the wiki article!

I did miss that step, but have changed that and now I am able to join and create games. I tested in a 1v1 and was able to play through the entire game. Thanks for the help.

Proton 5.13-1 is out!
Test pls!

testing.

works brilliant for me. I got way faster game ForgedAlliance.exe boot-up time. nothing else to remark on.