Unexpected result offset with PathsD

[F-Fede]

Hi,

I used to have an offset operation in Clipper1 like in the first attached picture (the green lines are the input paths, whilst the small black one is the result);
I tried and use Clipper2 by adopting double points: I expected a result that could be similar to the one depicted in the aforementioned picture, but I get no result; am I doing something wrong? Is there an issue with the operation?

Also, by continuing testing, I got some spikes in offset operation like in the second attached pictures.

Any help/hint very appreciated, thanks in advance!

I attach a file with the polygons replicating the behavior, just in case.
IssuesCLipper2PointD.txt

[AngusJohnson]

PathsD result = Clipper.InflatePaths(subj, -78, JoinType.Miter, EndType.Polygon, 2, 0); // I get no result

And why are you throwing all that precision away?

Try ...
PathsD result = Clipper.InflatePaths(subj, -78, JoinType.Miter, EndType.Polygon);
Then at least you'll get the default precision (ie 2 dec. places).

And likewise with the two regions you've marked with red arrows.

[F-Fede]

Thank you!

[AngusJohnson]

you're welcome 😁.