Just popping back to this one after a while. For now I'm going to close the ticket down as "Not a bug" but I will take the feedback on board and will pass it through in the new year.

That said as Stefan quite rightly pointed out at this point a lot of things things are not trivial to solve and it may be too far down the line for us to solve them in this game.

Hi I'm passing this back to Stefan but I can't promise we'll have a response before the new year. We're all currently on leave for XMas :)

Sorry we couldn't help, best of luck!

Hi Jastic,

Sorry to hear that, I've taken a quick look at the output log unfortunately it seems Unity failed to capture a full stacktrace.

RtlLookupFunctionEntry returned NULL function. Aborting stack walk.<Missing stacktrace information>

This might make it hard to diagnose the cause of the crash but I will pass it through to code anyway to see if they can spot something.

I can't promise a response until the new year though as we're all currently on XMas leave (But here I am anyway! ;) )

Cheers,

Lee

Hi RedPythoness,

Sorry to hear about the issues you've had while running the game, I've taken a quick look through your output log and can confirm that the cause of these crashes is as I suspected when I read your system specs.

Here's the cause:

DynamicHeapAllocator out of memory - Could not get memory for large allocation 8388608!

Could not allocate memory: System out of memory!

As you only have 4GB of RAM in your system and WFTO is a pretty intensive program it seems that in certain levels, after a length of time or under certain conditions your memory is being filled, leaving none for the engine to apportion for it's use and this causes the crash. Saving is one of the conditions where a lot of memory is used because it has to take a snapshot of the entire level.

On a technical level this is only made worse by the 32-Bit OS which can only address approx 3.5GB of system memory. Long story short you are at the very borderline of our minimum System Requirements.

We usually recommend at least 8GB of RAM to experience WFTO at a reasonable level hopefully without any chance of running into out of memory crashes. The minimum requirements simply dictate what it takes to get the game running.

But not all is lost, we have tested this in the past. A good year ago now and WFTO's memory footprint has only reduced since then! I can say it is possible to complete the entire game on a 4GB 32-bit system but you have to make sure as much system memory is free for the game as possible.

This means turning off all unnecessary programs, reducing Windows' own footprint by disabling various graphics settings, in general any steps you can take to free up memory. Especially make sure when you launch the game that you have any other programs closed, and there's nothing (perhaps even antivirus at a push) running in the bottom right quickbar (Use the arrow to show hidden icons)

If you can free up enough memory you should be able to complete the entire campaign but you may need to avoid saving on some levels. Levels 10, 12 and 13 in particular have quite high footprints due to the size and number of units in them.

Hope that helps,

Lee