Create new library

Transcoding templates for 3D assets

In this scenario we assume that the main element is a 3D file. We will set a lowres (!) FBX 3D file as the preview proxy. The preview 3D file can point to the main file if it’s a game ready asset with a few MB file size.

The textures are additionals files. For each additional texture file we will create thumbnails (1k resolution) for a quick preview of the different texture layers.

The preview 3d model will load the proxy textures as it’s texture source. Please be aware that the color information is loaded if a texture is named: diff, diffuse, beauty or color

Here are the different transcoding templates that we require for this setup:

Resolution folder naming

Since the main element and the proxy of the main element are 3D files, we will not need any resolution information in the folder name. We call the “resolution“ folders: main and proxy

For the additional files (textures) we assume that these are 2D files like OpenEXR, Tiff, etc. That’s why the resolution folder has information about the width and the height.

Template Mapping

The Template Mapping looks like this:

Transcoding templates

main - 3d

main - 2d

Thumbnails

thumbnail 16:9

thumbnail 1k

For the additional files we assume that the texture files have a square format. In this case we want to render square thumbnails as well.

proxy fbx

[optional] proxy mov & filmstrip

In cases where there is no lowres 3D proxy, you can choose to instead ingest a movie file e.g. a turntable rendering. In this case it will render a proxy movie and a filmstrip. These are the default proxy mov and filmstrip transcoding templates:

Ingest

Custom thumbnail

To set a new thumbnail you can use the build in screenshot-button to take a screenshot of the current viewport.

An alternative is to drag&drop a custom screenshot or image on the element viewer. This will perform a copy of the dropped file to the thumbnail path as defined in the settings.

Custom 3D proxy

Drag&drop a 3D proxy model on the 3D viewer (right side). This will perform a copy of the dropped file to the proxy path as defined in the settings.

Automate ingest

To automate the ingest process you can use the pre ingest load Python hook. This allows you to crawl for additional texture files, custom thumbnails, turntables and a 3d proxy file to automatically populate the ingest list when loading an asset in the ingest list. This can be a real time saver if your source files follow the same pattern.

The 3D viewer uses the element proxy as defined in the settings. This can be a low-resolution 3D file.
In some cases it can make sense to point the proxy to the same file path as the main of the element

Example configuration:
Set resolution for both main and proxy task e.g. to the text main.