Baraban

In my case, the last client update fixed the bug.

Hi, This is this an old bug. Not fixed yet. If you succeed to join again (there's a workaround in low graphics in the thread), you can try to create your company or join a company. It seems to fix it.

I think this is this bug :

I can't create my company because I can't go in game I tried low graphics ( worked 2 times , but seems no more working) and to launch other game in the same time to slow the game . Is there other workaround ?

No you're not alone. I cannot play for a week.

E4 doesn't work for me. I'm trying other servers.

Hi devs, today the topic is in third page but the bug is not fixed. We have many crashdumps if you need it Happy new year !

I checked my files and the "corrupted" file is officialserverstatus.ini . It could be rather a modified file from the patch ( updated status ) than a corrupted file. I can not launch the game anymore with the "low graphics" trick. How do you launch it ?

I would like to re-create my character but I can't because of the bug. I just cannot play.

The new patch doesn't fix the bug for me T_T

Timeout Connection is not the same issue. If you spam you could log on . If you can change home region it should be ok. The trick with low graphics does not work anymore for me. I don't think we've got any news before 2019 now.

I succeeded to play with the low graphics and spam respawn trick but the bug came back next time I died

The client crashed and produced a crashdump. This is a client bug. The client should handle gracefully unexpected server answers , showing a error popup but not killing itself in a crash. Btw handling errors gracefully will not help me to play and server should not sent unexpected answers

I fought a wolf and the wolf won. I didn't have my map open. Now since i'm dead, when I try to log the map should open to let me choose my respawn bed. I don't know if it's what you want. I answered to try to aggro the devs

It's not an error code but a line number in source code , with the current update it's line 1590. The bug is client side : we should have an Atlas error popup, not a system crash popup. But there's may be an server side problem too.