CSG2 errors or not expected result

Bugs
, ,
1

Hello,

In a previous post, I mentioned an issue with CSG that was causing some errors :

With the release of CSG2, I wanted to update the PG to see how the new version performed :

After some test, I encounter following problems :

  • The final position of meshes from ExtrudeShape are not the same
  • “cap” option from ExtrudeShape was removed in solution from previous post but causing error in new PG if not specified and/or if “closesShape” is set to “false”
  • Meshes after intersect not look like as expected
2

@Deltakosh any immediate thoughts here?

3

I beleive these are required with CSG2 because it is more sensitive to non-closed shapes. CAP_ALL and, likely, closeShape both ensure that the extruded shape is a fully closed shape. See this example, too.

1 Like
4

This is a correct assumption. Also @fybo: you can stick with CSG1, we will not remove it from the engine.

5

Ok, I’ll keep using CSG1.
About CSG1 and the “Maximum called stack size” error is some situations, after few tests and debug, I had to change CSGPlane.EPSILON (1e-5 to 1e-2 in my project) in csg.ts because it was too ambiguous in splitPolygon().
This fix allowed me to keep using CSG1 but this constant isn’t actually customizable.

1 Like