I am noticing some lag. I wouldn't suggest using 1000 iterations.
The Behavior
never uses 1000 iterations, it uses a few tens of iterations only, those that are strictly necessary to draw the visible path. Please, don't let yourself be confused by the "1000" number. It is only an anecdotical number. If you analyze the algorithm you will realize that the "
exit loop" block always stops the loop after using a few tens of iterations. I get 60 FPS constantly in Flash, HTML5, Desktop and Android. If you notice some lag, it is not due to my Behavior, I can assure you that it is highly efficient.
You can stop the arc when it collides with a tile using the arc raycast tool.
Yes, I know, but for a better understanding I have shown a simple example. It is simple and efficient in terms of performance. (Performance is always the most important factor for me.)