Perhaps you can have a look at the profiler during a game and look at the timings. The profiler can be brought up with F11 (and framerate with alt+F ). It shows how many milliseconds were spent on each separate step, info that help determine where your computer has a bottleneck. I have attached an example of the profiler, at the start of the Mauryan Punjab demo with 1 Aegis AI bot: The sim parts (simulation, pathfinding, AI and such) and the render parts (drawing the models to screen) are the most important (the rest should be fairly quick, plus there isn't that much that can be done about those). In my example you can see that the sim steps take up about 26 ms per frame, whereas rendering takes 81 milliseconds. No surprise the framerate is just 7fps. If you would open the Settings dialog from the top right corner menu, you can turn on and off different things and see it reflected in the render time. For example, turning off particles and shadows each reduces the render time by about 10 ms/frame for me. None of it is going to help me much, because my computer won't ever come close to a bearable framerate (anything 20+ fps) on a dense map like Punjab. Even on the lowest settings quite empty maps like Oases give me only 25 fps. But such stark differences show that for my computer the graphics are the main bottleneck. In my case I could switch from OS X to Windows on the same machine to improve the performance by quite a bit (30 fps should be possible with low AI action going on). So, profiling can help you determine what causes a low framerate. In my case I could switch to a lower resolution (1920x1080 is clearly too much) to improve performance. On the other hand, even if rendering took no time at all, the framerate would still be just 40 fps.