runtime error

felsi

8 years ago
Views 6,573
updated 8 years ago
Not a Bug

In the Campaign Mode (War for the Overworld 3rd level) the game (Version 1.4.3) crashes on various occassions:

1) Everytime I try to save a game.

2) Bevore killing the last enemys in the 3rd level of the campaign ( level.jpg). I wanted to enter the Menue to save. (see runtime error) runtime error.jpg

3) Everytime I try to set the texture quality to low in the options.

Reports :

error.log

output_log.txt

Options selected in the game

options ingame.jpg

I turned my Antivirus and all other Programs off.

Steam did a revalidation of the game.

I consider buying a new Graphics Card. (https://www.msi.com/Graphics-card/N730-4GD3V2.html#hero-overview)

My Spec:

Computerinformationen:
Hersteller: INTEL_
Modell: DH55TC__
Formfaktor: Desktop
Keine Touch-Eingabe erkannt

Prozessor:
CPU-Hersteller: GenuineIntel
CPU-Marke: Intel(R) Core(TM) i3 CPU 540 @ 3.07GHz
CPU-Familie: 0x6
CPU-Modell: 0x25
CPU-Stepping: 0x5
CPU-Typ: 0x0
Geschwindigkeit: 3059 MHz
4 logische Prozessoren
2 technische Prozessoren
HyperThreading: Unterstützt
FCMOV: Unterstützt
SSE2: Unterstützt
SSE3: Unterstützt
SSSE3: Unterstützt
SSE4a: Nicht unterstützt
SSE41: Unterstützt
SSE42: Unterstützt
AES: Nicht unterstützt
AVX: Nicht unterstützt
CMPXCHG16B: Unterstützt
LAHF/SAHF: Unterstützt
PrefetchW: Unterstützt

Betriebssystem:
Windows 7 (32 Bit)
NTFS: Unterstützt
Crypto Provider Codes: Unterstützt 311 0x0 0x0 0x0

Grafikkarte:
Treiber: Intel(R) HD Graphics

DirectX-Treibername: igdumdx32.dll
Treiberversion: 8.15.10.2622
DirectX-Treiberversion: 8.15.10.2622
Treiberdatum: 10.Jan..2012
OpenGL-Version: 2.1
Desktopfarbtiefe: 32 Bit per Pixel
Monitor-Aktualisierungsrate: 59 Hz
DirectX-Karte: Intel(R) HD Graphics
Anbieterkennung: 0x8086
Gerätekennung: 0x42
Revision: 0x2
Anzahl der Monitore: 1
Anzahl der logischen Grafikkarten: 1
Kein SLI oder Crossfire entdeckt
Prim. Anzeigeauflösung: 1680 x 1050
Desktopauflösung: 1680 x 1050
Prim. Anzeigegröße: 59.3 cm x 37.0 cm (69.8 cm diag.)

Kein prim. Bustyp entdeckt
Primärer VRAM: 1402 MB
Keine unterst. MSAA-Modi entdeckt

Soundkarte:
Audiogerät: Lautsprecher (Realtek High Defi

Speicher:
RAM: 3253 MB

Game Version:

Steam Public

Platform:

Windows

Replies 3

Newest first
Newest first Oldest first

Lee "Noontide" Moon Designer & Community Manager

8 years ago
Not a Bug

Hi Felsi,

Great to hear, we hope that improves your experience with WFTO :)

Cheers,

Lee

Reply Link

8 years ago

Hey Lee, thx for the quick response. I will update to win 10 64 Bit. In additon I will buy the above mentioned graphics card and 4G additional ram. I hope to be able to play the game afterwards. Kind regards

8 years ago
Pending Customer

I've reviewed your output log and I believe that I can confidently identify a cause of your crashes. It appears that the engine is crashing because it is unable to address further memory for the game's use.

DynamicHeapAllocator allocation probe 1 failed - Could not get memory for large allocation 4194304.
DynamicHeapAllocator allocation probe 2 failed - Could not get memory for large allocation 4194304.
DynamicHeapAllocator allocation probe 3 failed - Could not get memory for large allocation 4194304.
DynamicHeapAllocator allocation probe 4 failed - Could not get memory for large allocation 4194304.
DynamicHeapAllocator out of memory - Could not get memory for large allocation 4194304!
Could not allocate memory: System out of memory!

This isn't to be unexpected as your system is below minimum System Requirements and the timing of these crashes appear consistent with circumstances where the game would need to address a greater amount of memory than usual.

WFTO is a very CPU and RAM intensive game given it's vast size, amount of sounds, AI processes and deformable terrain we address a lot of memory to store all sorts of things at runtime. Unfortunately this means that anyone below 4GB of Memory is almost certainly going to see a crash even if they shut down all other processes, in fact we recommend that players have at least 8GB of RAM installed in their system (as well as using a 64-bit OS so that this memory can be addressed).

Unfortunately what this means is that there is little we can do for your particular case, although we certainly wish we could help further. All I can advise is try to shut down literally anything else that is running, even consider closing the explorer.exe process so that Windows explorer isn't using as much memory and turn down your settings for Windows. You might be able to get enough memory to perform the tasks you're looking to do but unfortunately I can't guarantee that.

I'm going to set this ticket to pending customer for now so I'll pickup any response from you immediately but I will close it down after a day if I receive no further response.

Best of luck and sorry that I can't assist you further.