# Customizing the Vehicle Template
## Customizing the Vehicle Template
If you expand the model hierarchy, you can see the target bones for positioning the arms and legs. They do not need to be updated. They are visible as markers for positioning the model's skeleton.
Attached to the bone called DEF\_FANbone is a propeller called Bike\_Fan. The motorcycle model itself has a skin.
The mesh density of the bike model should not exceed 15,000 triangles.
Upon opening the material editor, you can see that the motorcycle and propeller objects have one multisub material that does not have a name.
In the multisub we should have 2 materials - base for the bike mesh, the second for the procedurally animated boost indicator. It should be named "Indicator". For the bike material, Diffuse, Ambient occlusion, and normal map textures are allowed.
Textures must be in 2048x2048 resolution in JPEG format (PNG is allowed, but not recommended). The indicator material in the Diffuse channel must contain a nested IndicatorMap.jpg texture.
This is a texture marker, its size should not exceed 128x128 pixels.
## Customizing the Boost Indicator
You can create your own unique boost indicator. To do this, on the back of the motorcycle body, you need to select with polygons the place where the indicator material will be located, and assign its ID to them.
In order for the indicator to work as intended by your design, you need to open the unwrap of this section of the grid, make its flow as you intended for playing the offset animation, and place it on the green section of the material texture, since our motorcycle has a full boost charge at the start.
Any of the indicator design options should preferably be completely visible to the player. To do this, it is recommended to position it correctly and use a readable form.
## Customizing the Propeller(s)
The motorcycle propeller must be a separate object that is a child of the skeleton hierarchy.
The mesh density of a propeller model or any rotating object should not exceed 750 triangles. It must always be a child of DEF\_FANbone. It must always be named Bike\_Fan (case sensitive). It must contain base material.
The fan's pivot point should always be centered, and it is very important that the local axes of your fan model completely coincide with the directions of the template's axes. If you are not sure, simply attach your fan to the template.
All this is necessary for the correct execution of procedural animation of the propeller during the game.
\
You may not have a propeller, you may have more than one propeller, or you may have other design elements that spin the model. The limit on the number of rotating objects is 5 meshes. You can place them anywhere on the motorcycle.
For these objects to work correctly, they must have a logical direction of rotation and the same local axes directions as the template.
All such rotating objects should have the name Bike\_Fan at the beginning (the most convenient is to simply alternate such objects, such as Bike\_Fan\_1, Bike\_Fan\_2, etc.). They must all be children of the DEF\_FANbone bone.
Please note that the propellers will only rotate correctly if they are directed along the +Y side of the scene.
Using 3d studio max for skinning, you must add all the bones to the skin modifier. All points of the model must be connected 100% to the Bike\_root bone. Objects like Bike\_fan do not need to be skinned.
At the end of the process of creating the design and bindings, remove the Bluprint\_Stickman, Bike\_template and bounding box objects from the scene. You should still have a motorcycle mesh with a skin, in the desired position, a skeleton, and Bike\_Fan objects.
The scene must be exported in .glb format, including materials.
---
# 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://faq.faraway.com/technical-requirements-vehicles/customizing-the-vehicle-template.md?ask=
```
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.
