The Assets concept
Quick access:
- What are assets?
- Assets and external computers/render farms
- How do you populate the Asset Browser with your own files?
- How can you pass on an asset to other users?
- Faulty or missing assets
What are assets?
Assets can be anything that is contained in or used by a Cinema 4D scene. These are, for example: objects, scenes, Node circuits, images, videos, etc. These assets can be stored locally on the hard disk or on a Maxon or other server. Assets are organized in databases that you can manage and view via the Asset Browser.
There are many assets already supplied by Maxon (e.g. in the objects or scenes category of the Asset Browser), assets you have created yourself or assets offered by third parties.
Assets - wherever they come from - can hardly be distinguished from "normal" Cinema 4D functionality. They fit seamlessly into the program. You can find assets mainly in the Asset Browser, but also in the Material menu of the Material Manager under Node Material Presets, for example. Assets can consist of a single Null object or a complex, 2GB scene.
A special form of asset is also known as a capsule. These are mainly Node circuits that allow you to extend the functionality of Cinema 4D yourself or, for example, create your own objects or generators. However, new asset capsules are also constantly being added by Maxon, which you as a Maxon One customer can call up almost monthly via the Asset Browser, for example.
Assets and external computers/render farms
Assets and capsules are stored in databases (a directory with a few files, or packed as a ZIP) and can be exchanged between users and installations. Such a directory looks like this, for example:
Such a directory can be copied and passed on as a whole. However, it is easier to export assets using the special commands provided for this purpose (see Edit menu).
Scenes that contain Asset Nodes must have access to the corresponding assets on external computers (e.g. also team render computers) - similar to bitmaps linked in materials. Otherwise, rendering errors may occur or a scene may no longer work at all. Solutions to this problem can be found below under Faulty or missing assets.
There are basically two options for avoiding such problems:
- The assets are contained in the scene (if you save them with Save Project incl. Assets, copies of the assets will be integrated into the scene file).
- The external computer will have access to assets (e.g. via your company network). Set the database paths accordingly in the Preferences ( Asset Browser tab).
The interface of asset capsules can be defined with a separate editor, the Resource Editor. You will find an example of this on this page for the asset construction groups.
How do you populate the Asset Browser with your own files?
If you would like to populate the Asset Browser with your own files/assets, you can
- add these using the first four commands of the Asset Browser Create menu (Add to Database ...) to one of these in freely selectable categories and databases or
- for Material Nodes in the Assets menu of the Node Editor using the Convert to Asset command.
How can you pass an asset to other users?
If you would like to send an asset to another user, there are basically 2 ways to do this:
- Give the recipient access to the database containing the asset (e.g. via Internet server or via databases shared in the network).
- If there is no connection to another user, assets to be passed on must be exported from the database. The recipient can then import the asset into one of their databases. This works as follows:
- Let us first assume that the asset to be passed on is already contained in a database. If this is not the case, see the previous section How do you populate the Asset Browser with your own files?
- Then select the assets to be exported - if you have assigned the keyword "Export" to the 84 assets to be exported, for example, these can only be displayed (keyword: "export") and selected - and select Create/Export Latest Version from the Asset Browser menu. Enter a file name in the dialog and save the export. The result is a zip file that you can now pass on.
- The recipient can now select Create/Import Assets from the Asset Browser menu and then select their own database in which to store the imported assets.
- Alternatively, you can link directly to the zipped database by calling up the Databases/Connect Zip Database ... command in the Asset Browser.
Faulty or missing assets
The fact that custom-created assets can also be saved in their own databases (e.g. via Create new database... in the Database menu of the Asset Browser or directly when saving a new asset via Convert to asset ... in the Assets menu of the Node Editor) can also mean that not all assets used can be found when opening a project, e.g. on another computer. Cinema 4D will display an error message directly when loading such a project. Two scenarios are possible, but both can be corrected in the same way.
Scenario 1: Missing asset in the Object Manager
If you have used a Node circuit created with asset construction groups directly in the Object Manager and the database in which this asset was saved is not available in the Asset Browser or has been deactivated there, you will receive this error message directly when loading the scene:
To solve this problem, you must activate the corresponding database in the Asset Browser or add it there. If you then update the scene via File/Old Project Version... the asset should be found again and the functionality of the scene should be restored. You can find out more about this in the troubleshooting section further down on this page.
Scenario 2: Missing asset in the Node Editor
If an asset is used within a Node circuit in the Node Editor and this asset cannot be found in the active databases of the Asset Browser, you will receive this error message when loading the scene:
You can also get similar feedback at any time in the Project Asset Inspector, which you can open via the button at the bottom of this error message or directly via the Cinema 4D Window menu.
Your Node circuit remains intact even if an asset is missing. An empty Node with the same inputs and outputs is used as a placeholder for the missing asset so that the existing connections between the Nodes can be retained. However, the function of the circuit is no longer given and is indicated by a corresponding colored marking and error message directly in the Node Editor:
Integration of missing assets
The solution to both of the above problems is to activate or relink the asset database in which the previously missing asset was stored. To do this, open the Asset Browser and activate the display of the databases using the symbol with the three stacked disks (see red marking in the following image):
If the database from which the loaded asset originates is already listed here, check whether this database is also active. To do this, right-click on the name of the database and check whether the check mark in front of Activated Database is present. If it is a database that has been integrated via a URL, you must ensure that you have an online connection to this database. If in doubt, right-click on the database and select Show Details. In the lower part of the Asset Browser, an additional will open in which you can see the storage location of the database.
If the database in which the asset was saved is missing in the Asset Browser list, select the Connect database... entry in the Database menu. You can then directly select the folder in which the asset was saved. Alternatively, URL Connect Database ... can also be used to create a link to a database that has been saved online, e.g. in a cloud. The Connect zip database... command is also available if you have an asset database in zipped form. How you can transfer a database from one computer to another, for example, has already been explained in this section.
After you have activated or reloaded the database matching the missing asset, execute File/Old Project Version ... to reload the scene and the assets it contains. If the asset is contained in the newly linked database, the project should now work again without restrictions.