Colleagues, there are still big problems with the 3D Surface and ignoring my complaints about it is not helping progress. Clearly the program does not correctly define body boundaries. Selecting the “Don’t go over the boundaries” option makes it impossible to process edges.
Who makes this module, 3-D Surface? Who can I email the file to for review of the problem?
That this is a “program-side” problem, I believe, follows from this situation
There are bodies 1, 2, 3 and 4, which are connected into one body T1 via a Boolean operation. Path is created normally on body T1, borders are defined normally.
Similarly with group 5-7 in body T2. Bodies T1 and T2 partially overlap and are combined into body T3 by another Boolean operation. That’s all. The program does not correctly determine the boundaries of the body and “flies away” over the horizon.
Perhaps I can formulate conclusions about the localization of the source of the problem.
Here is a volumetric model, its geometry is checked without any problems. When creating Path, if the “do not go beyond the boundaries” checkbox is selected, all codes are created normally, i.e. the program defines the boundaries correctly. But as soon as you allow going beyond the boundaries, the program starts making a mess in the zone of the beginning or the end of the code or the external sharp corner. Perhaps it is something not very deeply buried in the python code.
Specifically on this object - small changes in the first three sketches lead to the disappearance of this artifact (we achieve the disappearance of a visually visible small crease on the surface, but this is only a “reason”, not the cause - on other similar objects NO even potentially toxic creases, and the result goes over the horizon - see the red screen)
I assume that there should be implemented a limit of going beyond the boundaries - “no more than the tool diameter”, which would solve all the issues.