Editor supports textured 3D models from a variety of programs or sources. This short guide has been put together by games artists with developers at Editor, to help you create assets that work better and more efficiently in your Editor project.
Scale & Units
Set your system and project units for your software to work consistently with Editor e.g. Metric.
Working to scale can be important for both lighting and physics simulation.
Be aware that, for example, the Max system unit default is inches and Maya is centimetres.
Editor has different scaling for FBX and 3D application files on import; check the FBX import scale setting in Inspector.
If in doubt export a metre cube with your scene to match in Editor.
Animation frame rate defaults can be different in packages, is a good idea to set consistently across your pipeline, for example 30fps.
Files & Objects
Name objects in your scene sensibly and uniquely. This can help you locate and troubleshoot specific meshes in your project.
Avoid special characters *()?"#$ etc.
Use simple but descriptive names for both objects and files (allow for duplication later).
Keep your hierarchies as simple as you can.
With big projects in your 3D application, consider having a working file outside your Editor project directory. This can often save time consuming updates and importing unnecessary data.
Build with an efficient topology. Add polygons only where you need them.
Optimise your geometry if it has too many polygons. Many character models need to be intelligently optimized or even rebuilt by an artist especially if sourced/built from:
3D capture data
Other high density Nurbs/Patch models designed for render
Where you can afford them, evenly spaced polygons in buildings, landscape and architecture will help spread lighting and avoid awkward kinks.
Avoid really long thin triangles.
Stairway to framerate heaven
The method you use to construct objects can have a massive affect on the number of polygons, especially when not optimized. In this diagram the same shape mesh has 156 triangles on the right and 726 on the left. 726 may not sound like a great deal of polygons, but if this is used 40 times in a level, you will really start to see the savings. A good rule of thumb is often to start simple and add detail where needed. It's always easier to add polygon than take them away.
If you author your textures to a power of two (e.g. 512x512 or 256x1024), the textures will be more efficient and won't need rescaling at build time. You can use up to 4096x4096 pixels, (although 2048x2048 is the highest available on many graphics cards/platforms). Search online for expert advice on creating good textures, but some of these guidelines can help you get the most efficient results from your project:
Work with a high-resolution source file outside your Editor project (such as a PSD or Gimp file). You can always downsize from source but not the other way round.
Use the texture resolution output you require in your scene (save a copy, for example a 256x256 optimized PNG or a TGA file). You can make a judgement based on where the texture will be seen and where it is mapped.
Store your output texture files together in your Editor project (for example: \Assets\textures).
Make sure your 3D working file is referring to the same textures for consistency when you save/export.
Make use of the available space in your texture, but be aware of different materials requiring different parts of the same texture. You can end up using/loading that texture multiple times.
For alpha (cutout) and elements that may require different shaders, separate the textures. For example, the single texture below (left) has been replaced by three smaller textures below (right)
One texture (left) vs three textures (right)
Make use of tiling textures (which seamlessly repeat) then you can use better resolution repeating over space.
Remove easily noticeable repeating elements from your bitmap, and be careful with contrast. If you want to add details use decals and objects to break up the repeats.
Tiling textures ftw
Editor takes care of compression for the output platform, so unless your source is already a JPG of the correct resolution it's better to use a lossless format for your textures.
When creating a texture page from photographs, reduce the page to individual modular sections that can repeat. For example, you don't need twelve of the same windows using up texture space. That way you can have more pixel detail for that one window.