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
Sorry to hear there are issues with the game.
Can you send me the generated crash files to Eran@forttriumph.com ?
There's one additional file that is important for figuring out what's preventing the game from starting.
Based on the platform you are using, it should be located in one of the following:
If you can send these I can check what the problem is and may be able to solve it.
All files have been sent as requested. As a note I'm not too bad with computers and have a High end desktop as well as a higer end gaming laptop that does not have the game installed on it currently. I would be willing to help you do some testing to work through this issue.
Registry keys under Computer\HKEY_CURRENT_USER\Software\Cookie Byte Entertainment You delete the enite thing, and reinstall the game, and it fixes the issue.
Note: I have tried verifying integrity of cache and deleting the registry method as offered above and both did not work.
Sorry about this.
Are you able to send a bug report from within the game?
To open the bug report panel, press Ctrl+Alt+F8. If that doesn't work, it may still be possible to reach it via the debug panel. To do so, triple left-click on the top-left corner of the screen and see if it opens the debug panel, from which the bug report panel is accessible.
This can help a lot in figuring out what's wrong as it's likely to contain errors. Specifically we had two reports recently of a similar issue (in which the solution specified above does not work), and it can show whether the cases are related.
If it's not possible to send a bug report, can you see if there's any log data here:
C:\Users\<username>\AppData\LocalLow\Cookie Byte Entertainment\Fort Triumph\Player.log
If there is, can you send it to Eran@forttriumph.com?
Notice that there's no need to do this if you can send a bug report as it'll already contain this data.
Thanks
Ctlr+Alt+F8 didn't work for you either, right? This can be important, as while the first asset that fails loading is something that handles input, the bug report system doesn't actually use it (it uses Unity's basic input handling mechanism), so the fact that this part doesn't work while the bug report system itself in general does can be an important clue.
We're a bit swamped because of the coming release, but we hope to figure out the underlying source of the issue and fix it soon. I'll keep you posted as soon as we have more information.
So, maybe this could be the case here too. Thanks and keep up the good work.
I did notice that in the first cases the language specified was Turkish, and wondered whether it's a coincidence or not. But there was another one with the exact same issue in which the language was English, so I figured it probably is a coincidence. We also don't have Turkish localization (nor any font in the game that supports any unique character it may have), and even before localization assets fail loading, an asset that handles input fails loading.
From what we've seen, it may be related to the order of things being loaded surfacing a bug in the engine we're using. So we've changed things so the assets that cause issues will be loaded at later phase (hopefully circumventing the issue).
Still, we're not certain that the change we've done will fix this, and if the similarity between the cases is close enough it's worth looking into it. What game was it? Can you share more information?
So, one thing I'm noticing is the use of an abnormal character in my file paths, the ı character. I have a fix for instances of this character uploaded to the public beta branch, I would ask that you exit steam if it is open, then re login to steam and see if the latest public beta updates and works for you.
And it worked like a charm. :)
It seems that it's the same problem here. The path in the log is 'uı/rewired ınput manager' instead of 'ui/rewired input manager' (didn't notice the lack of dots over the i's). The asset that does succeed in loading doesn't have one in it which is why it worked.
The issue is that we convert paths to lower-case, and with Turkish Locale they become wrong, resulting in resources not being found ('I' becomes 'ı' instead of 'i').
This is now fixed (will be in the release version).
Thanks for the help.