> For the complete documentation index, see [llms.txt](https://video-copilot.gitbook.io/element2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://video-copilot.gitbook.io/element2/importing-3d-objects-into-element/exporting-3d-objects-for-element.md).

# Exporting 3D Objects for Element

## Preparing Materials

For pieces to be accessed as separate, editable pieces in Element, they need to have separate materials mapped to the polygons. In most 3d applications you can drag a new material to the pieces you need to be separate in Element.

<div align="left"><figure><img src="/files/ctKAt9QHejCde5EWvAJI" alt=""><figcaption></figcaption></figure></div>

Giving each object it's own material in the full 3d app then importing to Element as an .obj or C4D file, allows them to be adjusted and separated in Element. You can turn off pieces with the blue buttons next to each material.

<div align="left"><figure><img src="/files/sRx5LlLFDvksP7tyw5au" alt=""><figcaption></figcaption></figure></div>

## Linking Textures Files

In Element V2 you have the option to automatically link textures to your material by loading an MTL file with the obj file. Most 3d programs have an option in the obj exporter settings to export an MTL file along with the obj. The MTL file is basically just data telling the obj file where to pull texture files from.

<div align="left"><figure><img src="/files/ITmNXbYgBkHmrwu99cKp" alt=""><figcaption></figcaption></figure></div>

Put the obj file and mtl file in the VideoCopilot/Documents/Model folder so that it shows up in the Element Scene Setup Model browser. Select the model and and import settings box will pop up with options. Once you hit ok, the model should import with the textures linked to the corresponding channels. If you are importing from C4D, see next section.

## Exporting from 3D Applications and Settings

Objects need to be exported as an .obj file

## Triangulating Objects before Exporting

Element auto-triangulates models that aren’t already triangulated. Performance will be increased with the model Pre-Triangulated.

## Surface Normals

Make sure that all polygon normals are facing the correct way.  If the Polygon Normals are backwards they will appear as invisible.

## UVW Coordinates

Make sure that the UVW Coordinate information is being saved out with your obj. This is usually a checkbox in the export settings. This is the information telling the program how to map materials.

## Smoothing groups

Make sure that the smoothing groups information is being saved out with your obj. This is usually a checkbox in the export settings.  Without this, the model might look blocky.

## Auto Normals & Edge Threshold

<div align="left"><figure><img src="/files/3RE5MKTWq4OurdR7A2Ra" alt=""><figcaption></figcaption></figure></div>

If your program does not have an export setting for smoothing groups, you can try using Auto Normals and Edge Threshold in Element to try to get a smoother look. See [3D Object Troubleshooting](broken://pages/NpHxGa1okoTRGAVyq9U8) if your model does not look as expected.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://video-copilot.gitbook.io/element2/importing-3d-objects-into-element/exporting-3d-objects-for-element.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.