Steamをインストール
ログイン
|
言語
简体中文(簡体字中国語)
繁體中文(繁体字中国語)
한국어 (韓国語)
ไทย (タイ語)
български (ブルガリア語)
Čeština(チェコ語)
Dansk (デンマーク語)
Deutsch (ドイツ語)
English (英語)
Español - España (スペイン語 - スペイン)
Español - Latinoamérica (スペイン語 - ラテンアメリカ)
Ελληνικά (ギリシャ語)
Français (フランス語)
Italiano (イタリア語)
Bahasa Indonesia(インドネシア語)
Magyar(ハンガリー語)
Nederlands (オランダ語)
Norsk (ノルウェー語)
Polski (ポーランド語)
Português(ポルトガル語-ポルトガル)
Português - Brasil (ポルトガル語 - ブラジル)
Română(ルーマニア語)
Русский (ロシア語)
Suomi (フィンランド語)
Svenska (スウェーデン語)
Türkçe (トルコ語)
Tiếng Việt (ベトナム語)
Українська (ウクライナ語)
翻訳の問題を報告
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.