# General Information

> Important information about Asset Transformer Studio's core technology and general behavior

Find below important information about Asset Transformer Studio core technology and its general behavior.

For definitions of important terms, see the [Glossary](/asset-transformer-studio/2026.5.0/manual/data-preparation-fundamentals/glossary.md), and other sections in the [Data Preparation Fundamentals](/asset-transformer-studio/2026.5.0/manual/data-preparation-fundamentals/_index.md) section.

## Coordinate system

Asset Transformer Studio uses a right-handed coordinate system, it defines +Y as up, +Z as forward, and -X as right. The front faces +Z.

![Coordinate system](/api/media?file=/asset-transformer-studio/2026.5.0/media/STUDIO_CoordinatesSystem.jpg)

## Units

The units for all linear distances are millimeters.

The unit for angles is degrees.

## Functions behavior

Many functions require entities as input to work, whether it is a list of one or more occurrences, materials, components, images, etc.

For example, the [Tessellate](/asset-transformer-studio/2026.5.0/manual/data-preparation-fundamentals/about-tessellation.md) function requires a list of occurrences to process: all [BRep](/asset-transformer-studio/2026.5.0/manual/data-preparation-fundamentals/about-3d-models-types.md) geometries contained in that list will be tessellated.

For functions that require a *list of occurrences* or a *root occurrence*, the user can define the `Root` node of the scene as the input for these functions.

In that case, **all** the occurrences of the scene will be processed, whether they are visible or not (the full hierarchy is parsed).

> **Warning:**
>
> In Asset Transformer Studio specifically, if a selection is empty when executing a function that requires a list of occurrences to be processed, the whole scene will be processed! Find more information about this specific selection behavior in: [About Asset Transformer Studio and Selections](/asset-transformer-studio/2026.5.0/manual/data-preparation-fundamentals/general-information/about-studio-and-selections.md)

## Export

Asset Transformer Studio can export 3D models (and [textures](/asset-transformer-studio/2026.5.0/manual/working-with-asset-transformer-studio/exporting-files/exporting-textures.md)) in many 3D file formats (see the whole list in [Supported File Formats](/asset-transformer-studio/2026.5.0/manual/supported-file-formats.md#export)).

More information in the page [Exporting Files](/asset-transformer-studio/2026.5.0/manual/working-with-asset-transformer-studio/exporting-files.md).

## Textures

When textures/images are imported in Asset Transformer Studio (through the import of a 3D model, or directly importing an image file in the [Texture Editor](/asset-transformer-studio/2026.5.0/manual/user-interface/menu-bar/materials-menu/texture-editor.md)), they are actually imported and stored as a raw image (which can cause the .pxz scene file to be heavy).

More information in the page [Exporting Textures](/asset-transformer-studio/2026.5.0/manual/working-with-asset-transformer-studio/exporting-files/exporting-textures.md).

## Materials and textures deletion

When deleting a model from the scene using the [Viewer](/asset-transformer-studio/2026.5.0/manual/user-interface/window/viewer.md) or the [Product Structure (Tree)](/asset-transformer-studio/2026.5.0/manual/user-interface/window/product-structure-tree.md), **materials and textures are not deleted along with it**.

They need to be manually deleted using the [Material Editor](/asset-transformer-studio/2026.5.0/manual/user-interface/menu-bar/materials-menu/material-editor.md) and the [Texture Editor](/asset-transformer-studio/2026.5.0/manual/user-interface/menu-bar/materials-menu/texture-editor.md), or using functions like [Clear Unused Materials](/asset-transformer-studio/2026.5.0/api/python/scene_functions.md#cleanunusedmaterials) and [Clear Unused Textures](/asset-transformer-studio/2026.5.0/api/python/scene_functions.md#cleanunusedimages).