Hi @HolgerBiebrach, you are right, the content browser is gone, and it is completely replaced by the Asset Browser. The correct way would be to provide a Database (the equivalent of the lib4d but for the Asset Browser) to your user, so if they are before R25 they should use lib4d, if they are in R25 they should use the database.
To do the conversion follow the next step:
- Create a new DataBase.
Open the Asset Browser, and click in the top menu in the 3 lines.
Then left click in a Databases this will open a contextual menu, select
Create Databases..., select a folder (an empty one) where the Database will be created.
- Import the lib4d file.
Go to the the Asset Browser Create menu, and click the Import Legacy Library entry, and select your lib4d file. A popup should open to select the destination Database, select the one you just created.
- Share this Database to the user.
zip the database folder you selected when you created the database and share it to the user.
- (User) Load the database.
Extract the zip file, go in the Cinema 4D Preferences, in the
Asset Browser and add the extracted zip folder. Restart Cinema 4D or open the Asset Browser and go to the Edit menu -> Reload Databases. The content will be in the Converted folder.
The C++ API for the Asset Browser is available in C++, in R25 but not the Python API. The main issue is that the Asset Browser UI does not expose the URL of an Asset, but if you have an
maxon.Url of an asset, you can load it the same way you did with
You can find an example in C++ how to load a Material within the Loading Materials from AssetDescriptions into a Scene.
Finally if you want to learn more about the Asset API I advice you to read the Asset API HandBook, to have a good overview of main classes and how things works together.