Read X3D for glTF / GLB output
A X3D-to-glTF / GLB workflow connects the X3D reader to the glTF / GLB writer. Select the model items and output representation needed by the receiving application.
Read the supported X3D mesh and scene data with the Assimp integration. Inspect the object structure, placements and material information needed by the receiving application.
Prepare a scene for glTF or GLB delivery
The Assimp integration provides mesh geometry, colors, materials and scene structure for its supported inputs. Pass that data to a separate OCCT or commercial writer. For STEP, STEP XML or DXF output, use the mesh-capable representation; this does not reconstruct BRep surfaces from polygons.
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.
Check the glTF / GLB result
Verify geometry coverage and supported appearance. Interactive behavior and scene logic are not established by mesh import and need a separate implementation if the destination requires them.
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.
Discuss this conversion with the producing and receiving applications, representative files and required geometry and attributes. Compare the reader/writer catalog when a different representation is needed.