I think it is something steam related.

If I launch the client without steam open it works fine, if I then load steam I get the error, if I then close steam the error remains, but if I close both down and only have the client open it works again.

If your game crashed, replay is not generated (if I'm not mistaken, happens to me at least when the game does crash/is killed via process).

sent a DM

@mazornoob Changing the directory worked, thanks. I'm somewhat annoyed that it was just that easy, but thank you nonetheless!

b37689b3-ebaa-4194-bfdb-6d813788108b-image.png

You only actively get logged out when there is a failure to refresh your access token. We have to log out then because we can't use the API fully until you reauthorize.

the same problem, the same error, on two differen OS.

Known bug, being worked on

Ah thank you. I haven't played FAF for years, just got into it again a couple weeks ago. Glad to see the community is still going strong.

My friend received his activation email this afternoon. Thanks for the replies! I'll sign up for the Discord too. 🙂

Even if your profile is public you also need your games list to be public ("Game details: Public")

Your steam account name can be different.
If you can't login to steam for resetting password, you will also not be able to link any new account to steam even if we delete the old account. So fix your steam account first.

The FAF client bundles with a 64bit Java runtime. We dropped official support for 32bit ~3 years ago.
All modern CPUs for the last 15 years support 64bit except for Intel Atoms which won't run Forged Alliance anyway, all Windows versions since Windows 7 had a 64bit edition on launch 2009 (even XP had one, but that launched four years aftetr release in 2005).
There is no reason to run a 32bit Windows in 2022.

(BUMP)