I used The ravage mod to create a survival based insurgency sand box where players must go and find gear, money, allies, and food to complete tasks covering the entire map of Tanoa where they will find enemies from multiple factions who spawn dynamically around the player. One of my most detailed missions I've made in arma 3 consist of very intense scrips/configs/mods. GTX 780 (Later upgraded to GTX 980ti SC in 2016)įor 2013 this was a very powerful set up, it still is today in terms of just gaming, but not for workstation applications. In 2013 I went from that toshiba laptop to these specs: I do other things Like 3d rendering and map building. When I build Computers I design around mostly the CPU. I loaded the old files and AI behavior returned. I proved this later when I built my first work station and replayed these same exact missions on arma 2. AI functions failing to do their jobs is a cpu related hang up.

Blufor and opfor wouldn't attack each other, even if they were placed feet apart with no scripts effecting behavior. My frames would be seconds per frame, and AI functions would cease to act. If I placed too many waypoints over vast distances and places large scripts in every unit to force them to have a particular loadout the game fell apart. When I first started making missions I used a Toshiba Satellite laptop. In the older titles mission framework can absolutely stop in its tracks if your cpu is low end. I have over 4k hours across every ArmA title. I have been making missions/scrips/mods in ArmA since 2011. If you are a mission maker, or in a unit that does large scale scenarios like warlords or Zeus then yes this game will absolutely tank your cpu. If you mostly play small scale multiplayer scenarios IE official server games like KoH or official single player campaigns, then yes OP is correct the cpu usage is less than GPU. I'm here to squash everyones point here including the OPs.

Arma 3 ravage missions