Instalar Steam
iniciar sesión
|
idioma
简体中文 (chino simplificado)
繁體中文 (chino tradicional)
日本語 (japonés)
한국어 (coreano)
ไทย (tailandés)
Български (búlgaro)
Čeština (checo)
Dansk (danés)
Deutsch (alemán)
English (inglés)
Español de Hispanoamérica
Ελληνικά (griego)
Français (francés)
Italiano
Bahasa Indonesia (indonesio)
Magyar (húngaro)
Nederlands (holandés)
Norsk (noruego)
Polski (polaco)
Português (Portugués de Portugal)
Português-Brasil (portugués de Brasil)
Română (rumano)
Русский (ruso)
Suomi (finés)
Svenska (sueco)
Türkçe (turco)
Tiếng Việt (vietnamita)
Українська (ucraniano)
Comunicar un error de traducción
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.