Newbe: Union between STL and new objects?
Forum rules
and Helpful information
and Helpful information
IMPORTANT: Please click here and read this first, before asking for help
Also, be nice to others! Read the FreeCAD code of conduct!
Also, be nice to others! Read the FreeCAD code of conduct!
Newbe: Union between STL and new objects?
I am new at freecad: is it possible to modify imported STL-objects (eg. from thingiverse) with union/intersect/difference with solid made objects in freecad?
Re: Newbe: Union between STL and new objects?
Only if you convert the mesh to a solid.
You need to switch to the Part workbench, then in sequence and from the Part menu:
You need to switch to the Part workbench, then in sequence and from the Part menu:
- Create a shape from mesh
- Convert the shape to solid
- Optional: apply a refine shape to the solid (it will clean up the coplanar faces)
Re: Newbe: Union between STL and new objects?
Thanks I got it!
Re: Newbe: Union between STL and new objects?
If for whatever reason it does not want to work that way, you still have one more shot at it by converting your current solid into a mesh and doing a mesh Boolean in the Mesh Design Workbench. I've found on several occasions, going the reverse has worked.
Mark
Mark
This post made with 0.0% Micro$oft products - GOT LINUX?
Re: Newbe: Union between STL and new objects?
a tip in addition to the other responses...
I am deliberately over simplifying this to get my point across clearly.....A mesh is "dumbed down" object compared to a shape. So it is easy to go from a shape to a mesh (to be overly basic, you pretty much just forget half the information). However the opposite is almost impossible, because to go from Mesh to Solid you have to "remember" all that data you lost, which is impossible, so you get an approximation/guess which can not, in most cases, be correct.
You can do Boolean operations with two mesh objects as Mark said, however you now need OpenSCAD to be installed on your system for this to work.
I am deliberately over simplifying this to get my point across clearly.....A mesh is "dumbed down" object compared to a shape. So it is easy to go from a shape to a mesh (to be overly basic, you pretty much just forget half the information). However the opposite is almost impossible, because to go from Mesh to Solid you have to "remember" all that data you lost, which is impossible, so you get an approximation/guess which can not, in most cases, be correct.
You can do Boolean operations with two mesh objects as Mark said, however you now need OpenSCAD to be installed on your system for this to work.
Re: Newbe: Union between STL and new objects?
+1 for Jim
And there is one thing I'd like note to platforms like thingiverse. There is a chance that the original author has the file in a proper CAD format. If he used a CAD program, he should be able to export a STEP file. If he used OpenSCAD it would make sense to, at least try to, import it directly. If the part was modeled in Design Spark Mechanical (or as I call it the Space Claim demo version) you might get to extract the ACIS (SAT) data from the .rsdoc file. Only if the original part was designed in mesh modeler (Blender, Wings3d, 3dmax...) or meshed form a point cloud you are stuck with the STL.
Thingiverse allows you to contact the author.
The conversion only works (well) for meshes with a low triangle count.
And there is one thing I'd like note to platforms like thingiverse. There is a chance that the original author has the file in a proper CAD format. If he used a CAD program, he should be able to export a STEP file. If he used OpenSCAD it would make sense to, at least try to, import it directly. If the part was modeled in Design Spark Mechanical (or as I call it the Space Claim demo version) you might get to extract the ACIS (SAT) data from the .rsdoc file. Only if the original part was designed in mesh modeler (Blender, Wings3d, 3dmax...) or meshed form a point cloud you are stuck with the STL.
Thingiverse allows you to contact the author.
The conversion only works (well) for meshes with a low triangle count.