
Industrial 3D Studio saves editable scenes as .ingmc3d files: structured JSON that records placed assets, transforms, parameters, project metadata, and annotations. Scene coordinates use millimetres. The file describes a scene; it is not a combined 3D model.
Objects and annotations
Each annotation stores its 3D anchor in the local coordinates of a semantic node. Its 2D label position is separate, so moving the label on screen does not move the anchor on the object. Named Selection Sets refer to existing objects; they do not change the scene hierarchy or transforms.
The asset library is separate
Scene objects reference an asset by assetId and assetVersion. The scene file does not contain the GLB geometry. Anyone opening it needs the matching asset library and versions. For example, an ESPDuino-32 HW-707 R02 object refers to ingmc.device.espduino32-hw707, version 2. Those model files are not currently offered for redistribution while licensing is confirmed.
The current export is a single JSON scene file, not a ZIP package. To hand off a scene, provide the .ingmc3d file and the corresponding asset files separately, when you have permission to share them.
Ignition viewer compatibility
Studio can save scene data that the current native Ignition viewer does not yet display. Its compatibility report flags files over 512 KiB, scenes with more than 64 objects, objects with more than 64 annotations, unavailable asset versions, and unsupported annotation frames.
The viewer currently renders static proxies. It does not apply robot joint positions, tool selection, procedural parameters, or Selection Sets. Articulated anchors such as J5, ToolMount, and TCP, and detailed ESPDuino pin anchors, are reported as unsupported rather than repositioned silently.
An .ingmc3d file is scene-authoring data, not a connection to a PLC, robot controller, or Ignition Gateway. It does not validate physical fit, robot reach, collisions, or machine safety.
For the distinction between a visual scene and a connected system, see From a robot-cell visualization to a digital-twin scope.
