|
Geometry
This section lets you configure geometry-related preferences
when loading a project.
Note:
Sync does not support Geometry settings because they
are stored in project (.smgProj) files.
| Command Name
|
Description
|
| Load
|
Loads the assembly-tree structure and geometry for
products (
.smgProj and
.smgXml files). When this option is
cleared, only the tree structure is loaded. To reduce memory usage, clear this
option for large models or when working with only a portion of a model.
|
| Visible actors only
|
Loads geometry for visible actors only.
|
| Show only first level assembly tree
|
(Available when
Load is cleared.) Loads the root and
first-level tree structure only (not sub-products or geometry).
Note:
When you double-click an assembly or a
part node in fully shattered structures (i.e. when you click the red icon that
identifies it), only one level is loaded. To load all levels, right-click and
click
or in the ribbon click
.
When this option is cleared, the entire assembly structure
is loaded.
|
| Use level of detail
|
Specifies the default actor mesh detail to load. For
example, a screw can have a lower level of detail (LOD) in a car context than
in an engine context. Select one of the following:
-
Based on bounding box - The LOD is
based on the size of the geometry as compared to the entire model.
-
Low
-
Medium
-
High
You can define multiple LODs from Sync during the
conversion process to Composer format. When opening an SMG file with LOD in the
different Composer products, each actor's geometry is chosen as a function of
the size of the actor compared to the full model size. Note that when resaving
the file, only the current LOD is saved. Moreover, the refinement specified in
Input settings is used for the higher LOD. Sub-levels are automatically
defined.
|
| Load on visibility
|
In loading-on-demand mode (
), loads actor geometry
when a product is not loaded and visibility is activated.
|
Launch
This section lets you configure launch preferences when
loading a project.
| Command Name
|
Description
|
| View mode
|
Starts Composer applications in view mode. When you open a
model, the first view (as listed in the Views pane) is displayed. To open
models in animation mode at the beginning of the animation (time=0), clear this
option.
|
| Outlines on demand
|
Calculates outlines when needed instead of when opening a
file. Outline calculation takes time. Outlines are needed for some rendering
modes and measurements.
|
Views
This section lets you configure view preferences when loading
a project.
| Command Name
|
Description
|
| View Name Template
|
Lets you define a template to use for view names when
creating views. You can use alphanumeric characters, as well as the following
optional variables, in any order:
- %filename%: inserts the name of
the file containing the model, without its extension.
- %viewnumber%: inserts the number
of the view based on the creation order in the current session. For example,
1 is used for the first-created
view,
2 for the second-created view, etc.
- %viewindex%: inserts the index of
the view based on the actual number of visible views in the document. For
example,
4 is used when creating the first
view if there are already three views visible in the document,
5 is used for the next one, etc.
- %viewindex+n%
(where
n is an integer): inserts the index of
the view based on the actual number of visible views in the document plus the
number you define. For example, if you
specify%viewindex+10%,
14 is used when creating the first
view if there are already three views visible in the document,
15 is used for the next one, etc.
- %viewindex-n%
(where
n is an integer): inserts the index of
the view based on the actual number of visible views in the document minus the
number you define. For example, if you
specify%viewindex-2%,
2 is used when creating the first
view if there are already three views visible in the document,
3 is used for the next one, etc.
Note:
For
%viewindex+n%
and
%viewindex-n%,
make sure you don't add spaces between characters.
Note:
In the examples provided in the table below, we
consider that the file containing the model is called
Hammer.smg.
| Use this template...
|
To create views as...
|
| %filename%_View_%viewnumber%
|
Hammer_View_1,
Hammer_View_2,
Hammer_View_3, etc.
|
| %filename%
%viewindex%
|
Hammer 1,
Hammer 2,
Hammer 3, etc.
|
| View
%viewindex+10%
|
View Hammer
11,
View Hammer 12,
View Hammer 13, etc.
|
| %viewnumber%-%filename%
|
1-Hammer,
2-Hammer,
3-Hammer, etc.
|
| Demo of %filename%,
View %viewnumber%
|
Demo of Hammer, View
1,
Demo of Hammer, View 2,
Demo of Hammer, View 3, etc.
|
| View
%viewnumber%
Note:
This is the default template.
|
View 1,
View 2,
View 3, etc.
|
| View
%viewGuid%
|
View
812b33921beb7aa,
View 88fdbf810d791318, etc.
|
Note:
If you leave the field empty, views will be automatically
named according to the default template.
|
|