USER FORUM
(you are viewing a thread; or go back to list of threads)
interfering surfaces (by Mike O)
Folks,
I have a pretty straightforward question that I'm struggling with as a newbie. Attached is a rendering of the part I'm trying to implement for 3d printing. You can clearly see there are two pieces that are sketched and extruded in a different workplane than the outer part, and so they interfere. When exporting as Triangle Mesh I get an error and the areas become highlighted with red. I know it is possible to force NURBS to triangle mesh, but I've read elsewhere on this forum that it's better to avoid it, and then when imported to slicer all kinds of glitches appear. So... what's the proper way to accomplish such geometry ? Thanks!
I have a pretty straightforward question that I'm struggling with as a newbie. Attached is a rendering of the part I'm trying to implement for 3d printing. You can clearly see there are two pieces that are sketched and extruded in a different workplane than the outer part, and so they interfere. When exporting as Triangle Mesh I get an error and the areas become highlighted with red. I know it is possible to force NURBS to triangle mesh, but I've read elsewhere on this forum that it's better to avoid it, and then when imported to slicer all kinds of glitches appear. So... what's the proper way to accomplish such geometry ? Thanks!
(no subject) (by Andrew)
Can you post the .slvs, so that I can see how you built the model?
(no subject) (by Mike O)
Yeah, here it comes :)
(no subject) (by Andrew)
I made some changes to your drawing.
1) removed the force to nurbs in cable supports group.
2) Deleted you separate cut out for the cable entry.
3) Made the cable entry from a single drawing and extruded it as the last operation.
Curved surface are problematic at times in SolveSpace, especially when it should match adjacent surfaces. Cutting the wall and the cable supports with one extrusion is the best approach. I have assumed that both ends are in line, but if they are not, current both ends separately will also work.
Attached is my modified version of your drawing, hope this helps.
1) removed the force to nurbs in cable supports group.
2) Deleted you separate cut out for the cable entry.
3) Made the cable entry from a single drawing and extruded it as the last operation.
Curved surface are problematic at times in SolveSpace, especially when it should match adjacent surfaces. Cutting the wall and the cable supports with one extrusion is the best approach. I have assumed that both ends are in line, but if they are not, current both ends separately will also work.
Attached is my modified version of your drawing, hope this helps.
(no subject) (by Mike O)
Very cool, thank you so much! So it's the curved cuts that create most of the issues when going through multiple surfaces ? What if (hypothetically) a rectangular cut was used ?
(no subject) (by Andrew)
Trying to match two curved surfaces that touch, in my experience, is a source of problems in solvespace. In your example, I avoided it by using a single cut after the solids had been joined.
(no subject) (by Mike O)
Understood! I've made some more minor adjustments, and it's printing now :)
(no subject) (by Mike O)
Ran into another similar problem, but this time the geometry is much simpler and I really can't see any other way to accomplish the desired result...
(no subject) (by Andrew)
I can't help you get rid of the errors this time, I suggest you report it as a bug. However, slic3r repairs the exported mesh and so you can print the object.
(no subject) (by Andrew)
After a bit of playing, I sort of fixed the model export to stl by ending the bezier just above the top surface, and starting the 'legs' under the surface, as in the attached drawing.
Note for developers, the original model looks fine in solvespace, and no errors in analyze 'show naked edges'. When exporting as triangle mesh (stl) it errors of 'The mesh is self intersecting...' and .The mesh has naked edges..'. Program version is 3.0-83a0a517.
Note for developers, the original model looks fine in solvespace, and no errors in analyze 'show naked edges'. When exporting as triangle mesh (stl) it errors of 'The mesh is self intersecting...' and .The mesh has naked edges..'. Program version is 3.0-83a0a517.
(no subject) (by Mike O)
That's impressive! Thank you again! But yeah, seems like a software issue.
Post a reply to this comment: