Mod Troubleshooting

Sometimes, technical problems occur when mods are used. Here are some common problems and potential solutions.

While the possibilities are numerous, it is not recommended to try to use all mods at once. Every additional model requires some disk space and increases the RAM usage ingame once used. Additional scripts may need some additional computation time. Thus it may be possible that slower computers tend to be overwhelmed when using hundreds of mods.

If you encountered serious slowdowns directly after adding a certain mod, try to play the game without it again. If this is the case it is likely that the mod has some negative performance side effects.

Especially when mods are used, in rare cases game crash may occur. There are different possible reasons for the crash related to mods. Likely are:

• A mod has some errors in itself
• A mod uses some (script) resources of the game that were removed with an update
• A mod does not adhere to the assumed standard and after an update of the problem errors now occur
• Some mods have mutual side effects

In any case the search for the cause can be cumbersome. Usually the error message gives a hint to where the error occured and what the problem might be. Maybe a similar problem was described earlier in some discussion in one of the communities? If you recently had an update of the game or the mod you might try to revert to an older version if available.

See below for information on how to get further assistance in case of crashes.

Sometimes mods that were previously installed can't be found by the game anymore. Then the savegame can't be loaded and the missing entry is marked with a red triangle. In case of Steam Workshop mods, just click the icon to open the corresponding Workshop pages of the mods. Check if they still are where they should be. If they are not, try to reinstall them by either unsubscribing and subscribing again in the Steam Workshop or by manually downloading them again. In some cases it is possible to replace a missing Workshop mod with a manually installed version of the mod. If the mod can't be restored anymore, it may be possible to remove it without destroying the savegame.

In any case it is neccessary to deactivate the mod. Do the following steps:

1. To deactivate the missing mod, go to the load dialog in the main menu.
2. Click on SELECT OPTIONS.
3. Deactivate the missing mod with the red triangle by clicking on the green slider.
4. Optionally activate a replace mod by clicking on its gray slider.
5. Press START.

If there is no replacement mod or that mod does not cover all contents of the missing mod, it is likely that some models are replaced by dummy cubes. These behave like static assets or very slow vehicles, depending on the type of model that got replaced. These static cubes can be deleted or vehicle cubes can be replaced by working vehicles in the vehicle manager.

There are various reasons why some contents do not show up in the game although the mods are installed and activated.

• Some mods use resources from other mods. This other mod is then called dependency. Ensure that all required dependencies are installed and activated in game.
• Some mods have mod settings which may hide some content. Read the description of the mod (ingame and at the download location) and check if this happens here.
• Some mods alter the availability dates of models. Maybe some other mod changes the availability of the missing models?
• If some resources can't be found or contain errors, e.g. due to a spelling mistake in code, models are filtered by the game. If models are filtered, this can be seen in the stdout.txt. Usually the cause for filtering is written there too.

Already existing instances of the filtered models are replaces by dummy cubes too. An entry in the stdout looks like

WARNING: The following models were removed because they reference an invalid resource:
 * [...].mdl was removed because the following resources were missing:
 - res/models/mesh/[...].msh
...
The following models are missing and will be replaced:
 * building/[...].mdl 1513
 * building/[...].mdl 1514
 * building/[...].mdl 1515

If you struggle to solve the problem yourself, you may ask somebody else for assistance. Usually it is helpful to provide as many details as possible. These details may be:

• Screenshots which show the problem and screenshots which show the mod folder and its relevant content
• The stdout.txt logfile (can be found in userdata/.../crash_dump) containing error messages and other valuable information for finding the cause of the problem.
• Any error message that was displayed by the game
• If the problem might be hardware related, some basic hardware specs (CPU model, Graphic card model and RAM size)
• Steps you have taken so far to solve the problem

See the general troubleshooting section to find out where to get further assistance.