The current pre-release of the client ("pioneer" in the version) is only compatible to itself. So you can only play with other testers. Please be aware!

Subcategories

  • 29 Topics
    260 Posts
    maudlin27M
    FAF's rules are set out on the main FAForever website - by accessing FAF services, you agree to the rules outlined there, which are supplemental to the FAF Terms of Service. For details of how to report rule breaches and/or how the rules are enforced, please refer to the separate page on moderation Separate contribution guidelines exist for those considering contributing to FAF, while there are also official tournament rules that apply to official FAF tournaments.
  • 940 Topics
    5k Posts
    SaverS
    Hi, The issue is known, and a fix is currently being worked on. https://github.com/FAForever/fa/pull/7119
  • Please provide detailled logs and/or error messages!

    991 Topics
    4k Posts
    C
    Hi! Since July 16 I can't join or host any game — FA launches, reaches the lobby, then hangs on "Connecting..." forever. The ICE debug window and telemetry stay completely empty: no peers, no gathering, nothing. From my logs the game processes CreateLobby fine and the client receives GameState Idle → Lobby, but after that no JoinGame / HostGame / ConnectToPeer ever arrives, so the ICE adapter is never asked to connect to anyone. My lobby connection itself looks healthy the whole time (join requests get responses, I even got a game_not_ready error back once, and the game list keeps updating live). Last working game: July 15. Same silent behavior on client 2026.1.0 and after updating to 2026.4.1 — ~12 attempts across 6+ different games.
  • 39 Topics
    155 Posts
    wilson_W
    Dear Commander, are you willing to learn and improve your game play? If your answer is yes, the FAF Dojo is the place to be. What You Can Expect From The FAF Dojo A (mostly) voice-based community of 500+ players from all over the world Like-minded people willing to improve A wide range of skill levels (0-2000+) An experienced trainer team (incl. several top 50 players) Replay reviews Training sessions (as a group) Training sessions (1on1) In-house tier lists resembling the ranks of a Judo school 1v1 Team games (”global”) A wide variety of options to practice Sparring (trainees only - unrated) Sparring (trainees and trainers - unrated) 1v1 challenges TMM queue Events Tournaments Community nights (e.g. a dedicated 1v1 Night) What The FAF Dojo Expects From You Participating requires a functioning set of headphones and microphone, or a headset Keeping a positive and supportive atmosphere Once you reach a certain level, you might want to consider giving back by becoming a trainer yourself How do I join the FAF Dojo? Check out our Notion page to find out more about our trainers (incl. several official trainers from the FAF Discord), tournaments (1v1, 2v2, 3v3), and more. If our system appeals to you, we would gladly welcome you on our Discord server. Cheers.
  • How I cam fix lags FAF 09/2021 ?

    2
    0 Votes
    2 Posts
    202 Views
    J
    @tyhig2 You might have the nvidia bug. Is it lagging more if you move the mouse? Then you should update your nvidia drivers or install the nvidia fix ui mod. Bit weird for that to occure now (was mainly an issue couple months ago) but some other people also got it recently out of nowhere.
  • Game crashed and replay crashes too

    2
    0 Votes
    2 Posts
    141 Views
    L
    debug: Loading module '\000/units/dalk003/dalk003_script.lua\000' info: CWldSession::DoBeat() unknown entity id (0x2ff000b4) supplied in a pose update. warning: Error running OnRelease script in <deleted object>: ...mdata\faforever\gamedata\lua.nx2\lua\maui\button.lua(84): Game object has been destroyed stack traceback: [C]: in function `Play' ...mdata\faforever\gamedata\lua.nx2\lua\maui\button.lua(84): in function <...mdata\faforever\gamedata\lua.nx2\lua\maui\button.lua:78> warning: Connection dialogue opening due to disconnection by players: info: send Ptr: 77CF0002 info: send Ptr: 77CF0002 info: send Ptr: 77CF0002 info: terminated info: Sending game result: 2 defeat -10 info: SSB >>> TRACE GameResults: result = defeat -10, armyID = 2, name = Kavat info: SSB >>> TRACE GameResults: Kavat has been defeated by Kavat info: SSB >>> TRACE AnnounceDeath [ZFG] Kavat has been defeated by [ZFG] Kavat info: SSB >>> TRACE OnBeat() player has died: Kavat debug: Loading module '\000/effects/entities/debrisboneattachchassis01/debrisboneattachchassis01_script.lua\000' debug: Loading module '\000/effects/entities/scudeath01/scudeath01_script.lua\000' debug: Loading module '\000/effects/entities/scudeathshockwave01/scudeathshockwave01_script.lua\000' info: CWldSession::DoBeat() unknown entity id (0x2ff002c9) supplied in a pose update. info: CWldSession::DoBeat() unknown entity id (0x2ff002cb) supplied in a pose update. debug: Loading module '\000/effects/entities/debrisboneattachhigh01/debrisboneattachhigh01_script.lua\000' info: Sending game result: 4 defeat -10 info: SSB >>> TRACE GameResults: result = defeat -10, armyID = 4, name = Tatheil info: SSB >>> TRACE GameResults: Tatheil has been defeated by Tatheil info: SSB >>> TRACE AnnounceDeath [FF] Tatheil has been defeated by [FF] Tatheil info: SSB >>> TRACE OnBeat() player has died: Tatheil info: send Ptr: D6FE0002 info: send Ptr: D6FE0002 info: send Ptr: D6FE0002 info: send Ptr: D6FE0002 info: send Ptr: D6FE0002 info: send Ptr: D6FE0002 info: send Ptr: D6FE0002 info: send Ptr: D6FE0002 info: send Ptr: D6FE0002 info: send Ptr: D6FE0002 warning: Connection dialogue opening due to disconnection by players: info: send Ptr: D6FE0002 info: send Ptr: D6FE0002 info: send Ptr: D6FE0002 info: terminated info: Minimized true
  • game crash

    2
    0 Votes
    2 Posts
    158 Views
    JipJ
    This particular crash is fixed by this PR, it is already available in FAF Develop and on Monday part of the patch!
  • Linking Steam Account (Expired Ticket) & Log In Error

    3
    0 Votes
    3 Posts
    155 Views
    D
    Thanks I refreshed the cache, but logging out and in manually worked.
  • Game Crashs

    12
    1 Votes
    12 Posts
    1k Views
    H
    My error, seems only slightly different in the lines: java.lang.RuntimeException: Forged Alliance Crashed with exit code 1. See C:\ProgramData\FAForever\logs\game_15430702.log for more information at com.faforever.client.game.GameService.lambda$spawnTerminationListener$43(GameService.java:676) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) at java.base/java.lang.Thread.run(Thread.java:832) Hope it helps
  • This topic is deleted!

    2
    0 Votes
    2 Posts
    32 Views
  • 0 Votes
    14 Posts
    555 Views
    T
    @brutus5000 That doesn't make sense because we have been playing for years on the client, and once the account is linked to Steam it cannot be unlinked. He tried to link his account last night and it said it was already linked as well. But that's fair, please look further into the issue later! Have a good night.
  • HELP PLS

    5
    0 Votes
    5 Posts
    272 Views
    K
    @sheikah fix doesn't work
  • Game Crashes

    3
    1 Votes
    3 Posts
    231 Views
    T
    I too have crash at 23:03 MSK. FAF not connected. And at 23.09.2021 FAF have fix and 2 my compuuters begin lagg. 2 comp in another 2 providers in another 2 home. java.util.concurrent.CompletionException: org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://hydra.faforever.com/oauth2/token": Connect to hydra.faforever.com:443 [hydra.faforever.com/116.202.155.226] failed: Connection timed out: connect; nested exception is org.apache.http.conn.HttpHostConnectException: Connect to hydra.faforever.com:443 [hydra.faforever.com/116.202.155.226] failed: Connection timed out: connect at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(CompletableFuture.java:314) at java.base/java.util.concurrent.CompletableFuture.completeThrowable(CompletableFuture.java:319) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1803) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1792) at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:290) at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1016) at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:1665) at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1598) at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:183) Caused by: org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://hydra.faforever.com/oauth2/token": Connect to hydra.faforever.com:443 [hydra.faforever.com/116.202.155.226] failed: Connection timed out: connect; nested exception is org.apache.http.conn.HttpHostConnectException: Connect to hydra.faforever.com:443 [hydra.faforever.com/116.202.155.226] failed: Connection timed out: connect at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:784) at org.springframework.web.client.RestTemplate.execute(RestTemplate.java:710) at org.springframework.web.client.RestTemplate.postForObject(RestTemplate.java:436) at com.faforever.client.api.TokenService.retrieveToken(TokenService.java:105) at com.faforever.client.api.TokenService.loginWithRefreshToken(TokenService.java:99) at com.faforever.client.user.UserService.lambda$loginWithRefreshToken$3(UserService.java:86) at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1800) ... 6 more Caused by: org.apache.http.conn.HttpHostConnectException: Connect to hydra.faforever.com:443 [hydra.faforever.com/116.202.155.226] failed: Connection timed out: connect at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:156) at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:376) at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393) at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) at org.springframework.http.client.HttpComponentsClientHttpRequest.executeInternal(HttpComponentsClientHttpRequest.java:87) at org.springframework.http.client.AbstractBufferingClientHttpRequest.executeInternal(AbstractBufferingClientHttpRequest.java:48) at org.springframework.http.client.AbstractClientHttpRequest.execute(AbstractClientHttpRequest.java:66) at org.springframework.web.client.RestTemplate.doExecute(RestTemplate.java:775) ... 12 more Caused by: java.net.ConnectException: Connection timed out: connect at java.base/sun.nio.ch.Net.connect0(Native Method) at java.base/sun.nio.ch.Net.connect(Net.java:574) at java.base/sun.nio.ch.Net.connect(Net.java:563) at java.base/sun.nio.ch.NioSocketImpl.connect(NioSocketImpl.java:588) at java.base/java.net.SocksSocketImpl.connect(SocksSocketImpl.java:333) at java.base/java.net.Socket.connect(Socket.java:648) at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:368) at org.apache.http.impl.conn.DefaultHttpClientConnectionOperator.connect(DefaultHttpClientConnectionOperator.java:142) ... 25 more
  • crashes happening randomly 1 out 10 games approximately

    8
    0 Votes
    8 Posts
    464 Views
    JipJ
    @Breezy1 We need logs, especially from the debugger when it involves a crash. See also this topic. For now, make sure to play on the FAF Develop branch.
  • Trouble with Steam link

    4
    0 Votes
    4 Posts
    328 Views
    RoweyR
    https://imgur.com/m008i0y make sure it looks like this you can reset it after the steam link!
  • Crash while playing

    3
    0 Votes
    3 Posts
    164 Views
    JipJ
    If it is a hard-crash then it is not. We need the information from the debugger, you can see an example in this post
  • Modding Regeln

    7
    0 Votes
    7 Posts
    434 Views
    SaverS
    Danke dir.
  • 2 Crashes in 2 games. New patch unstable.

    9
    0 Votes
    9 Posts
    482 Views
    T
    Thanks, I'll check it out
  • dfc_windows-x64_1_5_0.exe ERROR pls help

    4
    0 Votes
    4 Posts
    225 Views
    N
    i have that same problem
  • Trouble confirming i own the game on steam

    2
    0 Votes
    2 Posts
    139 Views
    SwkollS
    I've sent a pm.
  • CPU rating is REALLY DOWN after latest patch

    11
    0 Votes
    11 Posts
    677 Views
    GiebmasseG
    They offloaded some stuff to other threads mid-development, even if the effect doesn't look too big nowadays I think the game would've been pretty unplayable if they didn't do it. Some info about it: http://www.slideshare.net/guest40fc7cd/threading-successes-02-supreme-commander There were some benchmarks that compared single vs multithreaded performance of supcom during the launch era too, running it multi-threaded had quite big advantages. Saw it some time ago but can't find it now.
  • 0 Votes
    2 Posts
    154 Views
    JipJ
    Please share the report of the debugger tool - we're already on top of one specific hard-crash that so far the majority of the reports indicated.
  • Crashing game help please

    2
    0 Votes
    2 Posts
    7k Views
    JipJ
    That is a crash code that I have not seen before. Does anything in this issue on Github sound familiar? edit: added link
  • Game crashing

    2
    0 Votes
    2 Posts
    152 Views
    JipJ
    We need the full log of the debugger - please share that with us next time it happens. We're on top of one particular issue that causes a lot of hard-crashes (90% of the reports so far are related to that one particular file), that will be hotfixed next Monday.