515
edits
Changes
→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 ==
Examples: <pre>w_h_0_a, w_h_0_b, w_f_1_0</pre> == 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. == Voice navigation == Data format for voice navigation feature is described at [[Documentation/Engine/Units/sound_data_voice_navigation]]. == 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. Affected units are '''prefab_model''', '''model_def''' and '''curve_model'''.Also '''sign_model''' newly has LOD array. == Timezone sub-areas == 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). One set of data is in '''city_data''' units and data is used for static city-based zone usage (eg. delivery times in game economy):* '''time_zone''' (integer, default 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 is undefined (or 10080) then there is used time zone of country the city belongs to. 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 & 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. == Economy data == New attributes in '''economy_data''' 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.0)* '''refuel_time_base''' - base time of emergency refueling delay (default 1800.0, in seconds) == Traffic data == === Parked vehicles/trailers === Parked vehicle/trailer attribute '''allowed_trailer''' is now also interpreted as a trailer chain definition. {{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 chassis data[[Documentation/Engine/Units/accessory_chassis_data|accessory_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 === Allows 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, a button on the truck dealer world map that will direct you to the this screen.
=== 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 === Unit '''accessory_transmission_data''' 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 element (id 1310) if truck display contains one. === Wheel collision offsets improved ===
If no '''wiper_duration_and_delay''' is correctly stated it is defaulted to single element float2(already silently introduced ??2.0, 0.0), which serves as single active state in such case.