507
edits
Changes
Jump to navigation
Jump to search
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>
→Voice navigation
== Curve items ==
== Mover/walker unification and improvement ==
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 ==
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 the <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).}}
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 ===
Previously, the wheel collision representation used a hard-coded offset and width, and thus did not always match precisely the visuals. Most wheels should now have their collisions matched by default.
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) wheels
to rotate as intended, or for making tires with multiple widths compatible with a single rim/disc accessory).
For such wheels, there is a new parameter in <code>accessory_wheel_data</code> called '''wheel_shift'''. This shift should amount to the difference between the zero of the scene and the zero of the tyre for the collisions to be generated correctly.
{{Note| Another ingredient needed for the collisions to work as intended is ensuring the BB locator is positioned at the outer edge of the tire.}}
=== Wipers duration & delay format ===
