Suscríbete para descargar
Custom Battle Crash Fix

Simple fix to circumvent unit roster cap in Custom Battle.




What it does:

This is a simple fix that disables the AI calculation of armies in Custom Battle, so that you are able to have (theoretically endless) unit-mods enabled. This was tested with +90 units for multiple factions, all DLCs and a heavy modded game (AIO, AFP, unit packs etc.).

You should not encounter any Crash to Desktop anymore, if you click on Custom Battle.

It should not interfere with any other mod or the campaign itself, because it comes with a custom table-fragment.
Technically it sets the regarding values to zero.

One minor flaw is that you have to assemble an AI army in Custom Battle yourself (no one-click army anymore).

I use this file in my mods, if you have use for it in your own mod feel free to copy or grab it yourself.
That's why I uploaded it this way.

For players:
It does not matter if you have 230 mods, with that table fragment active, as long as one loads that has the entries disabled. So you can have this mod and the Germanic Tribes mod (that does the same) or any other mod active without any problem.

Note:
If you look for a CUSTOM BATTLE CRASH FIX for TOTAL WAR - ATTILA, then go to Swiss Halberdier's Workshop and grap it from there .


What it does not:

Crashes on Start Up
Please beware, that mods that come with ESF (map, campaign) files are still not compatible. If your game crashes on Start Up this has nothing to do with the Custom Battle Crash and this "patch" does not fix this.
This only fixes the CTD by click on Custom Battle.

Crashes on Loading Screens
If your Custom Battle crashes on the loading screen after you picked an army, this has nothing to do with the CB-crash, we try to fix here. If that happens to you, it means that you have a mod that
a) requires another mod you do not have
b) a mod conflict between two mods that try to do the same stuff
c) is foul (everybody is a human being - modders make mistakes, too)
You might have not seen it in campaign, because your game never tried to access the units on a battle-field (this is a very important difference) in a campaign battle, but it woud have crashed then there as well.

What you can do is to disable some mods (that come with animations, balancing etc.) and only load strictly unit mods in (a little change in the load order can help). Unit mods don't do much except adding units and are tested that the units work, so you would have a positive result at hand and later enable more complex mods (that are 100% tested as well of course, but we want to see a lot of units first at all & later have a cool Roman formation), so that you can see where the conflict comes from.
If mods that should not conflict still conflict, just unsuscribe, load in the game and then suscribe again.
If they do not work - they do not work together.

What can help as well is to delete the files in (your User folder in C:) %appdata/The Creative Assembly/Rome II battle_preferences.
This resets your Custom Battle preferences to zero.

But all of this - has nothing to do with the Custom Battle Crash Fix!
Those are all loading-screen crashes and some tips how you can try to prevent them.


Please be advised:

If you experience still any problems - I can not help you. I just load this up for players and other modders that want a fast fix. I tested this with Radious and my mod active ,other modders were so kind to do "hardness tests" with their mods (f.e. Toon (All In One) let it run as well with AFP, SirEggmond fired up his unit packs, up to +90 units, see the comments section for further details) and it worked. So if it does not work at your side, it must be something very specific and rare.
Nevertheless:

You use this on your own risk!

And, please, do me the favor - just in case you feel like it - do not rant at CA here, because it is possible that it is not their fault and that there is no other fix than disabling the one-click-army feature.

Big thanks to DogSoldier who pointed the Better AI-Recruitment mod out to me ( A great mod and it circumvents the problem, too, but by deleting mp entries) so that I could figure out the problem, I tried to solve for a very, very long time.

If it works for you, have fun and thank you for your time.

~ Ryan