One Asset to Rule Them All!

One Asset to Rule Them All
Clarifying the upload structure.

Being able to create Houdini Digital Assets is great, but thought should be given to their structure and hierarchy. There are multiple ways to build your assets. Here are some guidelines to help when creating digital assets and uploading them to Orbolt.

- single asset per otl file; no dependencies

This is the simplest option as it keeps everything self-contained and easy to keep track of.

- multiple assets per otl file; dependencies are 'private'

This option lets user include multiple asset definitions into a single otl file without having to worry about uploading each asset individually. The limitation is that only the main asset is visible on Orbolt and all of the dependencies are only usable inside the main asset type. The way this restriction is enforced is by using scoping mechanism in Houdini. The asset dependencies have asset type names prefixed with the main asset type eg. Object/Uberasset::dependentAsset.

- one asset per otl file; dependencies are assets from Orbolt

This option lets users build asset from other assets on Orbolt as dependencies. When you upload the otl file, the upload process will know that the dependencies are already in the store and only grab the main asset. The benefit is that if one of the dependencies gets updated the AssetBrowser in Houdini will automatically get the latest definition.

- multiple assets per otl file; all assets are independent of each other

This is the only option that currently is not supported on Orbolt. One possible solution for the current restriction is to include needed assets in the hip file by writting 'Embedded' in the path of the asset Type Properties. When you save the hip file those definitions will be saved with it. The one thing to keep in mind about this method is that those assets will be only available when the hip file is loaded.

Let us know if you have any quesitons or suggestions