Does this still happen after you disable the mods?

Originally posted by Benjin:

Does this still happen after you disable the mods?

I deleted the game documents and the entire game, then re-downloaded it. I removed other mods and only kept the AAA series. In every test my friend and I conducted, after about 15 turns and more than 5 manual battles, the game would definitely crash. However, when my friend and I used the AAA series in Total War: Rome II back in 2020, there were no issues at all.

Originally posted by Rush Come:

Originally posted by Benjin:

Does this still happen after you disable the mods?

I deleted the game documents and the entire game, then re-downloaded it. I removed other mods and only kept the AAA series. In every test my friend and I conducted, after about 15 turns and more than 5 manual battles, the game would definitely crash. However, when my friend and I used the AAA series in Total War: Rome II back in 2020, there were no issues at all.

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.

I solved the virtual - memory error problem, which took me a long time. In the online campaign, during manual battles, do not use the fast - forward button to end the game, as it may cause an error in the third or fourth battle. During this period, I re - ordered the MOD list, updated the graphics card driver, adjusted the virtual memory settings, and ensured that there was more than 100GB of free space on my hard - drive, but the effect was poor. I found that it was the fast - forward button, which accelerated the game battles, that caused the error.
The name of this virtual - memory error is not trustworthy, because MOD conflicts can also trigger this message, so the message is false.