Lvl 13 Freezing crash while attacking east laying smith

Martinowitsch

fa 7 anys
Views 6.234
actualitzat fa 7 anys
Not Fixable

As i played Map 13 now 3 times and every time i attacked the smith in the east my game freeze and no input is any more possible, have to stop the game over the task manager

in steam Noontide ask me for some crash logs, but there is nothing :(

[quote=Steam]

[quote=Noontide;1470841715933374375][quote=Martinowitsch;1470841715933369085]in Lvl 13 every time i attack the east laying smith my game crashes, sometimes when i beginn the attack, some other times when im allready finished and try to bring my troops home [/quote]

We had one other report of this on our forums earlier this week. When we tested ourselves we couldn't replicate but more confusing is that neither could the person affected and thus we couldn't get a solid report on it.

If you can get a solid, consistent report and an output log from the game when this occurs then we'd love to look into it check out [url=http://brightrockgames.userecho.com/topics/118-how-to-submit-a-bug-ticket/]our bugtracker[/url] to log a full report with us. [/quote]

[quote=Noontide;1470841715933456797][quote=Martinowitsch;1470841715933408974]Thats strange i have looked in this folder \Program Files (x86)\Steam\SteamApps\common\War For The Overworld\ but there is no crash log

its an freezing crash, where the game stops working and i only can stop the game over the task master

what i found is an output log, but no timestamp files [/quote]

Chuck us through a report regardless and our QA Analyst will be able to help you. Just let him know what's happening and that you had a quick chat with me here :) [/quote]

[/quote]

Game Version:

Steam Public

Platform:

Windows

How would you rate the customer service you received?

Satisfaction mark by Martinowitsch fa 7 anys

Add a comment about quality of support you received (optional):

Replies 7

nous primer
nous primer vells primer

fa 7 anys

Yes that could be the problem, i know i will need some time in the future an real graphic card, my computer is relative new and an standard modell. With a little time and money i will rebuild this system.

But coriusly this was the only problem i did have with the game. All other Lvls worked fine.

Last night with the new patch i tryed a new game and saved it before i attacked the smith .. this time i could finish lvl 13

Respondre Enllaç

anonymous

fa 7 anys
Not Fixable

Hey Martin,

I hate to be the bearer of bad news but I've just had a closer look at your GPU and it looks like it falls far below minimum spec. As you can see here https://www.videocardbenchmark.net/gpu.php?gpu=Radeon+HD+8570D&id=2553 your GPU scores on average 678 points on the PassMark benchmark.

Unfortunately War For the Overworld requires a minimum score of 1500 on the PassMark benchmark to run the game, as stated in our System Requirements. There's nothing we can really do to fix it other than recommending that you attempt to run in the absolute lowest video settings. I hope that you can find some way to enjoy the game, or an alternative machine to play on.

What is likely happening is that you're entering a very busy part of the level and the crashing due to a lack of available system resources, unfortunately that's not something we can fix.

there is only an debug.log.meta in I:\Steam\steamapps\common\War For The Overworld\WFTOGame_Data\CoherentUI_Host\windows

no other files with "log" inside WFTO folder

fa 7 anys
Pending Customer

Is there an error.log next to the output_log.txt? If there is please upload it

yes this was the last time the crash occurred, thats why i didn't played any more

output_log 29_07_17.txt

Lee "Noontide" Moon Designer & Community Manager

fa 7 anys
Under Review

Quote from Martinowitsch

if you want i could give you the output log from 29.07.2017

thats the last time i tryed to play

Provided that log is from an instance where the issue occurred it would be very useful. An output log should be created whenever the game is opened so if when you last played the issue occurred then that output log should have the issue within it.