Open ThatBrianDude opened 5 days ago
After further inspection it seems that the unnecessary point is not equal to but VERY close to one of the input path points.
To make this more clear here is a gif of me moving the input point a bit and the buggy point appearing/dissapearing:
Further observation: Switching to Clipper1 completely removes this issue. Il stay at Clipper1 for now until theres a fix for Clipper2.
Thanks for all the effort!
There is a case where this library adds an unnecessary point when executing a clipperOffset.
In the image you can see a point being generated right in the center of the road. This only happens in a specific positioning of the path.
When I move that waypoint just slightly up it dissapears:
This is the code that Im executing: