> For the complete documentation index, see [llms.txt](https://animotive.gitbook.io/animotive-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://animotive.gitbook.io/animotive-documentation/asset-import-preparation/character-import/characters-basic-points-for-meshes-and-textures.md).

# Characters: Basic Points for Meshes and Textures

**Meshes**

The following bullet points are tips and best practices for Animotive-ready meshes.

\
![](https://lh7-us.googleusercontent.com/SQL6YoMAFhK9Sr6P02dTnZaPFFHU0RZ_ZR1iuF2d-ZRz-bo8bdZuTl0v4Fw3lcS9HzLUsR2yPT6c98p9MTjSP_ezC6XW5htPfQLnOa1A9ipLYI_kesbcfR1NGksRG4PFcy015supMRBFWW5gc0Mp-AA)

* Characters should be in a valid, palms down T-pose for best results where possible
* Multiple meshes are supported
* Poly counts should be between 500 - 250,000
* All facial blendshapes (shape keys) should be named correctly; according to the system being used, eg; [ARKit](https://arkit-face-blendshapes.com/) or [MetaQuest](https://developer.oculus.com/reference/unity/v46/class_o_v_r_face_expressions/#a05d1349f5dbea07a93aa00b68ee6bf9fab75fcdd2d72d9e000beab48622402d93)
* All normals are facing correctly including on all blendshapes
* Each mesh must have a UV map
* Scaling is based on real world sizes, remember to check your units in your modelling software.
* Transforms should be zeroed out
* Feet and mesh origins should be at world zero
* Make sure the model is as clean as possible, get rid of unused textures and materials, bake modifiers, delete history, unnecessary nodes, animation curves, deformers etc

**Textures**

* Animotive accepts: PNG, JPG
* Ensure that all texture maps are square and multiples of 256 pixels
* Texture maps should be no larger than 4096 x 4096 resolution
* Texture maps should conform to Unity’s usual URP format. If using a software like Substance Painter, look for the Unity Metallic workflow output presets
* For best practice, remember to clearly name your texture maps with the name of the object, the channel it should be applied to and the resolution of the file, eg; “Table\_Albedo\_1024” or “Chair\_MetalSmooth\_2k”
* For best practice, remember to clearly name all your materials. Having clear names on your textures and materials will make things much more manageable if you need to hook up multiple textures to multiple materials
* Although animotive can handle multiple textures on a model, it is good practice to consolidate materials and textures into as few as possible. It will also be easier to manage if you have a large scene with many characters, props and sets
* Using trim sheets is a great way to use texture maps efficiently where possible
* Emission is currently not supported in Animotive
* UDIMs are not currently supported in Animotive


---

# 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://animotive.gitbook.io/animotive-documentation/asset-import-preparation/character-import/characters-basic-points-for-meshes-and-textures.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.