Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
And the reason crash show up more often in the campaign map than the battle, because during battle it's required less game memory but the GPU memory.If you have the fine graphic dev won't be crash that easily.But while you loading into the campaign after the battle or click anything some random crash will happen because the some process code by CA has conflict to each other in game memory.Which cause the DTP, and that the reason the game get more unstable by update of CA.
Yeah the conclusion is the CA update not only ruined your old game save or mod by the community etc. Also get the game more unstable so that you can only play the battle and restart time and time again during the campaign.But the CA wouldn't pay more efficient in the update and published the causally update each time and put properties issue on the DLC to harvest more money.
Memory specs + pagefile settings.
(I can confirm TWWH3 is happy enough with these numbers)
Because Campaign mode does use more memory than Battle mode.
Every new interaction on the campaign map uses more memory as it loads data.
Then there is a gradual memory leak when switching between Campaign and Battle modes.
And Steam / Steam Overlay can crash repeatedly just before TWWH3 does.