mifth

This has worked out. We need to calculate an area of all triangles. And then make a decision if it should be ignored.  Now it works well even with...

Another one problem is found: XAtlas triangulates Quads/NGons and considers them as uniquee triangles. For example, 2 triangles of a quad can be in different charts.    This...

I think it can be fixed in the computeCharts() function. Looking at it.

It was pretty hard to understand what's going on there but I almos fixed quads and ngons determination by charts. Hopefully, to finish today/tomorrow.  

Finally, I made've final changes/fixes for Quads/NGons. My commit: https://github.com/jpcy/xatlas/pull/138/commits/22f4d644aeff61a99af10facd579d4736c5043d4 https://github.com/jpcy/xatlas/pull/138#issuecomment-2445383272 Pictures: Some pictures of a final result after a generation:     

Some pictures to explain a new computeBoundaryIntersection variable which I've added with the latest commit.