In the morning when buses start to arrive and path-finding will stall into the 200’ queue limit in no time, later when they go through security it hits again.
Can you please automatically dial time down even more when the queue hits above 100’ queued up numbers and normalize it when it goes under.
Maybe don’t use hard numbers to enable / disable it but the weighted average of 15 in game minutes?
And as suggested somewhere else, can we get a tool, to “support” the path finder, with “routes” like the airwaynodes, as a suggestion from A to B, then pathfinder can take the suggested path when available between place A and B.
The queue limit is there to prevent path requests from growing beyond what the path finding can handle. Basically it reduces the FPS if the count goes over 200 to allow the path finding thread to catch up. This is a temporary solution as we are working on a new much faster method. It is unclear when this will be deployed as we still have some work to do, it is quite complex but initial tests looks very promising. Caching will be much more utilized and we expect something like 90% of paths can be cached, meaning very few actual path calculations.
the world of algorithms is a wonderful field.