Convert 3DS to SAT

A CAD application may require SAT when a legacy visualization or modeling package has supplied geometry as 3DS. Converting it can provide selectable CAD faces and solids, but it cannot recover design information lost when the source was tessellated.

What the 3DS format is

3DS is Autodesk 3D Studio's legacy binary format for polygon meshes. It can contain vertices, triangular or polygonal faces, material assignments, texture coordinates, cameras, and lights. 3D Studio and 3ds Max created it, and visualization, game, and general-purpose 3D applications still import it.

Its geometry is primarily a tessellated surface. A 3DS file normally does not contain analytic planes, cylinders, parametric surfaces, CAD topology, modeling history, or native solid definitions. The format also has legacy limits on scene structure and object naming, so it is unsuitable as a mechanical-CAD master file.

What the SAT format is

SAT is the exchange format associated with Spatial's ACIS geometric modeling kernel. It stores boundary-representation geometry, including faces, edges, shells, surfaces, and closed solids. AutoCAD, Inventor, Solid Edge, SolidWorks, and other CAD systems can use SAT, although supported SAT versions and import behavior vary.

A valid SAT solid gives the receiving application selectable faces, measurable edges, sectionable geometry, and operations such as filleting or boolean editing. SAT does not preserve a 3DS mesh as a mesh object during this workflow: the mesh must become individual CAD faces or be rebuilt as smoother analytic or NURBS geometry.

How to convert 3DS to SAT

Rhino desktop workflow

Rhino 7 or Rhino 8 is a practical option because it imports 3DS and exports ACIS SAT. The following process creates a faceted BREP from the mesh:

1. Open the file with File → Open and select .3ds. Confirm the import scale and retain texture coordinates only if the original mesh is needed for visual reference.
2. Inspect the mesh with _Check and _MeshRepair. Find holes, duplicate vertices, flipped faces, and non-manifold regions; use _ShowEdges where applicable to locate naked edges.
3. For a closed, manageable mesh, run _MeshToNurb. Rhino creates one NURBS face for each mesh polygon. This is a faceted CAD representation, not a reconstruction of the original feature history or smooth surfaces.
4. Select the resulting faces and run _Join. If the joined polysurface is completely closed, create or verify a solid with _CreateSolid. Repair naked edges before exporting if Rhino cannot make a closed volume.
5. Select the valid surface or solid and choose File → Export Selected. Set the type to ACIS SAT (*.sat), choose a compatible SAT version when available, and confirm the export units and tolerance.
6. Open the SAT in the destination CAD system. Check the reported units, solid validity, face count, naked edges, gaps, and critical dimensions instead of relying only on the viewport.

An open mesh can export as an open SAT shell, but it cannot become a valid closed solid without adding or repairing the missing geometry. For a large or detailed mesh, rebuilding key features as planes, cylinders, extrusions, fillets, or NURBS surfaces usually produces a more usable SAT than applying _MeshToNurb to every polygon.

Direct conversion software and online services

CAD Exchanger Desktop can be used when its current format matrix lists both 3DS import and SAT export. Open the 3DS file, review the conversion preview, select SAT as the output, and validate the result in the target CAD application. Depending on the source, it may produce a faceted BREP, an open surface, or no valid solid.

CAD Exchanger Cloud is an option for nonconfidential files only when its current online support list explicitly shows 3DS input and SAT output. Browser-based converters generally expose fewer controls for healing, tolerances, units, and solid validation. Do not upload proprietary models unless the service and project security rules permit it.

AutoCAD or another CAD program may also perform the conversion if the installed release supports both 3DS import and SAT export. Check the application's current import and export commands first; format support differs by product and release, and simply renaming .3ds to .sat never converts the geometry.

Quality and compatibility limits

_MeshToNurb is not reverse engineering. A 10,000-face mesh can create approximately 10,000 NURBS faces, resulting in a large, slow, difficult-to-edit SAT file. It does not restore holes, fillets, extrusions, exact cylinders, dimensions, or design intent lost during tessellation.

3DS files often provide insufficiently reliable unit information. Confirm the source scale against a known dimension before export; a model that looks correct can still be off by a factor of 10, 25.4, or 1,000. SAT tolerances and ACIS versions also differ between applications, so re-save the file in the receiving CAD system or export an older compatible SAT version if import fails.

Materials, textures, cameras, and lights have little or no role in SAT's mechanical BREP representation. Preserve the original 3DS separately when appearance data or the polygon mesh is still required.