# Create a 3D asset for GuidiGO: Guidelines (EN)

## 1. Modeling in 3D Software (3ds Max)

1. Each model you make in 3D software should have "healthy geometry", which means no overlapping, flipped polys, etc. You should always work with quads, separate polys on smoothing groups, and apply turbosmooth (but you should rasterize it before exporting FBX file for Unity).
2. Unwrapping is preferred when you have model with few materials on it. It is also necessary to unwrap model if you want to bake light on its diffuse texture, or create lightmap.
3. For materialization use standard mental ray material (not V Ray or Corona). Unity supports NORMAL maps, so you should convert your bump map into normal via Photoshop, using different plugins for conversion, which you can find on internet, for free.
4. Number of polys of a model that will hopefully work on Tango is less than a million. This depends on sizes of textures and complexity of a code and animation in project.
5. Always convert your model into editable mesh before exporting it as FBX.
6. Unity is in meters, so set your metrics in meters.

## 2. Animation in 3ds Max

Export models from 3ds Max as FBX, in order to import it in Unity. You can import .max file also, but in that case, Unity makes conversion in FBX, and it can cause program to break and go down.

In case of animations, FBX is a big downside, since it only exports a few kinds of animations from 3ds Max:

* transition, rotation, scale
* character animation (bones)
* morpher

Except morpher, you can't export animations of some other modifier (bend, FFD...). 

## 3. Unity

1. **Shaders**:
   1. If you are using scanned models with photorealistic or baked textures, use UNLIT shader in Unity. That shader doesn't receive or emit shadows, and looks great with good textures. Most important - there are no bugs with shadows during animation.
   2. If you are painting textures by yourself, or you are not baking light, you should use STANDARD shader, since this shader depends on light from project and emits shadows in real time (if you have some animations in project, you should use this shader).
2. **Transparency**: There is a known bug in Unity: it goes crazy if you have two models, one behind another, that are semi-transparent. The program doesn't know what to render first, so you can notice some unrealistic overlapping. Very often you can fix it with code.
3. **Textures** should be as good as possible, regarding quality. 1k textures are minimum. Unity compresses texture bigger than 2k, so you should manually return them back to 4k, for example.
4. **Always create empty game object,** with pivot in 000 000 111, and put your model in its hierarchy. Sometimes, if you do not do that, your model may "fall down".


---

# Agent Instructions: 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:

```
GET https://support.senar.io/senar-api/create-a-3d-asset-for-guidigo-guidelines-en.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.