Distance Map computation is still a performance issue.

[DivineThreepwood]

Once a level object position has changed, the level view updates the distance map.
This computation is still heavy and could be optimized.

[DivineThreepwood]

Issue is identified, its caused by a high frequent marker placement of multiple agents, for each placement the distance map has to be recomputed which is a quite heavy computation:

Possible thoughts to solve the issue:

• introduce cache by using the position as key, this would avoid recomputing it again and again.
• avoid high frequent replacement my any game balancing
• improve neighbor identification process.
  • 

Note:

• check if we have similar moving level objects with the same issue.