Thanks for the tipp, this could be the problem. I looked at my folder and found it.
I think this folder whas not there until i started a game an faf created this one.

I look into my magic crystal ball and it says approximately Sunday 13th August between 6pm and 7pm.
While that sounds a bit sarcastic (and it is), it's a good guess too 🙂

We have already fixed the hydrocarbon issue:
https://github.com/Uveso/BlackOpsFAF-Unleashed/pulls?q=is%3Apr+is%3Aclosed

Now Jip is hunting some script errors that happen with drones.
After he found the issue we will be able to do the patch.

As far as i know there are no more gamebreaking errors.
Assuming you can't find any more 😉

But even with smaller errors I will make an update, so that we at least have a working version.

Does it work when you disable/uninstall Hitman Pro?

Was he an observer? As I often have an issue where I cant kick observers. Most of the time, I can un-ready, go observe and kick him. Sometimes even that wont work; but that is a rarety .

Starting with observers for me also gives a likely chance for my game to crash.

I noticed this other message on another thread for your reference :
https://forum.faforever.com/topic/6343/who-is-paralon-shutting-down-lobbies

AFAIK your windows username C:/Users/DYLAN(~1 is causing issues - Create a new windows user without any fancy symbols - Install FAF and Supreme under that account and try again.

@Roni19 Do you have a Steel Series headset?

Everything is going great as usual, thank you very much 🙂

Solution for me was - i have a headset with virtual instances(eg. multiple profiles for chat/game)- once i deactivated all that and there was only one device left it worked just fine. Now i just deactivate all the steelseries sonar/virtual surround stuff before i play FAF.

@giantrubberduck i am getting the same problem but when i tried to link faforever with steam account from my android based phone it works you can also try to link from your phone.

same issue

Thanks magge will do

Look, we devs did something right 🙂 . Glad to hear it worked out

This thread may help: https://forum.faforever.com/topic/4093/can-t-autorizate/7?_=1688673862482

Thank you so much, that helped. I can start it again. 🙂

So, I turned on IPV6 in FAF settings, choose COTURN server Finland (no server was chosen before), turned on experimental debugger. And it started connecting 80-90% times (it's ok for me, because it was around 0% for the last week and much earlier). Maybe this information will help somebody.

@Jip sorry if didnt respond earlier but thanks for fixing it, Your support to the FAF community is always greatly appreciated!

Ive just downloaded 2023.5.0 and trying to loging for first time on this PC and am getting this error.
Was there ever a specific solution?