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
Discussions Rules and Guidelines
2 
Report this post
There are two issues, which we have seen with the game client that may cause the behaviour you're describing. In my view, you've done all the correct steps to try and debug the problem from your end.
Issue 1:
In most cases, we have found that the game client's configuration file(s) become 0-byte long due to a save file routine failing. If these configuration files are missing (don't exist, e.g. with first install), they are re-created; but with version v1.100 starting the client up fails, if such a 0-byte configuration file exists under %username%\batclient (location of the configs on Windows platform). This file needs to be removed manually, also if playing on the current version (v1.101). (Read: We failed to fix this in the latest release.)
As we are utilizing Steam Cloud, the same file must also be purged from the Cloud storage as well, because otherwise it gets downloaded from the Cloud back to your computer at the point of game client start-up (..and also deployed on your other machines, would you have such.)
Issue 2:
In a more rare case, we have found that running the game client fails (and is not related to issue 1). We've tried to pinpoint the issue, but have failed to find the cause. Unfortunately any debuggers used haven't (so far) yielded any further insight on why some Windows Platform installations have failed. One player allowed us remote access to her machine over video conferencing tooling to debug this issue for several hours, but we couldn't pinpoint what was the reason behind.
Based on your description, yours might be the 4th one of such cases reported, if the same. One of the four players was able to run the game client on a different Windows user (but this didn't help the person we had the debugging sessions with). A third player actually wanted to re-install Windows and got it working after that; but I don't suggest anyone to go to such extremes.
Please accept my apologies for the game not working out for you. We'll continue fixing any issues we find; hopefully on a shorter return-time in the future!
We're not exactly "a game company" (as we're not in it for the profit); and yes. we might not report back immediately, but we do respond! :-) That being said, you're 100% correct with that comment.
I'm sorry that you had to spend your personal time debugging the crash on loading up there earlier, without being able to resolve it and get enough support from us for the issue during that time.
All the best to you in your endeavors and have a great rest of the summer!
If you're facing issue #2, we'd appreciate further information from your environment. We don't currently have a "feedback loop" from the game client that would provide information on such crash -situations, but have been planning to add a "sentry", which would catch these issues for debugging.
I'll see if we can get this implemented for v1.102. Any information you could provide meanwhile would be helpful to assist locating the issue.