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
For that reason it is recommended to do a save in regular intervals as auto saves may not be far back enough.
i read sometimes somthing about a 4 gb patch or a fix for ss 6.4 ?
To get around that you may have to use auto resolve (if your chances are good) or to withdraw. Maybe do some custom battle with units that are common in those crashed battles to figure which unit might be culprit.
The old version of the mod is however not supported anymore so all it would achieve is knowing which unit not to use.
Gets trickier if there is no commonality between units in crashed battles....
I made a repack of Stainless Steel that includes the 'meloo' fix, unfortunately it's unlikely that it would be compatible with your save, see below. Requires removal of the old installation. Applying the 4GB patch (Large Address Awareness or LAA) helps with memory issues: https://ntcore.com/?page_id=371
https://steamcommunity.com/sharedfiles/filedetails/?id=861485547
but i have it like every 2. round or like every battle i play. no fun at all to play a mod wich such an unstable performance tbh
That is indeed no fun and way too often. Try LAA and if that doesn't help switch to my repack.
merry xmas btw :D
You can look for it on the internet. Here is a site with a safe download and full explanation:
https://www.techpowerup.com/forums/threads/large-address-aware.112556/