Each row represents a prim in the scene graph tree.

The icon shows the prim type, unless the prim has a kind, in which case the icon shows the kind.

The tree displays the prim name in different colors to indicate different states:

The tree can also display dot icons next to the names of primitives and their children, which have changes not originating from nodes:

A Favorites folder can be populated either from the context menu on a primitive in the scene graph, or by dragging primitives from the scene graph into the Favorites folder. This folder provides a convenient location where commonly used primitives can always be accessed quickly. Primitives in the Favorites folder are merely shortcuts, not actually a separate scene graph, and so will also appear in the main scene graph tree. The contents of the Favorites folder are dictated by the pinnedprims parameter of the current LOP Network. The parameter must be an explicit list of primitives; patterns and wildcards are not supported.

The primitive’s type name.

If the prim has any variants, this is a pop-up menu showing the list of “Variant set: selected name” items.

The kind name for this prim, if any.

The render purpose set on this primitive. You can enable and disable various purpose tags in the viewport. Purposes are not extensible. The only possible values are default, render, proxy, and guide.

The name of the material bound to this primitive. Hover the mouse over this column to see the full path. The text will be in italics if the material binding is a result of inheriting a direct binding on an ancestor primitive.

The path to this prim’s render proxy, if any.

(A primitive set to render purpose may have a proxyPrim relationship to a primitive with proxy purpose.)

The computed draw mode for the primitive. Draw mode can only be set on primitives with a kind, and which are part of a valid Model Kind Hierarchy.

Changing the draw mode of a primitive also changes the draw mode of all descendants, unless you give them their own viewport overrides.

Changes to this column cause a red dot to appear in the menu, and on the modified primitive. This indicates that the primitive has a viewport-only override applied to it. Such overrides will not affect the USD saved to disk or rendered with a USD or USD Render ROP.

Only meaningful if “Populate all primitives” is off. The population mask only affects the viewport, so all primitives are always visible in the scene graph tree even if they are not marked as “populated”.

When “populate all primitives” is off, this column will have one of four states.

You can click in this column to mark the primitive explicitly populated (), or if it’s already explicitly populated, to remove it from the list of explicitly populated prims.

Only meaningful if “Load all payloads” is off. The visual indicators are the same as the P (Populated) column, but indicate to whether payloads are loaded or not. Like the Populated column, this only affects the viewport.

As with the “populated” column, explicitly including a prim in the “loaded” set also includes all child primitives in the “loaded” set.

Click the icon in this column to switch the primitive between active and inactive (in the view override layer).

A primitive that is not active will not have any effect on the scene as it appears in the viewport. A deactivated primitive does not report having any child primitives. Unlike the populated and loaded flags, changes to this column do affect the scene graph tree, hiding (or exposing) any child primitives, depending on the setting.

Changes to this column cause a red dot to appear next to the icon, and on the modified primitive. This indicates that the primitive has a viewport-only override applied to it. Such overrides will not affect the USD saved to disk or rendered with a USD or USD Render ROP.

Click the icon in this column to switch the primitive’s visibility between “inherit” and “hidden” (in the view override layer).

A primitive that is hidden will not appear in the viewport. The only two visibility states a prim can have are “inherit” and “hidden”, so all descendants of invisible primitives will also be invisible, and a child of an invisible primitive cannot be made visible.

Unlike the active state or a primitive, the visible state can be animated. The icon will indicate if the value for this primitive is animated (has more than one time sampled value). But clicking this column to change the visibility state of the primitive will override any animation as well, and the visibility will remain constant at the overridden value.

Changes to this column cause a red dot to appear next to the icon, and on the modified primitive. This indicates that the primitive has a viewport-only override applied to it. Such overrides will not affect the USD saved to disk or rendered with a USD or USD Render ROP.

Soloing is applied independently to geometry and light primitives.

• Primitives that are neither lights nor geometry will have no icon in this column.

• Making a light solo will leave geometry primitives in the “nothing soloed” state.

• Soloed lights are made active, while all other lights are made inactive.

• Soloed geometry is made visible while all other geometry is made invisible.

This means that soling a single primitive may result in overrides being set on a large number of primitives, all of which will display with red dots. Also, like visibility and activation, soloing an ancestor primitive will make its children visible (for geometry) or active (for lights) as well.

When primitives are soloed, the display and active columns are blanked out, because the values of these columns are ignored when soling is applied. The display and active overrides are restored when soloing is disabled.

• Click here to make this prim solo.

• If you click here when the prim is already solo, nothing will be solo.

• ⌃ Ctrl-click here to add or remove the prim to/from the solo group.

Like the visible, active, and draw mode columns, soloing applies to the view override layer. Changes in this layer are not saved to disk in USD files or rendered.

Click the icon in this column to toggle the primitive’s selectability (in the view override layer).

This flag affects whether the primitive can be selected in the viewport. All primitives can always be selected in the scene graph tree, which will set the viewport selection as well, regardless of this setting. This flag is useful when selecting primitives in the viewport, but where certain primitives are “background” primitives which are often picked up by a box selection, but are of no interest for the current operation.

Setting a primitive to be selectable or unselectable affects all descendant primitives, down to the next primitive in the hierarchy with an explicit setting for this flag. The selectability of a primitive can also be controlled with a Configure Primitive LOP.