1,740
edits
Changes
Created page with "= Recommendations = <ul> <li> Some new models utilizing the "sc" suffix or prefix are still work in progress and it is likely that they might change significantly in some next..."
= Recommendations =
<ul>
<li> Some new models utilizing the "sc" suffix or prefix are still work in progress and it is likely that they might change significantly in some next patch. For this reason it is recommended that you avoid using them in your mods at this time.
</li> <li> When basing you model on the original ones, add to your mod also <strong>ALL</strong> original /automat/ files used by it. The names of the files are generated as SHA1 hash of theirs content so whenever we change the parameters of the material in any way, a different file will be used to store them and the original file might cease to exist if there is no other model utilizing the original parameters.
</li> <li> When modifying original models, always include <strong>ALL</strong> compoments of the model (pmg+pmd) instead of just those you changed. Otherwise you risk crash if we change the model.
</li> <li> As always when adding new objects to files which support multi-file approach (e.g. road_look.sii) it is <strong>HIGHLY RECOMMENDED</strong> to use suffix or prefix in the name to avoid conflicts with new objects we are adding in patches. Otherwise you might have to use the batch renaming functionality (see Batch renaming) to fix the conflicts when new patch appears.
</li>
</ul>
= How to convert map =
<ul>
<li> Visit small truck dealers and do the following <ul>
<li> Set proper variant of the prefab model to match the brand it sells.
</li> <li> Set the look to default if it was set to something else previously.
</li> <li> Select prefab, unselect the main node of the prefab (so only signs remain selected) and press delete to delete the existing signs.
</li> <li> Use "Add prefab signs" to add new signs
</li> <li> Select proper model for the prefab-based "Give way" sign based on country or drop the sign entirely if you already using a custom one.
</li> <li> Remove any unwanted signs.
</li> <li> Do any necessary corrections in the surrounding (e.g. grass, terrain, signs)
</li></ul>
</li> <li> Save map
</li> <li> Do rebuild (F8)
</li> <li> Save map
</li>
</ul>
= Changes =
== Changes in cargoes ==
The cargo attribute <strong>heavy</strong> was renamed to <strong>valuable</strong> to correspond to its real usage.
== Changes in economy_data ==
The attributes <strong>reward_bonus_heavy</strong> and <strong>exp_heavy_bonus</strong> were renamed to <strong>reward_bonus_valuable</strong> and <strong>exp_valuable_bonus</strong> to correspond to the real usage.
== Changes in city data ==
Optional property <strong>city_name_sort</strong> has been added to <strong>city_data</strong> unit. It is used for sorting cities on various screens instead of city name if defined. It should be used for cities that has non-basic characters in name and basic sorting is not sufficient (eg. Łódź).
== Changes in truck dealer ==
The mechanism used for handling the truck dealers was replaced to allow for bigger number of prepared configurations however it is still limited to one definition file per brand.
The small truck dealer prefab did change. It is now necessary to select the proper variant for the truck branch it represents, regenerate the signs and it might be necessary to do small corrections in its surrounding.
== Changes in animated models ==
While this change did already happen in 1.14, it was not mentioned in its modding info. As part of speed optimizations, the skinning now takes advantage of the knowledge that skinning info in our model format should have the sum of weights of all bones affecting a vertex set to 1.0. If you have model which does not meet this requirement, its vertices will be pulled towards or pushed outwards from the origin of the model depending on the sum.
== Changes in vehicles ==
=== Multiple dashboard colors ===
The luminosity materials on the truck dashboard now support up to 16 different sets of colors. The color slots are defined using dashboard_color array in the interior. The color slot used for part of the geometry is selected using integer part of UV coordinates of the geometry. See new <strong>dashboard_color.sui</strong> in our trucks.
== Changes in trailers ==
The game now respects the trailer model look if one is specified in the trailer definition.
Removed redundant definitions of chemical/fuel cisterns (the company look was always assigned automatically). If you are using one from those removed trailers in your cargoes, you need to update them to point to the base one.
== Changes in editor ==
=== Added experimental bazier patches ===
The editor now supports creation of terrain based on bezier patches. Please note that this is still experimental feature and might change in future versions.
=== Additional optional checks ===
<ul>
<li> <strong>Item connection check</strong> - this check is performed only on 'AI-enabled' roads and prefabs. It checks if there are smooth AI navigation line transitions from one item to another. It generates error messages like "<em>Connection error (Offset: ... Node: ... </em>". <ul>
<li> The <em> <strong>Offset</strong> </em>value is the key in determining what is wrong: <ul>
<li> In case of offsets around <strong>4.5 and larger</strong> (4.5 m is the width of one road lane) it is most often a map bug. It usually means there are two incompatible items connected to each other (for example UK road and non-UK prefab) However, it can also mean that there are some input/output prefab curves incorrectly assigned to nodes.
</li> <li> In case of <strong>smaller offsets</strong>, it is most probably a prefab bug. This usually occurs when input/output prefab locators are not exactly in the center of corresponding road lanes.
</li></ul>
</li></ul>
</li> <li> <strong>Navigation check</strong> - this check is performed only on items which are shown in the map. It checks if it is possible for navigation to compute a route between items. It generates error messages like "<em>Error navigating to prefab at node ... </em>". <ul>
<li> For example, it can be caused by connecting a one-way road to a prefab in the opposite direction (map bug -> to solve it, connect items correctly).
</li> <li> Another example is when there is no prefab navigation curve leading to/from a road where player can drive (prefab bug -> to solve it, add missing curves).
</li></ul>
</li></ul>
<ul>
<li> Some new models utilizing the "sc" suffix or prefix are still work in progress and it is likely that they might change significantly in some next patch. For this reason it is recommended that you avoid using them in your mods at this time.
</li> <li> When basing you model on the original ones, add to your mod also <strong>ALL</strong> original /automat/ files used by it. The names of the files are generated as SHA1 hash of theirs content so whenever we change the parameters of the material in any way, a different file will be used to store them and the original file might cease to exist if there is no other model utilizing the original parameters.
</li> <li> When modifying original models, always include <strong>ALL</strong> compoments of the model (pmg+pmd) instead of just those you changed. Otherwise you risk crash if we change the model.
</li> <li> As always when adding new objects to files which support multi-file approach (e.g. road_look.sii) it is <strong>HIGHLY RECOMMENDED</strong> to use suffix or prefix in the name to avoid conflicts with new objects we are adding in patches. Otherwise you might have to use the batch renaming functionality (see Batch renaming) to fix the conflicts when new patch appears.
</li>
</ul>
= How to convert map =
<ul>
<li> Visit small truck dealers and do the following <ul>
<li> Set proper variant of the prefab model to match the brand it sells.
</li> <li> Set the look to default if it was set to something else previously.
</li> <li> Select prefab, unselect the main node of the prefab (so only signs remain selected) and press delete to delete the existing signs.
</li> <li> Use "Add prefab signs" to add new signs
</li> <li> Select proper model for the prefab-based "Give way" sign based on country or drop the sign entirely if you already using a custom one.
</li> <li> Remove any unwanted signs.
</li> <li> Do any necessary corrections in the surrounding (e.g. grass, terrain, signs)
</li></ul>
</li> <li> Save map
</li> <li> Do rebuild (F8)
</li> <li> Save map
</li>
</ul>
= Changes =
== Changes in cargoes ==
The cargo attribute <strong>heavy</strong> was renamed to <strong>valuable</strong> to correspond to its real usage.
== Changes in economy_data ==
The attributes <strong>reward_bonus_heavy</strong> and <strong>exp_heavy_bonus</strong> were renamed to <strong>reward_bonus_valuable</strong> and <strong>exp_valuable_bonus</strong> to correspond to the real usage.
== Changes in city data ==
Optional property <strong>city_name_sort</strong> has been added to <strong>city_data</strong> unit. It is used for sorting cities on various screens instead of city name if defined. It should be used for cities that has non-basic characters in name and basic sorting is not sufficient (eg. Łódź).
== Changes in truck dealer ==
The mechanism used for handling the truck dealers was replaced to allow for bigger number of prepared configurations however it is still limited to one definition file per brand.
The small truck dealer prefab did change. It is now necessary to select the proper variant for the truck branch it represents, regenerate the signs and it might be necessary to do small corrections in its surrounding.
== Changes in animated models ==
While this change did already happen in 1.14, it was not mentioned in its modding info. As part of speed optimizations, the skinning now takes advantage of the knowledge that skinning info in our model format should have the sum of weights of all bones affecting a vertex set to 1.0. If you have model which does not meet this requirement, its vertices will be pulled towards or pushed outwards from the origin of the model depending on the sum.
== Changes in vehicles ==
=== Multiple dashboard colors ===
The luminosity materials on the truck dashboard now support up to 16 different sets of colors. The color slots are defined using dashboard_color array in the interior. The color slot used for part of the geometry is selected using integer part of UV coordinates of the geometry. See new <strong>dashboard_color.sui</strong> in our trucks.
== Changes in trailers ==
The game now respects the trailer model look if one is specified in the trailer definition.
Removed redundant definitions of chemical/fuel cisterns (the company look was always assigned automatically). If you are using one from those removed trailers in your cargoes, you need to update them to point to the base one.
== Changes in editor ==
=== Added experimental bazier patches ===
The editor now supports creation of terrain based on bezier patches. Please note that this is still experimental feature and might change in future versions.
=== Additional optional checks ===
<ul>
<li> <strong>Item connection check</strong> - this check is performed only on 'AI-enabled' roads and prefabs. It checks if there are smooth AI navigation line transitions from one item to another. It generates error messages like "<em>Connection error (Offset: ... Node: ... </em>". <ul>
<li> The <em> <strong>Offset</strong> </em>value is the key in determining what is wrong: <ul>
<li> In case of offsets around <strong>4.5 and larger</strong> (4.5 m is the width of one road lane) it is most often a map bug. It usually means there are two incompatible items connected to each other (for example UK road and non-UK prefab) However, it can also mean that there are some input/output prefab curves incorrectly assigned to nodes.
</li> <li> In case of <strong>smaller offsets</strong>, it is most probably a prefab bug. This usually occurs when input/output prefab locators are not exactly in the center of corresponding road lanes.
</li></ul>
</li></ul>
</li> <li> <strong>Navigation check</strong> - this check is performed only on items which are shown in the map. It checks if it is possible for navigation to compute a route between items. It generates error messages like "<em>Error navigating to prefab at node ... </em>". <ul>
<li> For example, it can be caused by connecting a one-way road to a prefab in the opposite direction (map bug -> to solve it, connect items correctly).
</li> <li> Another example is when there is no prefab navigation curve leading to/from a road where player can drive (prefab bug -> to solve it, add missing curves).
</li></ul>
</li></ul>