- Some new models utilizing the "fr" 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.
- When basing you model on the original ones, add to your mod also ALL 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.
- When modifying original models, always include ALL compoments of the model (pmg+pmd) instead of just those you changed. Otherwise you risk crash if we change the model.
- As always when adding new objects to files which support multi-file approach (e.g. road_look.sii) it is HIGHLY RECOMMENDED 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.
How to convert map
- Load map
- Do rebuild (F8)
- Save map
Interior data unit names
Unit names of interiors of most ETS truck was renamed to fix various issues with searching and matching. Naming conventions of all truck-based accessories has to be accessory_name.truck_brand.truck_series.accessory_type. All mods that linked accessories to unit names in any way (eg. by dependency rules - suitable_for, conflict_with, default) have to be updated.
Engine simulation has been made heavily data driven. For this purpose there can be defined torque curve and various rpm limits in accessory_engine_data files. Torque curve is defined as list of torque ratios based on rpm, with values between 0-1 and border values valid to +/-infinity rpm. Idle and limits define rpm points where truck electronics do some alteration (lowering throttle behind limits, adding throttle below idle). Rpm ranges define preferred rpm and are used by automatic transmission of any kind. Low- and high_gear define basic range (by gear) while power boost defines rpm power reserve for hills or adaptive behavior. All these values must fit to torque characteristic of engine to work correctly.
torque_curve: (300, 0) torque_curve: (440, 0.5) torque_curve: (1000, 1) torque_curve: (1300, 1) torque_curve: (1900, 0.77) torque_curve: (2400, 0.4) torque_curve: (2600, 0) rpm_idle: 550 rpm_limit: 2500 rpm_limit_neutral: 2500 rpm_range_low_gear: (700, 1500) rpm_range_high_gear: (1000, 1500) rpm_range_engine_brake: (1500, 2500) rpm_range_power_boost: (550, 450)
From accessory_chassis_data files has be removed attribute powered_wheel and replaced by powered_axle. It work in same way as other axle-based attributes now (residual_travel, kerb_weight, liftable_axle, ...).
Added torque_converter_viscosity_factor and torque_converter_locked_viscosity_factor for torque converter-based transmissions. Added manual_clutch_viscosity_factor and manual_clutch_connected_viscosity_factor for better manual clutch slipping simulation.
All damage data was removed from game_data.sii and set into new damage_data.sii file. Many new attributes have been added.
Basic damage coefs and damage transfer ratio between truck and trailer. Additional damage factors are used for overthrown truck.
- truck_damage_coef: 0.0007
- trailer_damage_coef: 0.0007
- dragged_trailer_damage_coef: 0.00002
- truck_to_trailer_dmg: 0.2
- side_damage_factor: 6.0
- roof_damage_factor: 11.0
Damage distribution to truck parts on hit.
- cabin_damage_ratio: 0.8
- chassis_damage_ratio: 1.0
- engine_damage_ratio: 0.5
- transmission_damage_ratio: 0.3
- wheel_damage_ratio: 0.15
Wear distribution to truck parts on regular usage (per km).
- cabin_wear: 0.0
- chassis_wear: 0.0
- engine_wear: 2e-6
- transmission_wear: 2e-6
- wheel_wear: 2e-5
Traffic vehicle types vs. traffic lane data
Traffic lane data attribute allowed_vehicle_type (defined per-lane-type in traffic_lane.sii) is now obsolete. Instead, please use attribute allowed_lane_type (defined per-vehicle-type in traffic_vehicle_type.sii). The new attribute is an array of strings, which define at which lanes which vehicle types are allowed. At least one of the strings in the array must match the traffic lane unit name (traffic_lane.sii) for the vehicle type to be allowed to drive there. Wildcards * and ? are supported.