Nainstalovat Steam
přihlásit se
|
jazyk
简体中文 (Zjednodušená čínština)
繁體中文 (Tradiční čínština)
日本語 (Japonština)
한국어 (Korejština)
ไทย (Thajština)
български (Bulharština)
Dansk (Dánština)
Deutsch (Němčina)
English (Angličtina)
Español-España (Evropská španělština)
Español-Latinoamérica (Latin. španělština)
Ελληνικά (Řečtina)
Français (Francouzština)
Italiano (Italština)
Bahasa Indonesia (Indonéština)
Magyar (Maďarština)
Nederlands (Nizozemština)
Norsk (Norština)
Polski (Polština)
Português (Evropská portugalština)
Português-Brasil (Brazilská portugalština)
Română (Rumunština)
Русский (Ruština)
Suomi (Finština)
Svenska (Švédština)
Türkçe (Turečtina)
Tiếng Việt (Vietnamština)
Українська (Ukrajinština)
Nahlásit problém s překladem
Yeah but, have you tested the crashing without the mods enabled too and attempted a pure vanilla run to see if that error repeats? The error message displaying is well known to be a RAM-related issue and can happen on vanilla in the same scenario you've described, so even if you disabled my mods, I wonder if it would still occur? Would be nice to know you and your friend's PC's specs too.
I also don't see why my mods would cause a crash like that - they're purely visual and rely on hardcoded db changes. VariantMeshDefinitions are relatively lightweight as well, each file is like a couple of kb as they're simple text files. Also, the mods haven't changed by that much since 2020 as I've been busy for the past 3 years. The biggest change was probably adding the Nubian generals to AAA: Africans back in 2022 when I had a few weeks off from work. I don't know what specs you were using back in 2020, but maybe those have changed as well which have lead to different results.
The name of this virtual - memory error is not trustworthy, because MOD conflicts can also trigger this message, so the message is false.