This is a 3D model of the vehicle, which will be visible when the camera is close to it.
It's created using 3D modeling software such as Blender, 3ds Max, Maya or SketchUp.
The actual mesh file contains vertices (their coordinates, UV mapping, normals and colors) and triangles.
Continuous connected parts of the mesh (called elements) which are closer than 5cm to 0 (ground) will be automatically detected as wheels. This it not relevant for ships, monorails, cable cars.
- FBX (most commonly used)
- OBJ (doesn't support vertex colors)
Pivot / Origin
The pivot point or origin represents the center point on the ground, on which the vehicle will drive. It's usually represented using a red/green/blue axis gizmo.
Make sure you are exporting a single object, which doesn't have any rotation or scale.
This can be done using "apply rotation & scale" in Blender, or "reset xform" in 3ds Max, and exporting only the selected object.
Vertex colors are automatically generated to determine wheels, which will spin based on the shader of the vehicle.
Example UV mapping using visible horizontal tiling on the bottom.
Triangle counts of some vanilla vehicles.
The absolute limit for a mesh is 65536 vertices.
Comparison between main and LOD meshes for the vanilla police car.
LOD stands for level of detail. This is the mesh visible from a distance. It must be as simple as possible.
If you don't provide an LOD mesh, the game will try to generate one automatically, which may have visual issues, so it's highly recommended to make a custom LOD mesh.
UV mapping for LOD mesh using automatic mapping in 3ds Max. No overlap and contained within the main tile - good for baking.
The UV mapping must be within the 0-1 area (main tile) of the UV map, no tiling is allowed. This is because ingame all the LOD textures are combined into a single texture called an atlas, so having incorrect uv mapping will end up putting the texture of some other random vehicle on your LOD.
These determine the color and material properties of your vehicle.
Example diffuse texture for a vehicle.
It will look very bright, contrasty, and saturated in the game, so make sure to reduce the saturation and limit the brightest parts to a medium/light gray below 150 RGB.
If you don't import a diffuse map, it will default to white.
Example alpha texture for some railings and metal beams.
Using lighter values for the invisible parts will decrease the chance of small details like railings disappearing completely.
Semi-transparency is not supported, you need to use the rotors shader for that.
If you don't import an alpha map, it will default to fully opaque or fully visible.
Determines which parts will be affected by color variations. White means fully affected and black means not at all.
The diffuse will get multiplied by the color variation, that means the resulting color will look darker than the original diffuse.
For emergency vehicles (police, ambulance, firetruck) this determines where the siren is. The sirens are marked white, and everything else is black.
If you don't import a color map, it will default to full color, but the "use color variations" setting must be enabled for the colors to appear.
Example illumination map for a vehicle.
Example illumination map for a train.
For the train shader, this defines always on lights (headlights/taillights) and lights which are only on at night (windows). The always on lights are 255 (white) and the night lights are 0 (black), everything else is 128 (medium gray).
For the ship shader (used by ships, monorails, cable cars), this defines lights which are only on at night (windows). The always on lights are 255 (white), everything else is 0 (black).
If you don't import an illumination map, it will default to black.
Transitions between different specular values produce artifacts on the normal map and vice versa, even if a normal map is not imported.
The specular highlight from the sun is very big and bright, so you might want to use very low (0-10%) specularity for surfaces facing upwards, like roofs.
If you don't import a specular map, it will default to no specularity.
Example normal map for rocks.
Problem: normal maps appear incorrectly if the asset importer mesh rotation feature is used.
Problem: default normal map value is 0.5, which isn't possible by using 127(left) or 128(right). Image shows the same flat normal map on faces with different UV rotation/flip.
This can be made from the diffuse or a height map (brighter colors will look extruded out more) using a normal map generator online, a photoshop plugin like xNormal, or standalone software such as CrazyBump.
The normal map generator should be set to +X +Y, which means no color channel inversions are required.
High specularity and normal map don't work well together because of the compression, so you might want to paint over shiny parts parts with a solid color before generating a normal map, or paint over these parts 128,128,255 on the final normal map.
Read more in the normal map article.
If you don't import a normal map, it will default to a flat normal map - no bump.
Use a lossless format like .PNG.
The game supports other formats as well, but there is no reason to use another one, it doesn't matter how much your texture is compressed or even if it's completely solid or complicated, the game will convert it to a DXT format, so the final size won't be affected by anything other than resolution.
Make sure the texture is 8 bit, because a 16 bit image can't be imported.
Texture sizes of various vanilla assets. See resolution in top right corner of preview window.
Powers of 2 is a standard practice in 3D graphics, which means sizes such as 1024x1024, 1024x512, 256x512, 2048x128 etc. It is recommended to stick to this standard, but the most important thing is that your width and height must be divisible by 32, otherwise your texture will be corrupted by compression. You can also use a very small size like 32x16 or 16x16 if necessary.
If you don't provide LOD textures, the game will try to bake them using the UV mapping your LOD mesh has, and that may cause visual issues, so it's recommended that you create your own LOD textures using baking.
Powers of 2 is a standard practice in 3D graphics, which means sizes such as 256x256, 256x128, 128x64, 64x64 etc. It is recommended to stick to this standard, but the most important thing is that your width and height must be divisible by 32, otherwise your texture will be corrupted by compression. You can also use a very small size like 32x16 or 16x16 if necessary.
Source files of an example vehicle ready for import.
The mesh can have any name, but it's not recommended to use spaces or underscores, as the name for the lod mesh name will be meshname_lod.
The textures must have the same name as the mesh, but with the texture type identifier after it, so the result will be names like meshname_d.png and meshname_lod_d.png
Files ready for import.
You should place the mesh and texture files in the import folder located here:
The AppData folder is hidden by default, you can access it by pressing Windows + R and typing in appdata.
The template you choose will determine many things about your building:
- AI and corresponding stats (like capacity for cargo, or passengers for a plane)
- max speed
- light effects and their position
- Item class (defines service, for example industrial - farming for the tractor)
- use color variations
- shader, material properties (color variations)
Importing a mesh in asset importer.
- max speed
- use color variations
You can add other vehicles as trailers which are attached to your vehicle, this is used for cargo trailers, train/tram cars.
You can change the 4 color variations.
You can add additional meshes as sub meshes, which appear only when certain conditions are met, for example the vanilla bus has a left hand traffic sub mesh, and the forestry trailer has a loaded trailer sub mesh.
Train trailers can display different sub meshes based on the cargo type they are carrying using this mod.
Flags are required and forbidden conditions, which determine when the sub mesh shows up, and also when the main mesh is hidden.
Flags used for when the vehicle is parked.
ModTools scene explorer and console.
- AI - Asset AI Changer by Snow_Cat & cerebellum
- Item Class (service) - Asset ItemClass Changer by Snow_Cat
- Many other advanced vehicle settings - Extended Asset Editor by Acc3ss Violation
Advanced article on using prop shader for monorail coming later.
Trailer Sub Mesh
When loading a trailer template, the sub mesh UI doesn't show up. To fix this, open the scene explorer, go to Tool Controller > ToolController > m_editPrefabInfo > m_placementStyle and set it to automatic, save and load the asset, the sub mesh UI should show up. Once you add the sub mesh, change m_placementStyle back to procedural and save your asset.
Sub Mesh Flags
The flags for the main mesh and sub meshes are oversimplified in the UI. The main mesh conditions are actually just like for any sub mesh, and the regular flags and parked flags are seperate fields. You can change them using this script.
Advanced article on custom vertex paint and parameters for tyres coming later.
Save asset window.
The asset name visible ingame.
Snapshot, Thumbnail, Tooltip
There are 2 different folders you can open by clicking the folder icons:
- On the snapshot image, bottom right corner.
Use this one to replace the snapshot, you can replace it with a 1x1 px image to save on the asset file size. This image will only be visible in the content manager. It will also default as the Steam preview image, but you can change that seperately when publishing.
- Below thumbnail, on the right side.
Use this one to change the thumbnail (109x100) and tooltip (492x147) of your asset.
Once you change the main thumbnail, the hover/active states will update automatically.
Local Assets Folder
CRP files in the local assets folder.
The AppData folder is hidden by default, you can access it by pressing Windows+R and typing in appdata.
Share button in content manager.
Go to the content manager > assets and find your asset, then click share.
Title and Description
You can change these on the Steam Workshop later.
Steam Preview Image and Content Folder
Publish window and content folder.
There is also the content folder, which is where the actual asset file is. You can paste multiple .crp files here if you would like to upload a pack of assets.
On the Steam Workshop page for your asset, you can:
- add it to a collection
- add images and videos
- add contributors and links
- add required items and DLC
- change visibility to friends only or private
To update your own item, you must subscribe to it first, then it will show up in the content manager. It won't be the same as a local asset, as it will show an "update" button.
When you click update, click the folder icon, and now you can change the Steam preview image and put your new asset in the content folder. If updating a pack, remember to put all the assets inside the content folder.
You can also add more assets to make it a bigger pack.
Comparison between local (top) and workshop published (bottom) prefab names shown in ModTools.
It's the hidden internal name used to refer to your asset in savefiles.
It's the reason why a local asset is not the same as a workshop published asset.
For local assets: filename.Asset Name_Data
For published workshop assets: SteamID.Asset Name_Data