Navigation
BlueprintAPI > BlueprintAPI/Utilities > BlueprintAPI/Utilities/Struct
Adds a node that breaks a 'Usd Metadata Import Options' into its member fields
Inputs
| Type | Name | Description |
|---|---|---|
| struct | Usd Metadata Import Options |
Outputs
| Type | Name | Description |
|---|---|---|
| boolean | Collect Metadata | Whether to collect USD prim metadata into AssetUserData objects at all |
| boolean | Collect From Entire Subtrees | Whether to collect USD metadata from not only a particular prim, but its entire subtree,when apropriate. This is useful when used together with collapsing settings, for example. |
| boolean | Collect On Components | We will always add the collected metadata to AssetUserData objects assigned to all generated assetsthat support them. When this option is enabled, however, we will also separately collect USD primmetadata and add that to AssetUserData objects added to every spawned component.This can be useful for tracking metadata on prims that don't usually generate assets, like simpleXforms, cameras, lights, etc., or for collecting metadata for prims with alternative draw modesenabled, like bounds or cards: We won't generate the usual assets for those, but the metadata couldstill be collected on the components with this option. |
| string | Blocked Prefix Filters | When collecting metadata, we will ignore all entries that start with these prefixes.Note that you can use the ":" separator for nested dictionaries, so for example using"customData:ign" to ignore anything within the "ignoredValues" dictionary inside the"customData" dictionary |
| boolean | Invert Filters | When this is false (default), the "BlockedPrefixFilters" property describe prefixes to block, andmetadata entries that match any of those prefixes are ignored and not collected.When this is true, the "BlockedPrefixFilters" property is inverted, and describes prefixes to allow.In that case, entries are only allowed and collected if they match at least one of the provided prefixes. |