<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE html
  SYSTEM "about:legacy-compat">
<html xmlns:mml = "http://www.w3.org/1998/Math/MathML" lang = "en"><head><meta charset = "UTF-8"/><meta name = "copyright" content = "(C) Copyright 2020"/><meta name = "DC.rights.owner" content = "(C) Copyright 2020"/><meta name = "DC.type" content = "reference"/><meta name = "abstract" content = "The Project page lets you configure the default preferences when loading a project."/><meta name = "description" content = "The Project page lets you configure the default preferences when loading a project."/><meta name = "DC.format" content = "HTML5"/><meta name = "DC.identifier" content = "cps-r-DocumentProperties-Project"/><meta name = "DC.language" content = "en"/><link rel = "stylesheet" type = "text/css" href = "../DSDocUI_XML34.css"/><title>Project</title>
<script type = "text/javascript" src = "../DSDocUI_Highlight34.js">
  	/* */
  	</script></head><body onLoad = "highlightSearchTerms();" id = "cps-r-DocumentProperties-Project">
<a name = "hj-top"> </a><table class = "table1" id = "table11"><tr><td><table class = "DocHeader"><tr><td class = "DocHeader1" colspan = "2"><h1>Project</h1></td></tr><tr><td class = "DocHeader4" colspan = "2"/></tr><tr><td class = "DocHeader3" colspan = "2"><table class = "DocThemeIntro" id = "table12"><tr><td class = "Intro1Only"><p class = "header"><p class = "abstract">
		<span class = "shortdesc">The Project page lets you configure the default preferences when loading a
			project. </span>

		<p><span class = "ph">You can set these properties both for the active document and as document defaults.</span></p>
	</p>
