This is an issue I get regularly when the zone is set to start at y = 0. Setting the zone to start at y = 10 does seem to fix this most of the time, however I thought id report the issue as finding the root cause of this issue might fix other false detection issues
This is an issue I get regularly when the zone is set to start at y = 0. Setting the zone to start at y = 10 does seem to fix this most of the time, however I thought id report the issue as finding the root cause of this issue might fix other false detection issues