1,784
edits
Changes
Jump to navigation
Jump to search
→Cargo system
* '''cargo_loading_methods[]''' - array of tokens representing supported cargo [loading methods|#Loading-Methods] by this body
* '''cargo_regular_width''' - float representing at which width extension parts for the trailer are switched on
* '''cargo_warning_signs''' - bool value indicating whether body should have warning signs part switching supported or not, see [more|#Warning signs]
* '''cargo_areas''' - array of area sizes (X,Z) that are used for any of area based loading method
* '''cargo_areas_cylinder_data[]''' - array aligned with cargo areas, storing additional data for cylinder based loading (each item representing height, slope angle for given cargo area)
* '''dimensions''' - float3 representing dimensions of the cargo model match in each axis (X,Y,Z). Y component is currently ignored however might be used in the future.
* '''unit_volume_factor''' - float as factor of the cargo unit volume defined in cargo data. This is usually used to distinguish different cargo model matches of the same cargo, that have completely different visual and thus different ratio to the cargo unit volume. Unless you are not defining new cargo model matches for existing cargo nor you have multiple cargo model matches you should not define it
* '''loading_method''' - token of the loading method cargo model match will be using, see [more|[#Loading Cargo loading methods]]* '''lashing_method''' - token of the lashing method cargo model match will be using, see [more|[#Lashing Cargo lashing methods]]* '''lashing_gear_type''' - token of the lashing device cargo model match will be using, see [more|[#Lashing Cargo lashing gear types]]
* '''lashing_hook_angle_constraints''' - float3 defining angle constraint on each axis of the hook in range between 0 and 90° (this will work similarly as angle constriants on body lashing mounts except that his is applied only when <code>direct</code> lashing is used for the cargo model match)
For '''''top_over''''' lashing cargo model requires lashing rail locators with naming: <code>lash_s_Z_X</code> and <code>lash_e_Z_X</code> where <code>Z</code> donates index of multiple rails along model forward axis and <code>X</code> donates index of multiple rails along model X axis. Multiple rails are usually used when there is some obstruction in the model and you need manual dividing into multiple railing (e.g. some separation elements). In all other cases one should use single Z rail indexing since the game will place multiple lashings on the distance of 1.25m from each other. X indexing should be done from left to the right (from -X to +X in model space)
==== Cargo lashing gear types ====
TBA
=== Traffic trailer data ===