<p>This page discusses: </p><ul><li><a href = "#r-Geometry" id = "toc_rg" title = "This section lets you configure geometry-related preferences when loading a project.">Geometry </a></li><li><a href = "#r-Launch" id = "toc_rg" title = "This section lets you configure launch preferences when loading a project.">Launch</a></li><li><a href = "#r-Views" id = "toc_rg" title = "This section lets you configure view preferences when loading a project.">Views</a></li><li><a href = "#reference_ymy_q3g_zsb" id = "toc_rg" title = "">View Collections</a></li></ul>
</p></td></tr></table></td></tr></table>
	

	
	<div class = "body refbody"/>

	<article class = "topic reference nested1" aria-labelledby = "ariaid-title2" id = "r-Geometry">
		<h2 class = "title topictitle2">Geometry </h2>

		
		<div class = "body refbody"><p class = "abstract">
			<span class = "shortdesc">This section lets you configure geometry-related preferences when loading a
				project. </span>

			<div class = "note collapse"><span class = "run-in.note">Note:
    		</span><span class = "notecontent">Sync does not support Geometry settings because they are stored in
				project (<span class = "ph filepath filepath">.smgProj</span>) files. </span></div>

		</p>

			<table class = "table frame-none"><caption/><colgroup><col/><col/></colgroup><thead class = "thead">
						<tr class = "row">
							<th class = "entry" id = "r-Geometry__entry__1">Command Name </th>
							<th class = "entry" id = "r-Geometry__entry__2">Description </th>
						</tr>
					</thead><tbody class = "tbody">
						<tr class = "row">
							<td class = "entry" headers = "r-Geometry__entry__1"><span class = "ph uicontrol">Load</span>
							</td>
							<td class = "entry" headers = "r-Geometry__entry__2">Loads the assembly-tree structure and geometry for products (
									<span class = "ph filepath filepath">.smgProj</span> and <span class = "ph filepath filepath">.smgXml</span>
								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. </td>
						</tr>
						<tr class = "row">
							<td class = "entry" headers = "r-Geometry__entry__1"><span class = "ph uicontrol">Visible actors only</span>
							</td>
							<td class = "entry" headers = "r-Geometry__entry__2">Loads geometry for visible actors only. </td>
						</tr>
						<tr class = "row">
							<td class = "entry" headers = "r-Geometry__entry__1"><span class = "ph uicontrol">Show only first level assembly tree</span>
							</td>
							<td class = "entry" headers = "r-Geometry__entry__2">(Available when <span class = "ph uicontrol">Load</span> is cleared.) Loads
								the root and first-level tree structure only (not sub-products or
								geometry). <p>
									<div class = "note collapse"><span class = "run-in.note">Note:
    		</span><span class = "notecontent"> 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 <span class = "ph menucascade"><span class = "ph uicontrol">Product</span><abbr title = "and then"> &gt; </abbr><span class = "ph uicontrol">Load Products</span></span> or in the ribbon click <span class = "ph menucascade"><span class = "ph uicontrol">Home</span><abbr title = "and then"> &gt; </abbr><span class = "ph uicontrol">Visibility</span><abbr title = "and then"> &gt; </abbr><span class = "ph uicontrol">Visibility</span><abbr title = "and then"> &gt; </abbr><span class = "ph uicontrol">Load on Visibility</span></span>. </span></div>

								</p>When this option is cleared, the entire assembly structure is
								loaded. </td>
						</tr>
						<tr class = "row">
							<td class = "entry" headers = "r-Geometry__entry__1"><span class = "ph uicontrol">Use level of detail</span>
							</td>
							<td class = "entry" headers = "r-Geometry__entry__2">
								<p>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: <ul class = "ul">
										<li class = "li">
											<span class = "ph uicontrol">Based on bounding box</span> - The LOD
											is based on the size of the geometry as compared to the
											entire model. </li>
										<li class = "li">
											<span class = "ph uicontrol">Low</span>
										</li>
										<li class = "li">
											<span class = "ph uicontrol">Medium</span>
										</li>
										<li class = "li">
											<span class = "ph uicontrol">High</span>
										</li>
									</ul>
									<table class = "table frame-none"><caption/><colgroup><col/><col/><col/></colgroup><tbody class = "tbody">
												<tr class = "row">
												<td class = "entry">
												<br/><img class = "image" src = "../CpsUserImages/LOD3.png"/><br/>
												</td>
												<td class = "entry">
												<br/><img class = "image" src = "../CpsUserImages/LOD2.png"/><br/>
												</td>
												<td class = "entry">
												<br/><img class = "image" src = "../CpsUserImages/LOD1.png"/><br/>
												</td>
												</tr>
												<tr class = "row">
												<td class = "entry">Low </td>
												<td class = "entry">Medium </td>
												<td class = "entry">High </td>
												</tr>
											</tbody></table>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. <table class = "Remark" id = "table132"><tr><td class = "Remark"><span class = "run-in.warning">Warning:
				</span><span class = "notecontent"> If
										an SMG file was converted with several LODs, only the
										selected LOD is saved. To keep an SMG file with all LODs,
										change the file name (to keep the original SMG file). This
										does not apply to project ( <span class = "ph filepath filepath">.smgProj</span>)
										files. </span></td></tr></table>

								</p>
							</td>
						</tr>
						<tr class = "row">
							<td class = "entry" headers = "r-Geometry__entry__1"><span class = "ph uicontrol">Load on visibility</span>
							</td>
							<td class = "entry" headers = "r-Geometry__entry__2">In loading-on-demand mode ( <span class = "ph menucascade"><span class = "ph uicontrol">Home</span><abbr title = "and then"> &gt; </abbr><span class = "ph uicontrol">Visibility</span><abbr title = "and then"> &gt; </abbr><span class = "ph uicontrol">Visibility</span><abbr title = "and then"> &gt; </abbr><span class = "ph uicontrol">Load on Visibility <img class = "image" src = "../Icons3DVIA/I_CPSRenderLoadOnVisibility.png"/></span></span>), loads actor geometry when a product is not loaded
								and visibility is activated. </td>
						</tr>
					</tbody></table>
		</div>

	</article>
	<article class = "topic reference nested1" aria-labelledby = "ariaid-title3" id = "r-Launch">
		<p><map name = "FPMap1"><area href = "#hj-top" title = "Back to Top" shape = "rect" coords = "416, 0, 435, 10"/></map><span class = "itemsprite"/></p><h2 class = "title topictitle2">Launch</h2>

		
		<div class = "body refbody"><p class = "abstract">
			<span class = "shortdesc">This section lets you configure launch preferences when loading a project.
			</span>

		</p>

			<table class = "table frame-none"><caption/><colgroup><col/><col/></colgroup><thead class = "thead">
						<tr class = "row">
							<th class = "entry" id = "r-Launch__entry__1">Command Name </th>
							<th class = "entry" id = "r-Launch__entry__2">Description </th>
						</tr>
					</thead><tbody class = "tbody">
						<tr class = "row">
							<td class = "entry" headers = "r-Launch__entry__1"><span class = "ph uicontrol">View mode</span>
							</td>
							<td class = "entry" headers = "r-Launch__entry__2">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. </td>
						</tr>
						<tr class = "row">
							<td class = "entry" headers = "r-Launch__entry__1"><span class = "ph uicontrol">Outlines on demand</span>
							</td>
							<td class = "entry" headers = "r-Launch__entry__2">Calculates outlines when needed instead of when opening a file.
								Outline calculation takes time. Outlines are needed for some
								rendering modes and measurements. </td>
						</tr>
					</tbody></table>
		</div>

	</article>
	<article class = "topic reference nested1" aria-labelledby = "ariaid-title4" id = "r-Views">
		<p><map name = "FPMap1"><area href = "#hj-top" title = "Back to Top" shape = "rect" coords = "416, 0, 435, 10"/></map><span class = "itemsprite"/></p><h2 class = "title topictitle2">Views</h2>

		
		<div class = "body refbody"><p class = "abstract">
			<span class = "shortdesc">This section lets you configure view preferences when loading a project.
			</span>

		</p>

			<table class = "table frame-none"><caption/><colgroup><col/><col/></colgroup><thead class = "thead">
						<tr class = "row">
							<th class = "entry" id = "r-Views__entry__1">Command Name </th>
							<th class = "entry" id = "r-Views__entry__2">Description </th>
						</tr>
					</thead><tbody class = "tbody">
						<tr class = "row">
							<td class = "entry" headers = "r-Views__entry__1"><span class = "ph uicontrol">View Name Template</span>
							</td>
							<td class = "entry" headers = "r-Views__entry__2">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: <ul class = "ul">
									<li class = "li"><kbd class = "ph userinput userinput">%filename%</kbd>: inserts the name of the
										file containing the model, without its extension. </li>
									<li class = "li"><kbd class = "ph userinput userinput">%viewnumber%</kbd>: inserts the number of
										the view based on the creation order in the current session.
										For example, <span class = "ph uicontrol">1</span> is used for the
										first-created view, <span class = "ph uicontrol">2</span> for the
										second-created view, etc. </li>
									<li class = "li"><kbd class = "ph userinput userinput">%viewindex%</kbd>: inserts the index of the
										view based on the actual number of visible views in the
										document. For example, <span class = "ph uicontrol">4</span> is used when
										creating the first view if there are already three views
										visible in the document, <span class = "ph uicontrol">5</span> is used
										for the next one, etc. </li>
									<li class = "li"><kbd class = "ph userinput userinput">%viewindex+</kbd><var class = "keyword varname varname">n</var><kbd class = "ph userinput userinput">%</kbd>
										(where <var class = "keyword varname varname">n</var> 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<kbd class = "ph userinput userinput">%viewindex+10%</kbd>,
											<span class = "ph uicontrol">14</span> is used when creating the
										first view if there are already three views visible in the
										document, <span class = "ph uicontrol">15</span> is used for the next
										one, etc. </li>
									<li class = "li"><kbd class = "ph userinput userinput">%viewindex-</kbd><var class = "keyword varname varname">n</var><kbd class = "ph userinput userinput">%</kbd>
										(where <var class = "keyword varname varname">n</var> 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<kbd class = "ph userinput userinput">%viewindex-2%</kbd>,
											<span class = "ph uicontrol">2</span> is used when creating the first
										view if there are already three views visible in the
										document, <span class = "ph uicontrol">3</span> is used for the next one,
										etc. </li>
									
								</ul>
								<p>
									<div class = "note"><span class = "run-in.note">Note:
			</span><span class = "notecontent">For
											<kbd class = "ph userinput userinput">%viewindex+</kbd><var class = "keyword varname varname">n</var><kbd class = "ph userinput userinput">%</kbd>
										and
											<kbd class = "ph userinput userinput">%viewindex-</kbd><var class = "keyword varname varname">n</var><kbd class = "ph userinput userinput">%</kbd>,
										make sure you don't add spaces between characters. </span></div>

								</p>
								<p>
									<div class = "note"><span class = "run-in.note">Note:
			</span><span class = "notecontent">In the examples provided in the table below, we consider
										that the file containing the model is called
											<span class = "ph filepath filepath">Hammer.smg</span>. </span></div>

								</p>
								<p>
									<table class = "table"><caption/><colgroup><col style = "width:50%"/><col style = "width:50%"/></colgroup><thead class = "thead">
												<tr class = "row">
												<th class = "entry" id = "r-Views__entry__5">Use this template... </th>
												<th class = "entry" id = "r-Views__entry__6">To create views as...
												</th>
												</tr>
											</thead><tbody class = "tbody">
												<tr class = "row">
												<td class = "entry" headers = "r-Views__entry__5"><kbd class = "ph userinput userinput">%filename%_View_%viewnumber%</kbd>
												</td>
												<td class = "entry" headers = "r-Views__entry__6"><span class = "ph uicontrol">Hammer_View_1</span>,
												<span class = "ph uicontrol">Hammer_View_2</span>,
												<span class = "ph uicontrol">Hammer_View_3</span>, etc.
												</td>
												</tr>
												<tr class = "row">
												<td class = "entry" headers = "r-Views__entry__5"><kbd class = "ph userinput userinput">%filename%
												%viewindex%</kbd>
												</td>
												<td class = "entry" headers = "r-Views__entry__6"><span class = "ph uicontrol">Hammer
												1</span>, <span class = "ph uicontrol">Hammer 2</span>,
												<span class = "ph uicontrol">Hammer 3</span>, etc. </td>
												</tr>
												<tr class = "row">
												<td class = "entry" headers = "r-Views__entry__5"><kbd class = "ph userinput userinput">View
												%viewindex+10%</kbd>
												</td>
												<td class = "entry" headers = "r-Views__entry__6"><span class = "ph uicontrol">View Hammer
												11</span>, <span class = "ph uicontrol">View Hammer
												12</span>, <span class = "ph uicontrol">View Hammer
												13</span>, etc. </td>
												</tr>
												<tr class = "row">
												<td class = "entry" headers = "r-Views__entry__5"><kbd class = "ph userinput userinput">%viewnumber%-%filename%</kbd>
												</td>
												<td class = "entry" headers = "r-Views__entry__6"><span class = "ph uicontrol">1-Hammer</span>,
												<span class = "ph uicontrol">2-Hammer</span>,
												<span class = "ph uicontrol">3-Hammer</span>, etc. </td>
												</tr>
												<tr class = "row">
												<td class = "entry" headers = "r-Views__entry__5"><kbd class = "ph userinput userinput">Demo of
												%filename%, View %viewnumber%</kbd>
												</td>
												<td class = "entry" headers = "r-Views__entry__6"><span class = "ph uicontrol">Demo of Hammer,
												View 1</span>, <span class = "ph uicontrol">Demo of Hammer,
												View 2</span>, <span class = "ph uicontrol">Demo of Hammer,
												View 3</span>, etc. </td>
												</tr>
												<tr class = "row">
												<td class = "entry" headers = "r-Views__entry__5"><kbd class = "ph userinput userinput">View
												%viewnumber%</kbd>
												<div class = "note"><span class = "run-in.note">Note:
			</span><span class = "notecontent">This is the default template. </span></div>

												</td>
												<td class = "entry" headers = "r-Views__entry__6"><span class = "ph uicontrol">View
												1</span>, <span class = "ph uicontrol">View 2</span>,
												<span class = "ph uicontrol">View 3</span>, etc. </td>
												</tr>
												<tr class = "row">
												<td class = "entry" headers = "r-Views__entry__5"><kbd class = "ph userinput userinput">View
												%viewGuid%</kbd></td>
												<td class = "entry" headers = "r-Views__entry__6"><span class = "ph uicontrol">View
												812b33921beb7aa</span>, <span class = "ph uicontrol">View
												88fdbf810d791318, etc.</span></td>
												</tr>
											</tbody></table>
								</p>
								<div class = "note"><span class = "run-in.note">Note:
			</span><span class = "notecontent">If you leave the field empty, views will be automatically
									named according to the default template. </span></div>

								<table class = "Remark" id = "table132"><tr><td class = "Remark"><span class = "run-in.tip">Tip:
				</span><span class = "notecontent">Click <span class = "ph uicontrol">?</span> at the right of the
										<span class = "ph uicontrol">File-name template</span> box to display a
									tooltip listing available keywords. </span></td></tr></table>

							</td>
						</tr>
					</tbody></table>
		</div>

	</article>
	<article class = "topic reference nested1" aria-labelledby = "ariaid-title5" id = "reference_ymy_q3g_zsb">
		<p><map name = "FPMap1"><area href = "#hj-top" title = "Back to Top" shape = "rect" coords = "416, 0, 435, 10"/></map><span class = "itemsprite"/></p><h2 class = "title topictitle2">View Collections</h2>

		
		<div class = "body refbody"><p class = "abstract">This section lets you specify a template to name the collections.</p>

			<table class = "table" id = "reference_ymy_q3g_zsb__table_zmy_q3g_zsb"><caption/><colgroup><col/><col/></colgroup><thead class = "thead">
						<tr class = "row">
							<th class = "entry" id = "reference_ymy_q3g_zsb__table_zmy_q3g_zsb__entry__1">Command Name </th>
							<th class = "entry" id = "reference_ymy_q3g_zsb__table_zmy_q3g_zsb__entry__2">Description </th>
						</tr>
					</thead><tbody class = "tbody">
						<tr class = "row">
							<td class = "entry" headers = "reference_ymy_q3g_zsb__table_zmy_q3g_zsb__entry__1"><span class = "ph uicontrol">Collection template</span>
							</td>
							<td class = "entry" headers = "reference_ymy_q3g_zsb__table_zmy_q3g_zsb__entry__2">Defines a template to use for collection names when creating
								collections. You can use alphanumeric characters and these optional
								variables in any order: <ul class = "ul">
									<li class = "li"><kbd class = "ph userinput userinput">%filename%</kbd>: Inserts the name of the
										file containing the model, without its extension. </li>
									<li class = "li"><kbd class = "ph userinput userinput">%collectionnumber%</kbd>: Inserts the
										number of the collection based on the creation order in the
										current session. For example, <span class = "ph uicontrol">1</span> is
										used for the first-created collection,
											<span class = "ph uicontrol">2</span> for the second-created
										collection etc. </li>
									<li class = "li"><kbd class = "ph userinput userinput">%collectionindex%</kbd>: Inserts the index
										of the collection based on the actual number of visible
										collections in the document. For example,
											<span class = "ph uicontrol">4</span> is used when creating the first
										collection if there are already three collections visible in
										the document, <span class = "ph uicontrol">5</span> is used for the next
										one, etc. </li>
									<li class = "li"><kbd class = "ph userinput userinput">%collectionindex+</kbd><var class = "keyword varname varname">n</var><kbd class = "ph userinput userinput">%</kbd>
										(where <var class = "keyword varname varname">n</var> is an integer): Inserts the
										index of the collection based on the actual number of
										visible collections in the document plus the number that you
										define. For example, if you
											specify<kbd class = "ph userinput userinput">%collectionindex+10%</kbd>,
											<span class = "ph uicontrol">14</span> is used when creating the
										first collection if there are already three collections
										visible in the document, <span class = "ph uicontrol">15</span> is used
										for the next one etc.</li>
									<li class = "li"><kbd class = "ph userinput userinput">%collectionindex-</kbd><var class = "keyword varname varname">n</var><kbd class = "ph userinput userinput">%</kbd>
										(where <var class = "keyword varname varname">n</var> is an integer): Inserts the
										index of the collection based on the actual number of
										visible collections in the document minus the number that
										you define. For example, if you
											specify<kbd class = "ph userinput userinput">%collectionindex-2%</kbd>,
											<span class = "ph uicontrol">2</span> is used when creating the first
										collection if there are already three collections visible in
										the document, <span class = "ph uicontrol">3</span> is used for the next
										one etc.</li>
								</ul><p>
									<div class = "notes collapse"><span class = "run-in.notes">Notes:
    		</span><span class = "notecontent">
										<ul class = "ul">
											<li class = "li">For
												<kbd class = "ph userinput userinput">%collectionindex+</kbd><var class = "keyword varname varname">n</var><kbd class = "ph userinput userinput">%</kbd>
												and
												<kbd class = "ph userinput userinput">%collectionindex-</kbd><var class = "keyword varname varname">n</var><kbd class = "ph userinput userinput">%</kbd>,
												make sure that you do not add spaces between
												characters. </li>
											<li class = "li">Collection names are unique. If the name of the
												collection calculated using the templates above is
												the same as an existing collection, then add a
												suffix to make it unique.</li>
										</ul>
									</span></div>

								</p></td>
						</tr>
					</tbody></table>
		</div>

	</article>
</td></tr></table><script type = "text/javascript" src = "../DSDocUI_Bottom34.js">/* */</script></body>
</html>
