Dynamic Lighting won't let me use Freehand

Why is it making me use the polygon tool when I just want to sketch it out? Why is this even there as an option if its going to not let me use it? Is there a way to get this to activate? Thank you.

Hi Eric K.,  Freehand has been blocked from being used on the Dynamic Lighting layer because it causes problems such as higher resource usage and artifacts. Freehand is a lot of points of calculation compared to the Polygon tool.  Freehand being blocked is intentional and not a bug.  As for why it shows it "as an option" is something only the Devs know, but my guess is because people were trying to bypass it. By leaving it shown and then showing a notice to use the Polygon tool instead people are less likely to try to bypass it. 

Following up on Gauss' comment, Freehand paths are really just composed of a ton of line segments so close together that they appear smooth from the zoom level of the vtt. Ray tracing calculations for line of sight have to be performed for each line segment on the map every time a token is moved, which takes processor time and causes the high resource usage Gauss mentioned.

Thanks. I remember in the earlier set-up (I am completely ignorant of techy terms) sometimes the freehand would appear, and sometimes it would not, and it seemed completely random so I thought that this might be one of those instances. Thank you for he responses.

Eric K. said: Thanks. I remember in the earlier set-up (I am completely ignorant of techy terms) sometimes the freehand would appear, and sometimes it would not, and it seemed completely random so I thought that this might be one of those instances. Thank you for he responses. Freehand was removed a number of times, only to find its way back. Every time it had to be removed again because it breaks things. 

David M. said: Following up on Gauss' comment, Freehand paths are really just composed of a ton of line segments so close together that they appear smooth from the zoom level of the vtt. Ray tracing calculations for line of sight have to be performed for each line segment on the map every time a token is moved, which takes processor time and causes the high resource usage Gauss mentioned. Due to the unpredictable placement of joins, you could also occasionally wind up with extremely sharp angles, which due to the mathematics of the process could project "phantom barriers". This can still happen with the pen tool, AFAIK, but it's not something a person would usually draw.