05-29-2015, 02:03 AM
(This post was last modified: 05-29-2015, 02:12 AM by LogicParrot.)
@xoft: The "field data" would become stale once the mob moves a bit. So, essentially, whenever the mob picks a single place to go to, it has to throw away the field and calculate a new one. That essentially takes us back to the current implementation.
800KB per mob? What? Who? How?
Perhaps the main interface problem is that the PathFinder is a "dumb machine" which knows nothing except spitting out the Path from A to B. This leaves the management stuff to Monster.cpp. One option would be creating a PathFinder wrapper which offloads the Pathfinding logic from Monster.cpp
(05-29-2015, 01:37 AM)worktycho Wrote: The problem is that you need ~800KB of information per mob.
800KB per mob? What? Who? How?
Perhaps the main interface problem is that the PathFinder is a "dumb machine" which knows nothing except spitting out the Path from A to B. This leaves the management stuff to Monster.cpp. One option would be creating a PathFinder wrapper which offloads the Pathfinding logic from Monster.cpp