SMG
(.smg)
|
The default file type, also known as memo3D. A single file
that includes all property, geometry, view, and animation information.
|
Package (.exe)
|
An auto-executable file containing the following:
-
.smg file
- Composer Player executable
- Composer Player Help
Use packages to distribute models to users who might not
have Composer or Composer Player installed. Opening the package file (
.exe) runs Composer Player and loads the
Composer data.
|
Product (.smgXml)
|
A multi-file format consisting of all the
.smg components:
The
.smgGeom,
.smgView, and
.smgSce files must have the same name as
the
.smgXml file.
|
Project (.smgProj)
|
A multi-file format consisting of one or more Composer
product files and a project (.smgProj) file. The
.smgProj file is an XML file that
references the top-level
.smgXml,
.smgView, and
.smgSce files that comprise the project.
- The
.smgXml,
.smgView, and
.smgSce files can be any name and
reside in any folder.
- The
.smgXml and
.smgGeom files must be the same name
and reside in the same folder.
Projects organize your Composer files into folders and let
you share references. For example, two projects can share the same
.smgXml,
.smgGeom, and
.smgView files but have different
.smgSce files. Projects also let you
import multiple subassemblies even when you do not have the main assembly file.
|
Fully Shattered
|
A Composer product with multiple
.smgXml and
.smgGeom files.
Note:
All other Composer formats contain geometry
and structure information in one (.smg,
.exe) or two
(.smgXml,
.smgGeom) files and are called
monolithic file types In the fully-shattered format:
- The main assembly and each subassembly has a
.smgXml file that includes the
neutral properties, assembly hierarchy, and position of its parts. It also
includes references to all the parts.
- Each part has a
.smgXml and
.smgGeom file.
Fully-shattered assemblies have several advantages:
- The assembly loads all its parts by reference. An
assembly does not have geometry files. This keeps the file size of the main
assembly small and lets you reuse parts in multiple assemblies.
- You can load assembly parts as you need them instead of
loading the entire assembly when you open it. For details, see the
options in the Open dialog box and the
Load on Visibility command. To
load a part, right-click the part in the Assembly tree and click
.
- You can load parts with different levels of details. If
you create your fully shattered assembly with more than one level of detail,
you can choose the level of detail on the Open dialog box.
- You can perform incremental updates. Because parts are
loaded by reference, you can update only parts that have changed.
When using fully shattered assemblies:
- You cannot create fully-shattered files from Composer.
Use Sync.
- Create projects with
, not
Save As
. Because Composer measurement actors, animation keys, and
other authoring content is stored in the top-level project assembly, that
content is lost if you create the project using
Save As
and then retranslate the top-level CAD assembly in Sync.
- Fully shattered assemblies reference the last saved
configuration of its parts. If your assembly uses multiple configurations of a
part, then it displays the last saved configuration for all instances of the
part. Therefore, you will get improper results when converting (from Sync) in
fully shattered mode an assembly that contains multiple instances of the same
part with different configurations.
- You cannot change the neutral properties of a part in a
fully shattered assembly because the part is loaded by reference into the
assembly. To change the neutral properties of a part, open the part in its own
window.
- When you modify a subassembly such as adding/removing
an assembly group or merging/exploding actors, you break the fully shattered
structure. All the associated structure branches will be saved in the top
assembly file.
- Undoing an operation that breaks a fully shattered
structure does not restore the fully shattered structure.
|