@sheikah After a while I can say that this solution helped me, the client does not crashes anymore and authorization is good

java.lang.IllegalStateException: State returned by user service does not match initial state at com.faforever.client.login.LoginController.lambda$initialize$13(LoginController.java:235) at com.sun.javafx.binding.ExpressionHelper$SingleChange.fireValueChangedEvent(ExpressionHelper.java:181) at com.sun.javafx.binding.ExpressionHelper.fireValueChangedEvent(ExpressionHelper.java:80) at javafx.beans.property.ReadOnlyStringPropertyBase.fireValueChangedEvent(ReadOnlyStringPropertyBase.java:72) at javafx.beans.property.ReadOnlyStringWrapper.fireValueChangedEvent(ReadOnlyStringWrapper.java:103) at javafx.beans.property.StringPropertyBase.markInvalid(StringPropertyBase.java:111) at javafx.beans.property.StringPropertyBase.set(StringPropertyBase.java:145) at javafx.scene.web.WebEngine.updateLocation(WebEngine.java:434) at javafx.scene.web.WebEngine$LoadWorker.dispatchLoadEvent(WebEngine.java:1364) at javafx.scene.web.WebEngine$PageLoadListener.dispatchLoadEvent(WebEngine.java:1239) at com.sun.webkit.WebPage.fireLoadEvent(WebPage.java:2524) at com.sun.webkit.WebPage.fwkFireLoadEvent(WebPage.java:2369) at com.sun.webkit.network.URLLoaderBase.twkWillSendRequest(Native Method) at com.sun.webkit.network.HTTP2Loader.lambda$willSendRequest$14(HTTP2Loader.java:497) at com.sun.webkit.network.HTTP2Loader.lambda$callBackIfNotCanceled$10(HTTP2Loader.java:437) at com.sun.javafx.application.PlatformImpl.lambda$runLater$10(PlatformImpl.java:428) at java.base/java.security.AccessController.doPrivileged(AccessController.java:391) at com.sun.javafx.application.PlatformImpl.lambda$runLater$11(PlatformImpl.java:427) at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:96) at com.sun.glass.ui.win.WinApplication._runLoop(Native Method) at com.sun.glass.ui.win.WinApplication.lambda$runLoop$3(WinApplication.java:174) at java.base/java.lang.Thread.run(Thread.java:832)

These are very strange stack traces. We'll look at it, but it is likely only your system that is having these type of errors. There are also sound errors in your log: [image: 1633849380634-78187c4f-1c7d-492a-b3e0-53658e2bb2d7-image.png] Did you see the topics on the forum about sound errors?

The error message you posted does not have enough detail. You need to post the info from the game log (the file "game_15476601.log")

@vmkcom We can't reproduce it through the replay - it is therefore likely local to your system. Update your drivers and anything else related to the stability of your system.

doesnt work in my case

I'll take the handsome and young any time. Jokes aside, I do appreciate the apology, and I think I'm not the only one thinking that. I'd like to emphasize what Axel said - there's than just developers in this community. There are content creators, content managers (news team), artists in general, developers (game related, client related, server related), server / system administrators (for the ddos mitigations, for example), testers and of course - gamers . We all make this community what it is, and that is why I personally appreciate your apology.

This is a known issue with client 1.6.0 and some users dns configuration. You can try using the beta client for the next version found here https://github.com/FAForever/downlords-faf-client/releases/tag/v2021.10.0-beta1 User have reported it resolves the issue.

@triple-x1 we started a thread about it 14 days ago; please continue there: https://forum.faforever.com/topic/2572/

The day we stop development on FAF, the day FAF will start slowly dying. I wrote an article about why: https://forum.faforever.com/topic/285/software-is-aging-and-what-it-means-for-faf

Quite confident that these are all pre-patch. If it keeps happening, attach the information of the debugger

LOUD is specifically oriented on large maps, large unit counts and play against the AI. FAF has always been essentially oriented on smaller maps with lower unit counts aimed primarily at PvP play.

The internal error is likely unrelated. Would need to know which portal you are logging into when you get that error. You do not need proof of game ownership for your account to be able to log in and post on the forum. So you can log in with C_P and post here. In order to log into the client, lobby server, and play the game you do need to have proof of game ownership. This is why only CP can login to the client. C_P cannot because it is not linked, it also cannot be linked to your steam account because each steam account can only be linked to one faf account. You can log into the forum with CP and then you can post as that user. The accounts themselves share no data between them in our databases. It is probably only logging you in here as C_P because you have remember me set.

@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.

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

This particular crash is fixed by this PR, it is already available in FAF Develop and on Monday part of the patch!

Thanks I refreshed the cache, but logging out and in manually worked.