309
edits
Changes
Jump to navigation
Jump to search
First draft of pin overrides section
|array<string>
|
|Two '''info''' members are typically defined for '''accessory_truck_data''':
<syntaxhighlight lang="cpp">
info[]: "@@brand_peterbilt@@" // The truck brand
|array<string>
|
|Each member contains a specially-formatted string which defines an accessory type (token) and the relative path to an SII file with a safe fallback accessory defined. So a fallback rule for <code>chassis</code> may look like <code>fallback[]: "chassis<nowiki>|</nowiki>4x2.sii"</code> which would call on ''/def/vehicle/truck/<brandmake.model>/chassis/4x2.sii'' if there is ever a problem with the vehicle's currently assigned chassis accessory that makes it invalid or unloadable.
Accessories in the accessory folder are handled differentlysomewhat specially. For example, a rule for <code>steering_w</code> looks like <code>fallback[]: "accessory<nowiki>|</nowiki>steering_w/shape1.sii"</code>.
{{Note|There is 8 mandatory are 15 ''required'' fallback rules: chassis, cabin, interior, engine, transmission, f_wheel (or f_tire), r_wheel (or f_disc, f_hub, f_nuts, r_tire), r_disc, r_hub, r_nuts, head_light, paint_job and head_light, interior. It is generally advisable to include a rule for steering_w if the truck has interchangeable steering wheels.}}
|}
=== Pin Overrides ''(Added in 1.40)'' ===
The following array attributes are used to override the location, appearance, and orientation of accessory pins in the truck configuration scene. Their usage is the same as the identically named attributes in the ui_truck_scene_config unit, such that one member of each array is used to override the behavior of each pin. Pin overrides defined in accessory_truck_data will supersede the data in ui_truck_scene_config for the associated truck.
{|class="wikitable"
!Name
![[Documentation/Engine/Units#Attribute_types|Type]]
!Description
|-
|pin_group
|array<token>
|The name of the accessory group for each pin override
|-
|pin_look
|array<token>
|The appearance of the accessory pin to use – typically <code>custom_acc</code>
|-
|pin_offset
|array<float3>
|Vector to offset the accessory pin from the locator
|-
|pin_dir
|array<float3>
|Vector to set the direction of the pin (independent of locator orientation)
|-
|pin_dir_uk
|array<float3>
|Vector to set the direction of the pin for right-hand drive (independent of locator orientation). This attribute is typically omitted in ATS.
|-
|double_sided
|array<bool>
|When true, the pin will be duplicated and mirrored across the truck's X-axis.
|}
In this first example, the pin for the ''sideskirt'' accessory is offset 1 m to the left of the locator (-X), and pointed to the left as well (-X). It will also be drawn 1 m to the right of the locator, pointed to the right.
<pre> pin_group[]: sideskirt
pin_look[]: custom_acc
pin_offset[]: (-1, 0, 0)
pin_dir[]: (-1, 0, 0)
pin_dir_uk[]: (-1, 0, 0)
double_sided[]: true</pre>
In this example, the pin for the ''exhaust'' accessory will be drawn at the locator (no offset), and will be pointed 45° to the rear left of the truck. It will also be drawn 45° to the rear right of the truck. This has the effect of making the pin completely visible from both sides and the rear of the vehicle.
<pre> pin_group[]: exhaust
pin_look[]: custom_acc
pin_offset[]: (0, 0, 0)
pin_dir[]: (-1, 0, 1)
pin_dir_uk[]: (-1, 0, 1)
double_sided[]: true</pre>
