507
edits
Changes
Jump to navigation
Jump to search
* If your mod adds Estonia, Latvia, Lithuania, Russia or Finland update your country, ferry, semaphore model and semaphore profile definitions to avoid conflicts.
TBA=== Curve model definition === Every single definition in the '''curve_model.sii''' file must be in the following format: <pre> ---------- Internal Data Type | | ------ Data Type Identification | | | | ----- User Name | | | v v vcurve_model : curve.2 { category: "Walls" # Category name: "Warehouse wall" # Curve model name model_desc: "/model/warehouse/tiled_wall.pmd" # Model Path dynamic_lod_desc[]: "/model/warehouse/tiled_wall_lod1.pmd" # LOD1 Model Path dynamic_lod_dist[]: 50 # LOD1 switch distance in meters dynamic_lod_desc[]: "/model/warehouse/tiled_wall_lod2.pmd" # LOD2 Model Path dynamic_lod_dist[]: 100 # LOD2 switch distance in meters variation[]: "var_name1 | center1:2 | center2:5" # Part variation definition variation[]: "var_name2 | center1, mapcenter2:5" start_part[]: "strt1|strt1a" # Start parts list per variation start_part[]: "strt2|strt2b" end_part[]: "end1" # End parts list per variation end_part[]: "end2|end3|end4" smooth_surface: false # Smooth surface color_variant[]: "red: 255, 0, 0" # Color variants color_variant[]: "blue: 0, 0, 255" vegetation[]: "tree_a : vegetmodel.cityalley.smalltree02a | 5:8 | -2:2 | 0.5:1.5 | 0:360" vegetation[]: "tree_b : vegetmodel.cityalley.smalltree02b | 5:8 | -2:2 | 0.5:1.5 | 0:360" fixed_step: 20 # Use given fixed step between parts fixed_inner_start[]: strt1 # Use given start part for "inner" curve (definition per variation) fixed_inner_start[]: strt2 fixed_inner_end[]: end1 # Use given end part for "inner" curve (definition per variation) fixed_inner_end[]: end2}</pre> * '''Internal Data Type, Data Type Identification''' - must stay intact and are obligatory.* '''User Name''' - must be UNIQUE for every single railing in the game (even across all dlcs, mods etc.). This name is token and can have up to 12 characters from the following set:_0123456789abcdefghijklmnopqrstuvwxyz. The best practice is to add some suffix to the name identifying the dlc or mod to avoid name conflicts.* '''Category''' - Category name used for navigation simplification in building item properties dialog. String value.* '''Name''' - Building scheme name. String value.* '''Model Path''' - Path to the model file (*.pmd).* Maximum Dynamic LOD count is 3* '''LOD Model Path''' - Path to the model file used for the low poly LOD (*.pmd).* '''Variation''' - Center part variation definition** <pre>Variation name (token) | part_name [,part_name ...] : weight [ | part_name [,part_name ...] : weight]</pre>* '''Start part''' - Array of all valid parts which can be used as the start* '''End part''' - Array of all valid parts which can be used as the end* '''Smooth surface''' - Perform smooth interpolation of the geometry normals. Default value: false* '''Color variants''' - User defined vertex color multiplication factor used during buildings item geometry generation (optional)* '''Vegetation''' - Instanced vegetation definition has following format:** <pre>Instance name (token) : vegetation model unit name | min_width : max_width | min_offset : max_offset | min_scale : max_scale | min_rot : max_rot</pre> === Automatic wire generation === The curve model can contain locators for automatic wire generation. These locators have the following naming convention: Locator name: '''w_X_Y_Z''' where: * '''w_''' - prefix* '''X''' - wire type** '''f''' - flat wire without any drop distance** '''t''' - LOW wire drop, with flat wire thickness (thin wire)** '''l''' - LOW wire drop** '''m''' - MEDIUM wire drop** '''h''' - HIGH wire drop* '''Y''' - wire line index 0 based* '''Z''' - unique suffix suffix can be any character Examples: <pre>w_h_0_a, w_h_0_b, w_f_1_0</pre>
For details see [[Documentation/Engine/Mover_model_group|Mover documentation]].== Voice navigation ==
== AI changes ==Data format for voice navigation feature is described at [[Documentation/Engine/Units/sound_data_voice_navigation]].
TBA== Dynamic LODs ==
== Dynamic lods ==Instead of single static LOD (attributes '''lod_desc''' and '''lod_dist''') there is now array of LODs (arrays '''dynamic_lod_desc[]''' and '''dynamic_lod_dist[]''').Logic is the same: ''descriptor'' defines path to LOD model, ''dist'' defines distance from where it should be used. For now old LODs definition are loaded and converted, but this support might be removed in future updates, eventually.
use dynamic_lod_desc[] instead of lod_descAffected units are '''prefab_model''', '''model_def''' and '''curve_model'''.Also '''sign_model''' newly has LOD array.
TBA== Timezone sub-areas ==
== Modded trucks support ==Data for time zone sub-areas has been introduced silently in 1.34 update (look for Malheur county, Oregon in ATS or Kaliningrad area, Russia in ETS).
For a brand/truck to show up correctly in the Mod Truck Dealer screen, the following conditions must be met:* The truck's One set of data is located in '''/def/vehicle/truck/<brand>.<model>/city_data'''units and data is used for static city-based zone usage (eg.delivery times in game economy):* The truck's unit name in its '''data.siitime_zone''' (integer, default is correctly formatted as '''vehicle.<brand>.<model>'''.undefined value, represented by week of time, 10080) - time zone of given city in minutes* The truck's dealer definition is located in ''time_zone_name'/def/vehicle/truck_dealer/<brand>/'''.(string, default empty) - name of eventual time zone* The '''<brand>''' token must match for all If city time zone is undefined (or 10080) then there is used time zone of thesecountry the city belongs to.
The brandSecond set of additional data consists of three synchronized arrays (same length expected) stored in '''country_data''' units and is used for spatial detection of time zone on map:* '''secondary_time_zone_area''' (float4 array) - elements of rectangle areas in editor coordinates* '''secondary_time_zone''s icon ' (integer array) - time delta of given area in minutes* '''secondary_time_zone_name''' (string array) - name of time zone in given areaIf point is in given country (decided by map logic by road/prefabs & borders) then all existing rectangle elements are checked for different time zone than country has. First matching area element defines the dealer will be proper time zone. If no area is found, country time zone is used instead. == Economy data == New attributes in '''economy_data'/material/ui/truck_brand_logo/<brand>'' unit that handle emergency refueling:* '''refuel_fuel''' - amount of fuel delivered on single emergency refuel (default 50.0, in litres), service is disabled if driver has more fuel* '''refuel_price_base''' - base flat price of the service (default 150.0)* '''refuel_price_factor''' - base fuel cost multiplier compared to regular diesel price in given country (default 3.mat0)* '''refuel_time_base'''- base time of emergency refueling delay (default 1800.0, in seconds) == Traffic data == === Parked vehicles/trailers ===
== COG data in Parked vehicle/trailer attribute '''accessory_chassis_dataallowed_trailer''' ==is now also interpreted as a trailer chain definition.
4 point simulation (locatorAllows all the modded truck brands to be available on one specific UI screen. You have access to this feature after you activate a mod in the Mod Manager that contains a defined truck brand. When a mod like this is detected, obsolete/new values in physicsa button on the truck dealer world map that will direct you to the this screen.sii)TBA
== Wheel offsets ?? ==To add a new brand on you mod simply create a directory with the name of your brand in '''/def/vehicle/truck_dealer'''. In this directory you will put your stock truck offer .sii files. For example, for a brand named '''X Brand''', create a directory named "'''xbrand'''" on the mentioned path. Now this directory needs to be populated with valid truck offers, .sii files that contain a vehicle and its accessories. Those accessories and vehicle configurations definitions are stored in a directory in the path '''/def/vehicle/truck'''. For more information on this folder's structure and contents, see the dedicated page: [[Documentation/Engine/Game_data/Player_trucks_definitions|Player trucks definitions]].
??It is important to mention if you are creating a new truck definition, the unit [[Documentation/Engine/Units/accessory_truck_data|accessory_truck_data]] should be named using the following convention <code>vehicle.<brand>.<series></code>. So using the example above, if the '''X Brand''''s offers use a new truck definition, the name of the accessory_truck_data in the <code>data.sii</code> should look like this:<code>accessory_truck_data : vehicle.xbrand.t_9000</code>
== Wipers duration+delay format =={{Note|At the moment, the UK only truck brands defined in '''/def/vehicle/truck_dealer_uk''' are not supported by this feature.}}
In unit [[DocumentationAdditionally, you can add a brand logo to your own brand dealer on the '''/Enginematerial/Unitsui/accessory interior data|brand_logo'''accessory_interior_datadirectory. To achieve this, create a .mat, a .tobj and a .tga logo files with the name of your new brand (aka "''']] attribute xbrand'''wiper_delay''' has been removed" here). Using the provided [[Documentation/Tools/Conversion_Tools#Download_. Instead, 26_Installation|conversion tools]] convert these files and add the resulting conversions to the new attribute aforementioned directory. The logo size has to be '''wiper_duration_and_delay128x64''' (array of float2) has been added. Each element contains animation length (If no brand logo is set, in seconds) and time delay between animation loops (in seconds) of one active stateits place there will be an empty material image.
If no Finally, you can still add modded trucks to the in-game dealers using the same procedure of creating a directory with that said in-game's brand name in the '''wiper_duration_and_delay/def/vehicle/truck_dealer''' is correctly stated path and populating it is defaulted with new offers. So if a modder wanted to single element float2(2.0add new offers to DAF for example, 0they would have to create a directory named "'''daf'''" in the truck_dealer path of their mod and add their truck offers there.0), which serves as single active state All modded content to the in-game brands will be available in such caseboth the modding and the actual brand dealers.
If there are stated more than one model of cargo visualization (see Unit '''data_pathaccessory_transmission_data''' array in has two new string attributes - '''cargo_model_matchauto_mode_name''' unit, stored in (default "A") and '''def/cargo/*/manual_mode_name''' folders of cargoes for owned trailers(default "M") for given trailer. Their value is used in dashboard computer display as transmission mode element (id 1310) if truck display contains one. === Wheel collision offsets improved === Previously, the one wheel collision representation used is chosen pseudoa hard-randomly from themcoded offset and width, and thus did not always match precisely the visuals. Most wheels should now have their collisions matched by default.
== Timezone sub-areas ==The only wheels requiring special treatment are those with a nonzero offset of the 'middle' of the tire from zero (this may arise for multiple reasons, e.g. for allowing baked (not tire + rim) wheelsto rotate as intended, or for making tires with multiple widths compatible with a single rim/disc accessory).
Data for time zone sub-areas has been introduced silently For such wheels, there is a new parameter in 1<code>accessory_wheel_data</code> called '''wheel_shift'''.34 update (look This shift should amount to the difference between the zero of the scene and the zero of the tyre for Malheur county, Oregon in ATS or Kaliningrad area, Russia in ETS)the collisions to be generated correctly.
One set of data is in '''city_data''' units and data is used {{Note| Another ingredient needed for static city-based zone usage (eg. delivery times in game economy):* '''time_zone''' (integer, default the collisions to work as intended is undefined value, represented by week of time, 10080) - time zone of given city in minutes* '''time_zone_name''' (string, default empty) - name of eventual time zoneIf city time zone ensuring the BB locator is undefined (or 10080) then there is used time zone positioned at the outer edge of country the city belongs totire.}}
Second set of additional data consists of three synchronized arrays (same length expected) stored in '''country_data''' units and is used for spatial detection of time zone on map:* '''secondary_time_zone_area''' (float4 array) - elements of rectangle areas in editor coordinates* '''secondary_time_zone''' (integer array) - time delta of given area in minutes* '''secondary_time_zone_name''' (string array) - name of time zone in given areaIf point is in given country (decided by map logic by road/prefabs === Wipers duration & borders) then all existing rectangle elements are checked for different time zone than country has. First matching area element defines the proper time zone. If no area is found, country time zone is used instead.delay format ===
== Transmission mode names ==In unit [[Documentation/Engine/Units/accessory interior data|'''accessory_interior_data''']] attribute '''wiper_delay''' has been removed. Instead, the new attribute '''wiper_duration_and_delay''' (array of float2) has been added. Each element contains animation length (in seconds) and time delay between animation loops (in seconds) of one active state.
Unit If no '''accessory_transmission_datawiper_duration_and_delay''' has two new string attributes - '''auto_mode_name''' (default "A") and '''manual_mode_name''' (default "M"). Their value is used in dashboard computer display as transmission mode correctly stated it is defaulted to single element float2(id 13102.0, 0.0) if truck display contains one, which serves as single active state in such case.
→Voice navigation
= How to convert map =
* Load map
* Do rebuild (F8)
* Save map
* Select correct looks for models where the selection of the looks changed
* If the save generated error messages of type "Sign template item 123 does not exist in template 'ABC'"
** Find the template in the content browser
** Right click on it and select "Edit"
** In the "Sign Editor" dialog choose File > Clean up overrides
= Changes & New Features =
== Curve items ==
== Mover/walker unification and improvement ==
Approach to movers and similar object has been completely reworked. '''Walker item''' is now obsolete and it is possible that it will be removed in the future. For the similar functionality use '''mover item''' with [[Documentation/Engine/Mover_model_group|mover model group]]. Mover item now supports all important properties from the walker item. Moverover <code>mover_model_u</code> property <code>model_anim_alt</code> is also now obsolete and it '''will be removed''' in the next update. It means that '''pedestrian hookups''' using this property won't work correctly. Recommended approach is to replace them by new mover hookups with [[Documentation/Engine/Mover_model_group|mover model group]] models.
{{Note|Attribute '''allowed_trailer_count''' is now obsolete, since the trailer count is determined from trailer chain automatically.}} === Spawn density rules === Trailer chain support has been added also to ''spawn density'' traffic rules (''traffic_rules_spawn.sui''). All items beyond the first one in the '''str_params''' attribute are now interpreted as allowed trailer chains. This can be useful for specifying areas in map where custom trailers (custom cargo) are spawned. Example: <pre>traffic_rule_data : traffic_rule.s_train_c2{ name: "Spawn density - cargo train (plane)" rule: "density" str_params[]: "train_cargo" str_params[]: "train_car.trplane_car 1 | train_car.trplane_care 1 | train_car.trplane_car 1 | train_car.trplane_care 1 | train_car.trplane_car 1 | train_car.trplane_care 1" num_params[]: 0.0 # 00:00 num_params[]: 0.015 # frequency num_params[]: 1 # count limit}</pre> === Trailer chains === Supported trailers are now defined at one place: ''in '''traffic_vehicle''' by defining the whole trailer chain'' (previously it was combination of per vehicle/trailer type + per vehicle/trailer)Related attributes in '''traffic_trailer''', '''traffic_vehicle_type''' and '''traffic_trailer_type''' are now obsolete. Partial backward compatibility is provided (more complex trailer configurations may not be created correctly using old attributes) {{Note|Support for wildcards has been removed to avoid the unnecessary complexity.}}{{Tip|If you have used (now obsolete) attribute '''allowed_tractor''', the similar functionality can be achieved by setting '''spawn_ratio: 0.0''' for trailers which have been using it. This way, they won't be chosen for any vehicle unless explicitly set in '''trailer_chains'''.}} Each trailer chain element can be specified either by trailer type name (a random trailer model of that type will be spawned)or directly by traffic trailer unit name. Optionally, for each element, the minimum and maximum count of occurrence can be specified. Elements and counts are separated by '|'. '''Examples:''' <code>trailer_chains[]: "semi_trailer"</code> - the vehicle will have one trailer of type '''semi_trailer''' <code>trailer_chains[]: "traffic_trailer.first | traffic_trailer.middle 2-4 | traffic_trailer.last"</code> - trailer chain with specific elements, 'traffic_trailer.middle' can occur 2-4 times. === Trailer type and storage renaming === Some trailer types and corresponding storages have been renamed by using a more universal ''special'' suffix to better match their usage. They contain trailers which are always selected explicitly, never randomly across the whole storage: * ''traffic_storage_train_car_pass.sii'' → ''traffic_storage_train_car_special.sii''* ''traffic_storage_trailer_parked.sii'' → ''traffic_storage_trailer_special.sii'' == Vehicles data == === Cabin suspension === The cabin is newly connected to the chassis by 4 springs as in real trucks (previously, only one spring was used to simulate the cabin behavior).The spring locations can be seen as yellow crosses when g_colbox is active. The data members in <code>physics.sii</code> '''cabin_pitch_force_scaling_factor''', '''cabin_pitch_damping_factor''', '''cabin_roll_force_scaling_factor''' and '''cabin_roll_damping_factor''' are now obsolete. There are new data members in <code>physics.sii</code>: * '''cabin_suspension_travel''' (float, default 0.05, in meters) - specifies the length of the cabin springs when at rest position with cabin weight on them* '''cabin_suspension_damping_factor''' (float, default 1.0) - relative strength multiplier of the cabin suspension damper* '''cabin_sway_bar_factor''' (float, default 1.0) - relative strength multiplier of the cabin suspension sway bar (which counters relative roll of the cabin)* '''cabin_cog_height_offset''' (float, default 0.5, in meters) - specifies the height difference between the cabin locator and the COG of the cabin (the COG is higher than the locator) {{Note|In addition, the working point of the cabin suspension may be altered with the g_cabin_suspension_stiffness cvar. Its default value (1.0) corresponds to working point at 0.65 (the spring compresses to 65 percent of its length when we put the cabin weight on it). Lower values of the cvar means lower working point, and thus softer springs (g_cabin_suspension_stiffness 0.0 puts the working point at 0.5).}} === Cargo model randomized === If there are stated more than one model of cargo visualization (see '''data_path''' array in '''cargo_model_match''' unit, stored in '''def/cargo/*/''' folders of cargoes for owned trailers) for given trailer, the one used is chosen pseudo-randomly from them. === COG data in chassis accessory === Center of gravity (COG) data has been moved from trailer definition to [[Documentation/Engine/Units/accessory_chassis_data|chassis dataaccessory_chassis_data]]. They are easier to edit, they have less count than trailer definitions and on given chassis cargo is typically loaded in same way.
Value logic itself work as before: '''cog_cargo_mass_min''' (float, default 0) and '''cog_cargo_mass_max''' (float, default 20000) sets border limits and '''cog_cargo_offset_min''' (float3, default (0,0,0)) and '''cog_cargo_offset_max''' (float3, default (0,1,0)) set values for interpolation.
In addition, default COG is now in center of model based on some trailer geometry analysis regardless of trailer model scene origin. So the longitudinal offset used as workaround should be discarded.
== Cabin suspension = Trailer chassis adjustment data === In unit '''trailer_configuration''' (folders '''def/trailer_owned/*/configurations/''') is new token '''equivalency''' (empty by default).Each non-empty value defines closed set of configurations. Any other configuration with same '''equivalency''' token value is considered as different variant of same trailer(s). By pure logic they should have same cost and level (but its not cross-checked nor forced by game) and any such switch made via trailer adjuster is free. === Dealer UI for modded trucks ===
=== Trailer braces sound ===
Default value is now set empty. So there is sound only if data explicitly state it.
== Cargo model randomized = Transmission mode names ===
