I've made the game a high-priority process in Windows, but I didn't have it in that build. It seems to help the problem you mention. Also, if your cpu is older it will show in this test because I turned on scale2x and that puts a huge load on it - in windows I go from 20% to 90%+ load. (in Linux the max load is much smaller, I think. Hmm. Or maybe I didn't look at that after making the "big" map.)

Scale2x is going to be more like a bonus option for people with high specs, I think. The graphics overall aren't going to change much at this point, but I can optimize collision by doing location-based culling. That will make large/detailed maps a LOT more efficient.