The entry point
Minimum
- CPU
- 2 cores
- RAM
- 8 GB
- Graphics memory
- 4 GB VRAM
A starting point for play. Large battles may slow down as the fighting grows.
Annihilation Engine X
Plan your next battle
A starting point for playing Total Annihilation in AEX on macOS, Windows and Linux. Your map, mod and the size of your battle all shape what your machine has to do.
Provisional guidance. Reference-machine and battle-size benchmarks are still pending. These figures are not validated frame-rate or unit-count guarantees.
The entry point
A starting point for play. Large battles may slow down as the fighting grows.
Room for more battle
More CPU headroom for demanding battles. How far that takes you still depends on the match.
A little under the hood
A busy battlefield asks different things of each part of your machine.
Units moving, fighting and responding to orders give the CPU work to do. As armies grow, CPU headroom becomes more important. Core count and per-core performance both matter; clock speed alone does not tell the whole story.
AEX can spread work across multiple CPU cores. Some work depends on other work finishing first, so twice the cores does not mean twice the speed. Strong individual cores still help, even in a multithreaded game.
Maps, mods and match data need memory. Larger content and other apps compete for that space, so spare RAM gives your system breathing room.
The GPU draws the scene, with graphics data held in graphics memory. Higher resolutions and more demanding mod graphics need more headroom. Recording your session adds work too.
You need your own Total Annihilation game data. Mods and game content are not included with AEX.