When I pressed the QUIT button, WFTOGame.exe has stopped working.
كيف تقيم خدمة العملاء التي تلقيتها؟
علامة الرضا من policeofficer110 منذ 8 سنة
إضافة تعليق حول كيفية المساعدة التي تلقيتها (اختياري):
Seems the error which you guys had is now fixed.
Now your logs look clean and I do not know what could be still causing this.
I fear again a Unity issue on certain systems, as it does not happen to me.
Can you try something for me?
Can you start cmd.exe and type regedit to open the registry editor.
Go to the folder
HKEY_CURRENT_USER / SOFTWARE / Subterranean Games / War for the Overworld
and delete all keys in right window which start with
"ScreenManager"
"UnityGraphicsQuality"
and
"UnitySelectMonitor"
then restart and quit the game.
Does it still do that?
Seems to be an issue other Unity games have as well.
Hope this gets addressed soon.
the problem is caused by the translation files.
editing the file with a free programs(libreoffice / openoffice) are created automatically columns and this causes the bug when you click on QUIT or when you enter the game menu.
try moving the translation files, without the community translation file the problem does not occur.
use google docs for edit files
I would at least not see how.
The translation files are parsed on game load and only again if set in the options and in this process any additional columns or anything which is not part of the key-text-pairs gets ignored.
From then the files are untouched and their keys are just stored in a dictionary in memory.
So there is no reason that this could have any impact at least theoretically.
It might be a Unity thing and they released a new hotfix themselves which is supposed to resolve crashes.
https://unity3d.com/unity/qa/patch-releases/5.3.4p5
"Game Performance: Fixed a potential crash on player exit if Game Performance Service is enabled."
We have this service on and thus this fix note matches our problem here exactly.
We will update to this Unity version and will see if this stops the annoying crashes on quit.
Going to mark this as done for now - The next patch that comes out should resolve this problem. If not, let us know and we'll reopen it to investigate further.
I can confirm that I am having this issue too. Here is a recording of it, and my output log.
2016-12-18 18-24-51.mp4
output_log.7z