Hello, In a previous post, I mentioned an issue with CSG that was causing some errors : [image] SlicerCSG issue with multiple meshes and angle of extrusion Bugs Hello, I have an issue with CSG when I try to slice multiple extruded meshes build with an extrusion path gene…

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 cons…

@Deltakosh any immediate thoughts here?

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

CSG2 errors or not expected result

Bugs

HiGreg February 15, 2025, 5:10am 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.

Topic		Replies	Views
SlicerCSG issue with multiple meshes and angle of extrusion Bugs extrudeshape , csg	4	495	April 3, 2023
Strange CSG2 result when using ExtrudeShape as brushes Questions extrudeshape , csg2	2	71	February 21, 2025
CSG Substract 2 extruded polygons gives strange result Questions mesh , csg	6	674	September 19, 2022
Mesh issue with CSG and Extruded Shape Questions	3	451	January 26, 2022
Bug when cutting GLTF object with CSG2 Bugs csg , csg2	34	567	December 18, 2024

CSG2 errors or not expected result

Related topics