Large army size and system crash after battle

[perfecto25]

hi everyone, Im loving RS2 thank you for this incredible mod.

2 questions,

1. how do i increase the army size that Ive seen on some screenshots (for example having 120 Taxeis hoplites instead of default 60 per unit)
2. im running this on Win7 x64, with 8gigs of RAM and NVIDIA graphics driver, after 4-5 turns, if I have 2 or more large battles initiated by the enemy AI during my End of Turn cycle, after the 1st or 2nd large battle, the entire game crashes. Its very frustrating because there were instances where Ive won very difficult victories and spent up to 30 min on the battle, only to have the game crash as soon as it exits battle mode to campaign map.

[romanius24]

1.You can change unit size in the launcher or game options all the way to 240 not just 120.
2.Make sure your game path length is as short as possible and you wont have and crashes.(for ex: D:/RS2 instead of d:/Program File.../.../../Rome Total War)
There is a thread with other potential fixes like avoiding quick/auto saves, disable anti virus or avoid memory leaks.

[neep]

Hi,
as Romanius24 points out, there is an excellent (actually several) thread that describes all the potential failure points.
Folks have already gone through the pain of discovering all of those issues, so you don't need to re-invent the wheel.
It's easy to work through and makes sure everything is set up just fine.

[_Tartaros_]

there is also a very important improvement that is not firmly allowed to use, but in effect totally avoid this ctd for me.
just google "enable more than 2gb rtw exe"

[Hetairos]

There is another very important thing to take into account when experiencing crashes.

1.) Lower your graphic settings (some of them are heavily using up resources, such as grass).

2.) Restart your game every one or two hours.

3.) Don't auto or quicksave.

This is all because Rome has some issues with memory leak. Hence, the longer you play, the higher the graphic settings and the bigger the battles the sooner the game will crash due overload. Lowering graphics, restarting the game every one or two hours and manually saving between big battles can help you out.

Hope you can soon solve the problem and enjoy RSII like it is meant to be.

Cheers
Alec

[Bradley]

In my experience:

1) I have an old old RTW anthology (=RTW+BI+ALEX) CD which I use since the game was published, so it is heavily scratched. When I started playing EB and RS II and other mods, I suffered by a lot of CTDs. After going through forums I bought completely new CD of RTW anthology, shiny, polished and perfect. I made an image of that CD and put that CD in my bookshelf and never used it again. Since I use this image created from perfect (not damaged) CD I suffer much (i mean really MUCH) less CTDs.

2) Than I tried to install game on SSD disc and it helped a lot and reduced CTDs even more (merely non existing). I suppose, that better data transmission rates helps. It was combined with aforementioned "short install path" tip.


3) I reinstall game after few weeks of playing (basically after one or two campaigns). When newly installed game suffers CTDs, I unistall it and reinstall both game and mod(s). I do it as long as the CTDs appear.


4) I installed RS II 2.6 and that helps a lot.

5) I play on huge army settings and graphic settings are set to medium (in my experience high details lead to crashes in battles, especially when "closing in" to units)

I think (no evidence here) that when I overclocked processor to around 4.0 Ghz it helped, but it maybe only a coincidence. I also tried different graphic cards, but to no (visible) effect.

Conclusion: I really think, that the main problem is "purity" of installation of the unmoded game. With the same hardware, software and graphic settings I have different results (considering number of CTDs) with different installs.

[romanius24]

Anything above medium settings is just draw distance anyway...useless.
You can double your frame rate if you dont use High settings and the game will look the same.

[tungri_centurio]

ill PM you a possible solution that helped me alot on my win8 system. but dont post it back on the forum please

[neep]

The solution is going to depend on many parts, there's no single magic bullet - there are several, well documented in the stickies, points to ensure you avoid CTDs.
Apply them all, since they do no harm.
I had intermittent problems at first becuse I applied the fixes one at a time. Once I had everything applied, no more issues

I'm running Win7 x64 (24G available but I never need more than12G); recent NVidia (3G available but never need more than 1G) graphics card.
Not to specifically knock ATI, but my previous card was a Radeon 5770. It worked just fine but since I changed over to NVidia, I noticed that my memory leak numbers dropped so low I stopped tracking it. I can run all weekend and never have to worry about this.
I have Huge unit size and have High (not Highest) video settings on everything.

[century x]

Neep brings up a good point.
When RTW was created it was made using Nvidia graphics cards and code. People for years have always said they find a more stable game running a nvidia card than an ATI.
It is just a fact of life

[ur-Lord Tedric]

The post-battle CTD, IMtestedHO is almost definitely Anti-Virus (and now Windows protecting itself as it's got cleverer) related given how RTW changes files in now malware-like ways. Sadly RTW was written in a nicer time.

Remove the internet connection; turn off all AV s/w; and try and tell Windows that RTW is okay as much as you can. That's the best that can be done. I have had the very occasional CTD on my standalone RSII machine, mostly due to actual and solvable glitches from the Map during testing. I have not had a post-battle CTD since I stopped running AV s/w. I also still use WinXP as it's more tolerable of RTW.

[_Tartaros_]

i´m running without any problems on windows 7,
but telling your antivirus that your games are ok make always sence. antivirus did a heavy impact for my running system

[perfecto25]

used tungri's suggestion, works like a charm. No crashes yet, the only thing is when memory goes over 2gb, the battles can be extremely slow with almost non moving frame rates, at that point I just Escape and exit the battle (losing the battle), but still better than having an entire game crash

[tungri_centurio]

Strange? it's suppost to fix that problem. did you have siege engines with that battle?

[perfecto25]

Strange? it's suppost to fix that problem. did you have siege engines with that battle?

not sure, but this has been pretty rare so far, only happened once in about 15-20 battles. This game is horribly addictive!