When the module is first enabled, it is loading the current map twice resulting in twice as many pathables loaded which hurts performance substantially. After the map is changed, this issue no longer occurs.
Likely due to a logic issue when we load for the current map + something triggering a map change just after that to the current map (perhaps the first firing from mumble service).
dlamkins
commented
3 years ago
When the module is first enabled, it is loading the current map twice resulting in twice as many pathables loaded which hurts performance substantially. After the map is changed, this issue no longer occurs.
Likely due to a logic issue when we load for the current map + something triggering a map change just after that to the current map (perhaps the first firing from mumble service).