Asenna Steam
kirjaudu sisään
|
kieli
简体中文 (yksinkertaistettu kiina)
繁體中文 (perinteinen kiina)
日本語 (japani)
한국어 (korea)
ไทย (thai)
български (bulgaria)
Čeština (tšekki)
Dansk (tanska)
Deutsch (saksa)
English (englanti)
Español – España (espanja – Espanja)
Español – Latinoamérica (espanja – Lat. Am.)
Ελληνικά (kreikka)
Français (ranska)
Italiano (italia)
Bahasa Indonesia (indonesia)
Magyar (unkari)
Nederlands (hollanti)
Norsk (norja)
Polski (puola)
Português (portugali – Portugali)
Português – Brasil (portugali – Brasilia)
Română (romania)
Русский (venäjä)
Svenska (ruotsi)
Türkçe (turkki)
Tiếng Việt (vietnam)
Українська (ukraina)
Ilmoita käännösongelmasta
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.