try_for_agents with position_no and radius_fixed_point works same as try_for_agents with get_distance_between_positions.Thanks. According to the operation description, try_for_agents have extra parameters to limit the search range: (try_for_agents, <destination>, [<position_no>], [<radius_fixed_point>]),
My question is: if I do want to limit the search range, is adding these two extra parameters better in performance than using the operation without the extra parameters, and then using get_distance_between_positions to check whether the agent is in range?
I have this question because by my understanding, try_for_agents works by going through a pre-saved array (or dictionary?) that contains the index of each agent, so I guess maybe those extra parameters (position_no and radius_fixed_point) work as an extra condition-check?
Performance is slightly better only due to fewer operations and less overhead on them.
try_for_agents with use_mission_grid gives much better performance since it goes through the mission grid rather than all the agents in the game, but you need to additionally use get_distance_between_positions if it is important for you to take into account the height in the agent position.