05-08-2015, 05:07 PM
(This post was last modified: 12-28-2015, 12:04 AM by LogicParrot.)
It's probably the too high CALCULATIONS_PER_TICK parameter, it was 5 before, and TigerW set it to 60 to accommodate for the current not-so-great path recalculation. I hoped that the performance change would not be noticeable, but it seems it is.
I've lowered it back to the way it was before.
Also, once we have all the basic features in place, I'll work pretty hard on optimizations. I am considering implementing Jump Point Search, it would be a very noticeable performance boost.
I've lowered it back to the way it was before.
Also, once we have all the basic features in place, I'll work pretty hard on optimizations. I am considering implementing Jump Point Search, it would be a very noticeable performance boost.