IN THIS ARTICLE
With Scene Settings, you can specify what data is processed from 3D scene source assets, and add modifiers to customize how the data is processed for Open 3D Engine (O3DE). Scene settings provides tabs with options for Meshes, Actors, Motions, and PhysX colliders. The Scene Settings interface presents tabs based on the types of data that are detected in the selected source asset file.
In Scene Settings you can specify any number of meshes, actors, PhysX colliders, and motions to process from a single source asset. Source assets often generate multiple product assets. A mesh group, for example, can generate an
.azmodel product asset, several
.azlod product assets, and multiple
.azbuffer product assets for the
.azlod product assets. Depending on the selected modifiers and options, a single static mesh group can generate dozens of product assets.
You can see the product assets by expanding the asset list of a source asset in Asset Browser. In the image below,
Lucy_High.fbx is the source asset and the assets contained within the highlighted box are all product assets of
Scene Settings operates on one source asset at a time. To open Scene Settings, use the steps below:
In O3DE Editor, in Asset Browser, select the 3D scene source asset to modify. You can use the search bar at the top of Asset Browser to filter the list.
Right-click the 3D scene source asset and then choose Edit Settings….
Note:O3DE integrates Open Asset Import Library to parse 3D scene source assets with support for
.gltfenabled by default. If you want to experiment with other scene formats supported by Open Asset Import Library, you can edit the
o3de/Registry/sceneassetimporter.setregsettings file and add format extensions to the
"SupportedFileTypeExtensions":list. When you add a new format extension, the Edit Settings… option appears in the context menu for that source asset format.
The asset groups you create, the modifiers you add, and the options you set in Scene Settings are all saved to a
.assetinfo sidecar file when you choose Update on the bottom right of the Scene Settings interface. Asset Processor recognizes the sidecar file as a source dependency for the source asset, and automatically processes the source asset when the
.assetinfo file is created or updated.
You can create, for example, a 3D scene source asset that contains plants of different types and sizes, with skinned meshes and LODs, and then use Scene Settings to specify mesh groups, actors, motions, and PhysX colliders for each plant contained in the source asset. The information needed to process all the plants is contained in a single
.assetinfo file. It’s important to understand that if you choose to process many product assets from a single source asset, a change to any aspect of the source asset or its dependencies will automatically reprocess everything contained in the source asset.
.assetinfo sidecar file is formatted with JSON, is human-readable, and can be easily generated and modified through automated processes such as a Python script.
There are four tabs in Scene Settings: Meshes, Actors, Motions, and PhysX. Each tab provides modifiers and options specific to processing data of that type. The tabs that are displayed for a particular source asset depend on the contents of the source asset. The table below provides links to topics for each tab, and the data required in the source asset to make the tab available in Scene Settings’ interface.
|Meshes||Create mesh groups and modify process job settings for meshes. Mesh processing generates ||The source asset must contain at least one mesh.|
|Actors||Create actor groups and modify process job settings for actors. An actor is any source asset (not necessarily a character). Actor processing generates ||The source asset must contain at least one bone and a skinned mesh.|
|Motions||Create and modify process job settings for motions (animation). Motion processing generates ||The source asset must contain a skeleton with keyframe animation.|
|PhysX||Create PhysX mesh groups and modify process job settings for PhysX colliders. PhysX processing generates ||The source asset must contain at least one mesh. The PhysX Gem must be enabled for your project to process and use PhysX colliders.|