USER FORUM
(you are viewing a thread; or go back to list of threads)
Assembly: mesh is self intersecting after 2.3 to 3.1 (by Bill)
Mint 20
Error message:
The mesh is self intersecting,
The mesh is watertight.
... problematic edges.
I created two files in V 2.3 and an assembly in 2.3.
Exported to stl, no problem.
I uninstalled 2.3 and installed 3.1.
Opening the previous assembly in 3.1 I have the above error message. (upon selecting 'show naked edges')
Export to stl saves OK.
However, opening the stl in MeshLab and selecting 'Filters>Quality Measures and computations>Compute Geometric Measures' says that the mesh is not watertight.
The imported/linked parts were at the end so I deleted them all.
There are no errors before the assembly.
The 'main' model is a flat, rectangular 'board' with several 2.5 mm holes in it.
The linked sub-model is a spacer, a 3 mm tall cylinder with a 5 mm diameter and a 3.2 mm hole in it.
After linking the part I constrain it's normal 'same orientation' to a hole's normal on the main board then select the top center point of a hole on the board and the bottom center point on the spacer and constrain them.
Selecting 'show naked edges' shows several red lines to other holes and to the nearby edge of the base-board.
The red lines start from the edge of the hole in the board. ( not from the hole in the spacer.)
I don't see what can possibly 'self intersecting'.
How do I go about this, what do i need to check to correct it?
Many thanks
Error message:
The mesh is self intersecting,
The mesh is watertight.
... problematic edges.
I created two files in V 2.3 and an assembly in 2.3.
Exported to stl, no problem.
I uninstalled 2.3 and installed 3.1.
Opening the previous assembly in 3.1 I have the above error message. (upon selecting 'show naked edges')
Export to stl saves OK.
However, opening the stl in MeshLab and selecting 'Filters>Quality Measures and computations>Compute Geometric Measures' says that the mesh is not watertight.
The imported/linked parts were at the end so I deleted them all.
There are no errors before the assembly.
The 'main' model is a flat, rectangular 'board' with several 2.5 mm holes in it.
The linked sub-model is a spacer, a 3 mm tall cylinder with a 5 mm diameter and a 3.2 mm hole in it.
After linking the part I constrain it's normal 'same orientation' to a hole's normal on the main board then select the top center point of a hole on the board and the bottom center point on the spacer and constrain them.
Selecting 'show naked edges' shows several red lines to other holes and to the nearby edge of the base-board.
The red lines start from the edge of the hole in the board. ( not from the hole in the spacer.)
I don't see what can possibly 'self intersecting'.
How do I go about this, what do i need to check to correct it?
Many thanks
Update (by Bill)
It has nothing to do with v2.3 to 3.1.
Just created 2 boxes: b1, b2.
Import/link one to the other, create the 3 constraints to line them up on one side and select 'show naked edges'.
Error is the same.
Just created 2 boxes: b1, b2.
Import/link one to the other, create the 3 constraints to line them up on one side and select 'show naked edges'.
Error is the same.
(no subject) (by Tom)
Assemblies will always generate that message by default, since it doesn't merge the coincident surfaces from different parts. If you change the "solid model as" from "assemble" to "union" then the problem should go away.
update (by Bill)
"... change the "solid model as" from "assemble" to "union" ... "
When I do that, the tops and bottoms of both objects disappear, the joining sides of bot disappear but the other sides of both objects remain and have an:
"The mesh has naked edges:
error message.
"Assemblies will always generate that message ..."
Thank you, didn't know that. The crucial question now is : does this affect the exported .stl?
When I do that, the tops and bottoms of both objects disappear, the joining sides of bot disappear but the other sides of both objects remain and have an:
"The mesh has naked edges:
error message.
"Assemblies will always generate that message ..."
Thank you, didn't know that. The crucial question now is : does this affect the exported .stl?
Post a reply to this comment: