Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Enter this path in File Explorer / run command and check out your logs:
With any luck it'll give you more detail.
I am now able to join servers sometimes. Other times it will not let me. I looked at the path you told me to look at and this is it's contents, 10 Ground branch Backups, 1 just called ground branch and 1 called Cef3. Not too sure what any of that means. Cef3 is a empty text files with not text inside.
Next time you have the issue, quit out and open up the latest GroundBranch.log with a text editor (Notepad etc) and have a read near the bottom of the file. It may give you an idea what is going on.
Is I cancel the "waiting for rules" popup, the loading screen doesn't seem to timeout. I have to kill the process (the kill command from the console works too).
It worked fine yesterday (my first games) and fails today for some reason. I revalidated the game, so it decided to re download something. But the end result was the same.
Looking at the logs, there's nothing really obvious.
There's a bunch of stuff marked as LogNet interspersed with a few other things. Maybe that block will be interesting to you :
BFS Servers in Germany, France and London lead into the connection error and I found one custom server that also fails (SAS Proving Ground 10)...
other servers work, like Un1t or Kommando Server...
it's not a client side issue...
And of course those were the exact three I tried... Duh.
Thanks for clearing that up.
I have fixed the logic that was causing the issue internally.
Working on some other fixes, but we'll push them all to the public build once when able.
With any luck that solve the issue.
Coming across the reports in the forums and such now.
Fun fun fun :(