Example mud decals.
The mod is not required for creating and saving the asset, but only for loading it ingame.
It's not required to make your own mesh anymore, you can download the premade decal mesh, ready to be used with the new decal prop fix script which will do the rest.
These determine the color and material properties of your decal.
Example diffuse texture for a mud decal.
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 a mud decal.
If you don't import an alpha map, it will default to white - fully visible.
Decals created using the Decal Prop Fix mod do not support color variations.
Allows for diffuse contribution illumination. Black means no illumination and white means the brightest possible illumination. For decals the illumination is not very noticeable.
If you don't import an illumination map, it will default to no illumination.
Example specular map for a mud decal.
Transitions between different specular values produce artifacts on the normal map and vice versa, even if a normal map is not imported.
If you don't import a specular map, it will default to no specularity.
The normal map only affects the reflective parts of decals, therefore it's often not useful.
Read more about normal maps in the prop asset creation 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.
All imported main textures must be the same resolution.
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.
The mesh can have any name.
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, meshname_a.png etc.
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 doesn't matter, as the script will change all the relevant values.
Importing the mesh in asset importer.
The result will be instantly visible and it's fine to run the script multiple times.
If you load a decal in the asset editor, it will not show up correctly.
At the top of the script you can change some variables.
This defines the width and length of your decal in meters, the texture width and height will be stretched to match this size.
This allows to tile the texture multiple times in width and length directions. This is usually left at 1.
This defines the height of the decal box mesh, which determines the amount of sloped terrain the decal will be able to handle, once the terrain slope exceeds this value, the decal will begin fading out at the top and bottom.
When the camera enters the decal box mesh, the decal will not be visible.
If you leave this as a negative value, the script will automatically calculate a reasonable value.
ModTools scene explorer and console.
- UIPriority (determines item order in menu) - Asset UI Priority Changer by Snow_Cat or script
It's recommended to pick a high number, use the first few numbers as a "signature" and only change the last few numbers of it for each item like here.
Prop variations menu in the asset editor.
Save asset window.
The asset name visible ingame, the name people should search for.
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