Hi Bebop, thanks for another excellent suggestion. The system currently takes all the required vision parameters at the start and calculates all required values right then to cut down on redundant calculations at runtime. Hence the reason why you don’t notice any changes happening at runtime despite modifying vision angle/radius.
But I believe it should be possible to add in an extra function that could be called to reset the visualization whenever required. I’ll do some tests and if everything works out fine, I’ll roll out a new update next week with said changes.