Read ACIS SAT / SAB for glTF / GLB conversion
A ACIS SAT / SAB-to-glTF / GLB workflow combines the ACIS SAT / SAB reader with the glTF / GLB writer. Use it when the receiving application needs glTF / GLB data from an existing ACIS SAT / SAB model.
Read SAT or SAB with the commercial ACIS interface and translate supported bodies into OCCT BRep. Select the supported source version and retain the relationship between imported shapes, names and colors needed by the application.
Prepare a scene for glTF or GLB delivery
Use the translated BRep for precise geometry output. For mesh-based delivery, tessellate the surfaces with an appropriate chordal deflection and inspect small faces and narrow features before writing the result.
Map supported model items into glTF scene nodes and configure the mesh, placements and appearance for browser or application delivery. Decide whether the receiving workflow expects a GLB package or glTF with companion resources. Keep names useful for selection and inspection.
Validate the glTF / GLB result
Include representative curved surfaces and multi-body files in the evaluation. Keep source-version compatibility and the target writer settings with the conversion record so that repeated jobs use the same configuration.
Reopen the asset in the target viewer and compare orientation, bounds, assembly placement and visible surface quality. Check material mapping and resource paths. Measure loading cost together with geometric detail so that reducing mesh size does not silently remove required features.
For a production pipeline, keep a representative source file and its expected geometry and attributes with the conversion settings. Discuss conversion integration with the source and destination applications, or compare the supported format interfaces.