Update ... I can set a new preset .... seems my old saved presets are lost.

@amygdala That is very interesting because I had disabled all notifications. Unchecking the box for the "After game review" notification in the notification settings in FAF did resolve this issue though.

Thank you for your help.

I did the update three times and realized you have to install it directly and not as an update which worked for me. If it helps.

I don't have a Steam deck or a Linux machine in general, but you could join the Discord and search for discussions on the topic, I know there have been a few.

@larens It looks like your Windows username has non-ASCII or Cyrillic characters in it which the FAF client can't read/write to.

What you'll need to do is either create a new folder for where FAF will store your maps/mods, such as in the FAF Data Location itself (default is C:\ProgramData\FAForever), a folder at the root of your main drive or on an external drive, & then go to FAF client > top left menu > Settings > Forged Alliance Forever > Maps and Mods Location > Choose... & select the folder you just created or select an already existing folder that isn't located within your Windows user directory.

@nicholasporan No chatGPT stuff my dude. We're talking to humans here.

I can't click on the top left menu 😄

Could you tell me where the path to the logs folder is?

EDIT: Found it in appdata. I'll edit the main message.

"Listening" means that some program is waiting on that port for connections, which means the port is blocked for other porgrams.
Behing 'listening' there should be a number, which is the PID (process ID) of the program that is using (listening on) the port.

The link i gave also describes how to get the name of the porgram from that number ("How to match the process ID to a program").

Once you know which software is blocking the port, you can decide on a solution:

Killing the program once when you want to play FAF Uninstalling the program permanently ...

@adastranoob Alright, thank you

And 9 out of 10 will be right!

It's already been reported in Discord but a fix hasn't been implemented yet.

Thanks for reporting it though.

OK cheers

@clint089 Sweet! I'll put the word out, will report if there are any issues.

@magge Thanks a lot

There is a known bug that causes the client to try and reconnect to the chat after being closed that could use the CPU. It should be fixed in the next client version