Catálogos de recursos

Los catálogos de recursos ayudarán a organizar los recursos. Lucirán similares a directorios de archivos, pero siendo completamente independientes de la ubicación de los archivos .blend. Será posible asignar cada recurso de un archivo .blend a su propio catálogo o tener un catálogo grande con todos los recursos de todos los archivos .blend combinados. Todo dependerá de lo que se considere más apropiado, según el caso.

Similares a las Colecciones, los catálogos podrán ser anidados, es decir, será posible tener un catálogo principal que contenga a varios catálogos anidados. Por ejemplo, esto permitirá tener un catálogo de recursos para «Muebles» con subcatálogos de «Mesas», «Sillas», «Lámparas», etc…

For more technical information, see Asset Catalogs on the Blender Wiki.

Ejemplo de la estructura del sistema de archivos y de los catálogos.

Ubicación principal de un recurso

There can be as many catalogs as you want, but an asset can be assigned to a single catalog at a time. This is similar to a file system, where a file is only in one directory (ignoring advanced things like symbolic links).

Catalogs themselves can be nested and moved by dragging and dropping. Moving a catalog will not modify the assets it contains; they will simply move along to the new location of the catalog.

Selecting a catalog in the Asset Browser will show all assets in that catalog and in child catalogs. So, in the preceding example, selecting Characters/Ellie/Poses will also show assets from Characters/Ellie/Poses/Head and Characters/Ellie/Poses/Hands.

Asignación de un recurso

Assigning a selection of «Scale material» assets to a catalog.

To assign assets to a catalog, just select and drag the assets on top of the catalog.

Truco

You can assign an asset to the «Unassigned» catalog, this will remove it from any existing catalogs.

Componentes de un catálogo

Each catalog consists of a catalog path, a UUID, and a simple name. Normally you would only deal with the catalog path; the rest is for internal Blender use and/or for emergency situations.

Ruta de un catálogo

The path of a catalog determines where in the catalog hierarchy the catalog is shown. Examples are Characters/Ellie/Poses/Hand or Kitbash/City/Skyscrapers, which would result in the following catalog tree. The highlighted catalog has path Characters/Ellie/Poses/Hand.

Example tree of asset catalogs.

UUID

Each catalog has a UUID, which is normally hidden from the user interface (enable Developer Extras and the experimental Asset Debug Info option to see them). This is what is stored in the asset, and what determines the «identity» of the catalog. As a result, a catalog can be renamed or moved around (i.e. you can change its path), and all assets that are contained in it will move along with it. This only requires a change to the catalog itself, and not to any asset blend-file.

Nombre simple

Each catalog has an optional simple name. This name is stored along with the UUID in each asset. The purpose is to make it possible for humans to recognize the catalog the asset was assigned to, even when the catalog definition file (see below) is lost.

Like the UUID, the simple name is normally hidden from the user interface. Enable Developer Extras in the interface preferences to make it visible in the Asset Browser.

Archivos de definición de un catálogo

Asset catalogs are stored in Catalog Definition Files (CDFs). Blender 3.0 supports a single CDF per asset library. It is stored in blender_assets.cats.txt in the root directory of the asset library. If the file does not exist, Blender will create it when the catalogs are saved. When catalogs are changed, Blender updates that file, but also creates a backup of the previous state to a file named blender_assets.cats.txt~.

A cuál archivo escribir

Asset catalogs can be saved independently of the blend-file; the catalog editor has its own «Save» button.

Formato

Catalog Definition Files (CDFs) are relatively simple text files, encoded in UTF-8. Each CDF consists of a version indicator, and a line of text per catalog. Each catalog line is colon-separated, of the form {UUID}:{path}:{simple name}.

Ejemplo

This is an example of a valid catalog definition file:

# This is an Asset Catalog Definition file for Blender.
#
# Empty lines and lines starting with `#` will be ignored.
# The first non-ignored line should be the version indicator.
# Subsequent lines are of the format "CATALOG_UUID:catalog/path/for/assets:simple catalog name"

VERSION 1

313ea471-7c81-4de6-af81-fb04c3535d0e:catalog/without/simple/name:
ee9c7b60-02f1-4058-bed6-539b8d2a6d34:character/Ellie/poselib:character-Ellie-poselib
cd66bf52-58f4-45cb-a4e2-dc0e0ee8f3fe:character/Ellie/poselib:character-Ellie
4eb44ec6-3424-405b-9782-ca006953e799:character/Ellie/poselib/white space:character-Ellie-poselib-white space
b63ed357-2511-4b96-8728-1b5a7093824c:character/Ružena/poselib:Ružena pose library
dcdee4df-926e-4d72-b995-33106983bb9a:character/Ružena/poselib/face:Ružena face
fb698f2e-9e2b-4146-a539-3af292d44899:character/Ružena/poselib/hand:Ružena hands

Rutas válidas de catálogo

Las rutas de catálogos deberán seguir las siguientes reglas:

• All paths are absolute; there is no difference between /a/b and a/b.

• Only / as separator (no \; think less filesystem path and more URL).

• Not empty (it’s required for a valid catalog).

• No empty components (so not a//b; a/b is fine).

• Invalid characters: :, \.

• Paths are always interpreted as UTF-8.