0
Declined

Game keeps crasing

JJunior2402 2 years ago • updated by Lee "Noontide" Moon (Community Manager) 2 years ago 4

2016-08-05_231432.rar


My game keeps crashes at random moments, when I play it just shuts down the game completely.

I have reinstalled the game, reset my computer, did a verification in steam but nothings works.


Core Information

    • OS: Windows
    • Version: 7
    • 32bit
      • Ram: 4096 MB
      • CPU: Intel Core i7-4770K
      • GPU: AMD Radeon HD 5700 Series 2530 MB
Game Version:
Steam Public
Platform:
Windows
Pending Customer

Hi J Junior, in order to take a look at your issue we're going to need your output log as well as the system specs you've already provided (thanks for those)


As it stands your system is barely meeting the minimum requirements for the game (if it's even hitting them at all, it's very borderline and my memory is a little foggy today) meaning you will have trouble on some of the bigger levels where more is going on. I'd guess that this is the cause of your crashes, with the game running out of usable free RAM/memory but without the output log we won't know for sure.


You can find your output log using this link http://brightrockgames.userecho.com/topics/118-how-to-submit-a-bug-ticket/ (There is a section for finding output logs)


So i'll set this to pending customer until we hear back from you with the log

Thanks


- Nutter

Output_log (from a map called: 2016-08-05_231432)


Output_log (from a map called WFTOGame_Data)


Hi Nutter, my output log is in the .rar file I attached but i will attache it again for you ;)


My system is hitting above the minimal requirements for the game except for my RAM. The minimal for that is 4096 MB but recommended is 8 GB. So that couldn't be the problem could it?


EDIT: sorry, i see now that a 64bit OS is also recommended...would it help if i upgraded my OS to 64bit?


- J.

Under Review

Sorry! I didn't think to look in the .rar folder, told you my brain was foggy today haha and thanks for uploading it again for me.


The RAM is the most important requirement as the game uses a ton of RAM, on a minimum 4gb RAM spec system the game will probably use absolutely everything available, and if that still isn't enough it will most likely crash.


Obviously it's the weekend right now, and I believe that they're having internet trouble at the offices at the moment anyway, but i'll get one of the coders to check out your log when they're back online and see if there is anything we do or suggest to try and help you out.

Declined

Hi Jjunior2402,


I can confirm after reviewing your output log that you are indeed running out of available system memory and this is causing War for the Overworld to crash as it attempts to reference a memory address that it cannot.


From the looks of things it appears you moved onto a level which contains quite a few Lava or Water tiles, in Patch 1.4.1 we added ambient sounds to these tiles and this added a bit of extra load onto system memory. Patch 1.4.2 which is due to release today optimises these ambient sounds to help reduce the footprint on memory so you may find the situation improved in the next patch.


However it is important to stress that we highly recommend at least 8GB of RAM while playing War for the Overworld, due to it's nature WFTO is a memory and CPU intensive game and will chew through RAM quicker than I'm going to do with my lunch in 8 minutes time!


At the same time a 64-Bit OS is practically mandatory as 32-Bit operating systems cannot address more than 3.5GB of Memory at any time, this presents a massive limitation to your system (although obviously with only 4GB of RAM you're less likely to notice it). Unless you have some very specific software requirements which cannot run on a 64-bit OS there's absolutely no reason to be using 32-bit now.


If it's not possible for you to upgrade in the near future I'd recommend the following:


  • Give the game a try after Patch 1.4.2 is released
  • Turn off all non-essential programs to free up memory for WFTO to use

Hope that helps, for now I will be declining this ticket as it is an issue caused by customer hardware limitations.


Cheers,


Lee