War Thunder Wiki - User contributions [en]

User:U100138

2021-04-06T10:53:57Z

U100138: Replaced content with "(*´・ω・)/`"

(*´・ω・)/`

User:U100138

2021-04-06T10:51:06Z

U100138:

The default sighting reticle for ground vehicles in War Thunder can be replaced with a custom one, for example if you want to recreate a historical representation of the sight.

Custom sights will be created by changing settings in the reticle file rather than in any graphic editor.

{{Notice
|Note! The custom sight does not guarantee the accuracy or correct aiming if it has been created by an author without taking into account all the recommendations in this article.
|!
}}

The ability to create user-made sight grid designs for ground vehicles was added in update [[Update_1.73_"Vive_la_France"|1.73 "Vive la France"]].

__TOC__

== How to setup a user-made sight ==

* Place and select the ground vehicle for which you want to replace the sighting reticle into the hangar.
* Open <code>game settings → Main parameters → Common battle settings</code> and for the parameter “Use alternative sight grid” select “Add grid sight”.
* Two sub folders will be created In the UserSights folder which is located in the game directory:
** A folder with the name of the selected vehicle containing the file ‘sight_1.blk’ (this is a template for the default sight)
** A folder with the name “all_tanks”
* Without closing the game client, copy the custom reticle into the created vehicle name folder if you want to apply the new reticle only to it. Or if the reticle is suitable for several vehicles, copy the file to the “all_tanks” folder.
* Return to the game, press Alt + F9 to update game data and select the uploaded reticle..

The number of different sight reticles per vehicle is not limited. So you can create any number of different reticles in one folder and be able to switch between them.

== How to create a user-made sight ==
The sighting reticle is a block of settings of elements: scales, lines, moving parts and text. The settings are set as one .blk file that can be edited using any text editor.

=== Creating a reticle template for a single vehicle ===

* Place the ground vehicle for which you want to replace the sighting reticle into the hangar.
* Open <code>game settings → Main parameters → Common battle settings</code> and for the parameter “Use alternative sight grid” select “Add grid sight”.
* Two sub folders will be created In the UserSights folder which is located in the game directory:
** A folder with the name of the selected vehicle containing the file ‘sight_1.blk’ (this is a template for the default sight)
** A folder with the name “all_tanks”
* Edit this particular .blk fily using any text editor. The result can be viewed in real time by taking the vehicle to a test drive and by pressing Alt + F9 to update game data.

=== Creating a reticle template for multiple vehicles ===

Complete the first 3 steps described in the instruction "Creating a reticle template for a single vehicle". Then copy the sight_1 file to the folder “all_tanks”. Now you just need to specify which vehicles have the available sight.

Open the .blk file of the sighting reticle using any text editor and add the following block to it:
matchExpClass {
}

You can specify the classes of vehicles for which the sight will be allowed for use or the specific list of vehicles inside this block.

=== Vehicle classes ===

{| class="wikitable" style="width: 100%;"
|+
! style="width: 20%;" |Option
! style="width: 80%;" |Description
|-
| exp_tank
| light and medium tanks
|-
| exp_heavy_tank
| heavy tanks
|-
| exp_tank_destroyer
| tank destroyers, ATGM carriers
|-
| exp_SPAA
| SPAA and SAM
|-
|}

Inside the block you can specify several vehicle classes and even combine them with specific vehicles. For example:
matchExpClass {
exp_heavy_tank:b = yes
ussr_object_120:b = yes
}

This sight will be available for all heavy tanks and the [[Object 120]].

The ID of the particular tank can be found by clicking "Edit source" in its article in the Wiki. The ID can be found inside the block <code><nowiki>{{Specs-Card</nowiki>|code='''ussr_pr_206'''}}</code>.

The ID will also be specified in the name of the catalogue which is created when creating the custom sight.

{{Notice
|In order to maintain full functionality for the universal sight for vehicle classes, it is not recommended limiting it to specific cannons and ammunition. Their ballistic reticle will simply not be displayed if the vehicle doesn't have the shells which are specified in the “ballistics” block.

When creating historical sights it is always better to use the ID of the specific vehicle for which it is suitable.
|!
}}

=== Editing the .blk file of the sighting reticle ===

The content of the reticle file is as follows:
block_name {
param_name: type = value

block_name {
param_name: type = value
}
}

* '''block_name''' - the name of the block, it must start with a Latin letter or underscore and consist of Latin letters, numbers or underscores.
* '''param_name''' - the name of the parameter, it must start with a Latin letter or underscore and consist of Latin letters, numbers or underscores.
* '''type'''- parameter type, must be necessarily, can be one of:
** '''t''' - a text (the value of the parameter must be enclosed in quotation marks "")
** '''r''' - a number
** '''i''' - an integer
** '''b''' - a boolean value in the form of yes / no on / off true / false or 1/0
** '''p2''' - a range of data from 2 values (p3 of three, p4 of four)

If an invalid variable type is specified, for example, instead of an integer textAlign: i = 1, you specify textAlign: i = 1,5 the game will not be able to read such a file and you will not see the changes you specified.

''To edit such files it is more convenient to use different programs for editors, for example, free Visual Studio Code for which there are already extensions that are familiar with the syntax of blk files (Blk and BlkTool they can be found in the extensions panel of the program by searching for blk).''

=== The following parameters can currently be changed in the code ===

{| class="wikitable" style="width: 100%;"
|+
! style="width: 30%;" |Parameter
! style="width: 70%;" |Description
|-
| thousandth:t = “ussr”
| <div class="mw-collapsible mw-collapsed" style="width:100%">The choice for the type of the thousandth for the whole sight<div class="mw-collapsible-content">
Possible values for ussr (1/6000), nato (1/6400), real (1/6283)
</div><div>
|-
| crosshairHorVertSize:p2 = 4, 2
| The size of the notches on the horizontal range-adjustment scale. The first value is the size of the notches with a denomination in thousands, the second is with no denomination (intermediate notches)
|-
| rangefinderProgressBarColor1:c = 0, 255, 0, 64
| Color of the rangefinder progress bar in the format RGB plus alpha channel
|-
| rangefinderProgressBarColor2:c = 255, 255, 255, 64
| Color of the rangefinder progress bar background
|-
| rangefinderTextScale:r = 0.7
| <div class="mw-collapsible mw-collapsed" style="width:100%">rangefinder text size<div class="mw-collapsible-content">
Note: ''Does not change the size of the estimated distance output text.''
</div><div>
|-
| rangefinderUseThousandth:b = es
| <div class="mw-collapsible mw-collapsed" style="width:100%">Sets rangefinder offsets to thousands<div class="mw-collapsible-content">
Attention: ''this is a new line added with 1.79, and without it the rangefinder in Custom Sights will NOT work! For old sights you'll probably have to add this line...''
</div><div>
|-
| rangefinderVerticalOffset:r = 15
| Rangefinder vertical offset relative to center of screen (positive direction is up)
|-
| rangefinderHorizontalOffset:r = 5
| <div class="mw-collapsible mw-collapsed" style="width:100%">Rangefinder horizontal offset relative to center of screen (positive direction is right)<div class="mw-collapsible-content">
Note: ''The "rangefinder" is actually by default the green bar that takes a few seconds to fill and will output an approximate distance, affected by crew training''
</div><div>
|-
| fontSizeMult:r = 1
| <div class="mw-collapsible mw-collapsed" style="width:100%">Line thickness<div class="mw-collapsible-content">
Note: ''Large fonts may prevent certain text from rendering if too close to each other (e.g. default Panther D sight)''
</div><div>
|-
| lineSizeMult:r = 1
| Thickness of lines drawn using the <code>line</code> function
|-
| drawCentralLineVert:b = yes
| <div class="mw-collapsible mw-collapsed" style="width:100%">Display vertical sight line (yes/no)<div class="mw-collapsible-content">
Note: ''The default vertical crosshair line.''
</div><div>
|-
| drawCentralLineHorz:b = yes
| <div class="mw-collapsible mw-collapsed" style="width:100%">Display horizontal sight line (yes/no)<div class="mw-collapsible-content">
Note: ''The default horizontal crosshair line. The horizontal line is in line with the default ballistics range indicator.''
</div><div>
|-
| crosshairDistHorSizeMain:p2 = 0.03, 0.02
| <div class="mw-collapsible mw-collapsed" style="width:100%">Length of the default lines along the default ballistics range indicator<div class="mw-collapsible-content">
Note: ''These lines link up with the range indicators (on the default sights, 4, 8, 12, 16 etc.) The second value gets added to the first value along the major indicators (e.g. numbers 4, 8, 12, 16, 20 etc. on the default sight are extra long).''
</div><div>
|-
| crosshairDistHorSizeAdditional:p2 = 0.005, 0.003
| <div class="mw-collapsible mw-collapsed" style="width:100%">Length of the default ballistics range indicator lines along the central vertical aiming axis<div class="mw-collapsible-content">
Note: ''Parameter definitions are similar to the ones above (Length, Additional_length_for_major_lines)''
</div><div>
|-
| distanceCorrectionPos:p2 = -0.1, -0.05
| <div class="mw-collapsible mw-collapsed" style="width:100%">Field offset of the entered range correction value<div class="mw-collapsible-content">
Note: ''First number – horizontal offset (+ to right of center, - to left of center), second number – vertical offset (+ up from center, - down from center) )''
</div><div>
|-
| drawDistanceCorrection:b = yes
| <div class="mw-collapsible mw-collapsed" style="width:100%">Draw or don’t draw text for entered range correction<div class="mw-collapsible-content">
Note: ''The number drawn is typically rounded up to the closest 50 meters, between 200 and the upper limit of the listed distances specified in <code>crosshair_distances{}</code>''
</div><div>
|-
| crosshairColor:c = 31, 239, 31, 255
| Color of the crosshair (all lines) in the format RGB and its alpha channel
|-
| crosshairLightColor:c = 255, 30, 30, 255
| Color after enabling the crosshair lighting
|-
|}

=== Parameters for controlling the radial moving of lines, texts, circles ===

{| class="wikitable" style="width: 100%;"
|+
! style="width: 30%;" |Parameter
! style="width: 70%;" |Description
|-
| radialCenter:p2 = 0.0, 0.0
| The point relative to which rotation occurs
|-
| radialAngle:r = 180.0
| The initial angular displacement from zero in degrees
|-
| adialMoveSpeed:r = 6.04
| <div class="mw-collapsible mw-collapsed" style="width:100%">Rotation speed multiplier<div class="mw-collapsible-content">
Note: ''Paired with radial stretch, allows objects to rotate at the same speed as the extended scale''
</div><div>
|-
| moveRadial:b=yes
| Angular moving resolution
|-
|}

<gallery perrow=2 widths="460px" heights="260px">
File:1_Sighting grid IT-1.jpg| A simple example of the thickness of notches and font size of an IT-1 sight after editing lineSizeMult:r = 2.0 and fontSizeMult:r = 2.0.
File:2_Sighting grid IT-1 with a changed thickness of scratches and font size.jpg| Apart from these settings, the standard sight contains the block crosshair_distances, which determines how regularly the range correction notches will be placed.
</gallery>

====Main parameters====

A simple example of the thickness of notches and font size of an IT-1 sight after editing '''lineSizeMult:r = 2.0''' and '''fontSizeMult:r = 2.0'''.
Apart from these settings, the standard sight contains the block crosshair_distances, which determines how regularly the range correction notches will be placed.

crosshair_distances{
distance:p3 =200, 0, 0
distance:p3 =400, 4, 0
distance:p3 =600, 0, 0
distance:p3 =800, 8, 0
distance:p3 =1000, 0, 0
distance:p3 =1200, 12, 0
distance:p3 =1400, 0, 0
distance:p3 =1600, 16, 0
distance:p3 =1800, 0, 0
distance:p3 =2000, 20, 0
distance:p3 =2200, 0, 0
distance:p3 =2400, 24, 0
distance:p3 =2600, 0, 0
distance:p3 =2800, 28, 0
}

crosshair_distances can be set in three ways (important as: the methods cannot be mixed):

{| class="wikitable" style="width: 100%;"
|+
! style="width: 30%;" |Parameter
! style="width: 70%;" |Description
|-
| distance:p2 =2800, 28
| The 2800 value is the distance to the target at which the notch will be drawn; 28 is which text will be placed by the notch (0 means display nothing)
|-
| distance:p3 =2800, 28, 0.01
| The 0.01 value is how much to increase the length of the notch from the left (-0.01 means extend it from the right)
|-
| distance { textPos:p2 = 0.042, 0; distance:p3 = 1000, 10, 0.01; }
| The textPos is an additional offset of the notch text (textPos:p2 = 0, 0 by default)
|-
|}

crosshair_hor_ranges{
range:p2 =-32, 32
range:p2 =-28, 0
range:p2 =-24, 24
range:p2 =-20, 0
range:p2 =-16, 16
range:p2 =-12, 0
range:p2 =-8, 8
range:p2 =-4, 0
range:p2 =4, 0
range:p2 =8, 8
range:p2 =12, 0
range:p2 =16, 16
range:p2 =20, 0
range:p2 =24, 24
range:p2 =28, 0
range:p2 =32, 32
}

These are the parameters of the standard sight. Apart from these elements, the sight can also contain a few more blocks that provide new options.

==== Shell ballistics block ====

The standard sight automatically draws a target reticule on the basis of the ballistic data of the selected shell type. However, with the help of this block, you can create a sight that will permanently display several lines for various types of shells, and their ballistics will correspond to the in-game values.
To display these lines, you must add the ballistics block, including the required number of bullet blocks, each of which has its own settings that are responsible for drawing and placing lines.

The shell ballistic data, which the game automatically recalculates into the distance between the line notches, are provided by the parameters:
* '''bulletType:t = "apcbc_tank"''' – ID of the ammunition type for which a line needs to be created (see the table of correspondence of shell types in the game localization).
* '''speed:r = 624.0''' – initial shell speed, which can be seen in the shell’s card along with the name of the shell type.

'''Important!''' The lines are linked with ammunition loading. If the tank’s ammunition complement doesn’t have a specific shell type, then the line for that shell type will not be displayed.

An example ballistics block for the T-55A tank and three shell types, APFSD ZBM25, KS-ZBK17 and composite armor-piercing BR-412D:
ballistics {
bullet {
bulletType:t = "apds_fs_tungsten_small_core_tank"
speed:r = 1430.0
drawAdditionalLines:b = no
drawDistanceCorrection:b = yes
distanceCorrectionPos:p2 = -0.15, -0.15
drawUpward:b = yes // option to draw the displayed line upwards, as in the Soviet sights, for example TSh2B-41.
distancePos:p2 = 0.03, 0.0 // line offset relative to center.
textAlign:i = 1
textPos:p2 = -0.012, 0.0
textShift:r = 0.0
crosshairDistHorSizeMain:p2 = 0.0075, 0.0075
crosshairDistHorSizeAdditional:p2 = 0.005, 0.003
crosshair_distances {
distance:p3 = 200, 0, 0 // + and - notches
distance:p3 = 400, 0, 0
distance:p3 = 600, 0, 0
distance:p3 = 800, 0, 0
distance:p3 = 1000, 10, 0.01
distance:p3 = 1200, 0, 0
distance:p3 = 1400, 0, 0
distance:p3 = 1600, 0, 0
distance:p3 = 1800, 0, 0
distance:p3 = 2000, 20, 0.01
}
}
bullet {
bulletType:t = "heat_fs_tank"
speed:r = 1085.0
drawAdditionalLines:b = no // draw notches on the central line
drawDistanceCorrection:b = no
distanceCorrectionPos:p2 = -0.09, -0.05
distancePos:p2 = -0.02, 0.0 //line offset
textPos:p2 = 0.02, 0.0
textShift:r = 0.0 //text offset
textAlign:i = 2 //text position relative to notches
crosshairDistHorSizeMain:p2 = 0.0075, 0.0075
crosshairDistHorSizeAdditional:p2 = 0.005, 0.003
crosshair_distances {
distance:p3 = 200, 0, 0
distance:p3 = 300, 0, 0
distance:p3 = 400, 0, 0
distance:p3 = 500, 5, -0.01
distance:p3 = 600, 0, 0
distance:p3 = 700, 0, 0
distance:p3 = 800, 0, 0
distance:p3 = 900, 0, 0
distance:p3 = 1000, 10, -0.01
distance:p3 = 1100, 0, 0
distance:p3 = 1200, 0, 0
distance:p3 = 1300, 0, 0
distance:p3 = 1400, 0, 0
distance:p3 = 1500, 15, -0.01
distance:p3 = 1600, 0, 0
distance:p3 = 1700, 0, 0
distance:p3 = 1800, 0, 0
distance:p3 = 1900, 0, 0
distance:p3 = 2000, 20, 0
}
}
bullet {
bulletType:t = "apcbc_tank"
speed:r = 887.0
drawAdditionalLines:b = no // draw notches on the central line
drawDistanceCorrection:b = no
distanceCorrectionPos:p2 = -0.09, -0.05
distancePos:p2 = -0.07, 0.0 //line offset
textPos:p2 = 0.02, 0.0
textShift:r = 0.0 //text offset
textAlign:i = 2 //text position relative to notches
crosshairDistHorSizeMain:p2 = 0.0075, 0.0075
crosshairDistHorSizeAdditional:p2 = 0.005, 0.003
crosshair_distances {
distance:p3 = 200, 0, 0
distance:p3 = 300, 0, 0
distance:p3 = 400, 0, 0
distance:p3 = 500, 5, -0.01
distance:p3 = 600, 0, 0
distance:p3 = 700, 0, 0
distance:p3 = 800, 0, 0
distance:p3 = 900, 0, 0
distance:p3 = 1000, 10, -0.01
distance:p3 = 1100, 0, 0
distance:p3 = 1200, 0, 0
distance:p3 = 1300, 0, 0
distance:p3 = 1400, 0, 0
distance:p3 = 1500, 15, -0.01
distance:p3 = 1600, 0, 0
distance:p3 = 1700, 0, 0
distance:p3 = 1800, 0, 0
distance:p3 = 1900, 0, 0
distance:p3 = 2000, 20, 0
}
}
}

<gallery perrow=1 widths="460px" heights="260px">
3_Sighting_grid_Т-55А.jpg| T-55A
</gallery>

'''Parameters within bullet block'''

{| class="wikitable" style="width: 100%;"
|+
! style="width: 30%;" |Parameter
! style="width: 70%;" |Description
|-
| bulletType:t = "apds_fs_tungsten_small_core_tank"
| Shell type
|-
| speed:r = 1430.0
| <div class="mw-collapsible mw-collapsed" style="width:100%">Muzzle velocity<div class="mw-collapsible-content">
Note: ''A twin machine gun line can also be set in a bullet block. To do this, enter the following parameters:''
</div><div>
|-
| triggerGroup:t = "coaxial"
| Weapon type (mandatory)
|-
| speed:r = 815.0
| Shell velocity
|-
| drawAdditionalLines:b = no
| Sets whether the line for this shell should be duplicated (yes/no)
|-
| drawDistanceCorrection:b = yes
| Sets whether to display a field in which the numerical value of the range correction will be shown (yes/no)
|-
| distanceCorrectionPos:p2 = -0.15, -0.15
| Range correction field offset
|-
| distancePos:p2 = 0.03, 0.0
| Line offset relative to center
|-
| textAlign:i = 1
| Numerical marker offset on the line relative to notches (-1, 0 or 1)
|-
| textPos:p2 = -0.012, 0.0
| Correction offset relative to notches
|-
| textShift:r = 0.0
| Text correction offset and downsizing of line notches
|-
| crosshairDistHorSizeMain:p2 = 0.0075, 0.0075
| Size and position of notches
|-
| crosshairDistHorSizeAdditional:p2 = 0.005, 0.003
| Size and position of additional notches (on vertical sight axis)
|-
|
crosshair_distances {
distance:p3 = 200, 0, 0
distance:p3 = 400, 0, 0
distance:p3 = 600, 0, 0
distance:p3 = 800, 0, 0
distance:p3 = 1000, 10, 0.01
distance:p3 = 1200, 0, 0
distance:p3 = 1400, 0, 0
distance:p3 = 1600, 0, 0
distance:p3 = 1800, 0, 0
distance:p3 = 2000, 20, 0.01
}
| First value - range<br>second value – number<br>third value – notch size
|-
|}

== ID of shell types and their localization in the game ==
'''Cannons'''
{| class="wikitable"
|-
| "apcr_tank" || "Armor-piercing composite rigid shell"
|-
| "apds_tank" || "Armor-piercing discarding sabot shell"
|-
| "apds_fs_long_tank" || "Armor-piercing fin-stabilized discarding-sabot shell"
|-
| "apds_fs_full_body_steel_tank" || "Armor-piercing fin-stabilized discarding-sabot shell"
|-
| "apds_fs_tungsten_small_core_tank" || "Armor-piercing fin-stabilized discarding-sabot shell (steel))"
|-
| "apds_fs_tungsten_l10_l15_tank" || "Armor-piercing fin-stabilized discarding-sabot shell"
|-
| "apbc_tank" || "Armor-piercing blunt-nosed shell"
|-
| "ap_large_caliber_tank" || "Armor-piercing blunt-nosed shell" (Used on the AP shell of the T34/M103)
|-
| "apc_tank" || "Armor-piercing sharp-nosed shell (with armor-piercing tip))"
|-
| "aphe_tank" || "Armor-piercing sharp-nosed high-explosive shell"
|-
| "aphebc_tank" || "Armor-piercing blunt-nosed high-explosive shell"
|-
| "apcbc_tank" || "Armor-piercing shell with armor-piercing tip and ballistic cap"
|-
| "ap_tank" || "Armor-piercing sharp-nosed solid shell"
|-
| "heat_tank" || "High-explosive hollow charge shell"
|-
| "heat_grenade_tank" || "Anti-tank grenade"
|-
| "heat_fs_tank" || "High-explosive non-rotating shell"
|-
| "hesh_tank" || "Armor-piercing incendiary shell"
|-
| "he_grenade_tank" || "High-explosive grenade"
|-
| "he_frag_tank" || "High-explosive shell"
|-
| "he_frag_fs_tank" || "High-explosive shell"
|-
| "shrapnel_tank" || "Shrapnel"
|-
| "atgm_tank" || "Anti-tank guided rocket"
|-
| "rocket_tank" || "Unguided rocket"
|-
| "smoke_tank" || "Smoke shell"
|}

'''Machine guns'''
{| class="wikitable"
|-
! Machine gun !! Velocity !! Bullet type
|-
| "7_7mm_Type_97_user_machinegun" || 730 || ap_ball
|-
| "7_7mm_Vikkers_user_machinegun" || 920 || i_t_ball
|-
| "7_62mm_DT_user_machinegun" || 815 || ap_i_ball
|-
| "7_62mm_M37_user_machinegun" || 853 || ap_ball
|-
| 7_62mm_M73_user_machinegun || 853 || ap_ball
|-
| 7_62mm_M1919A4_user_machinegun || 853 || ap_ball
|-
| 7_62mm_PKT_user_machinegun || 815 || ap_i_ball
|-
| 7_62mm_SGMT_user_machinegun || 815 || ap_i_ball
|-
| 7_62mm_Type74_user_machinegun || 853 || ap_ball
|-
| 7_92mm_BESA_user_machinegun || 880 || ap_i_ball
|-
| 7_92mm_MG3_user_machinegun || 853 || ap_ball
|-
| 7_92mm_MG34_user_machinegun || 880 || ap_i_ball
|-
| 7_92mm_MG42_user_machinegun || 880 || ap_i_ball
|-
| 8mm_Breda_Mod38_user_machinegun || 790 || ap_i_t_ball
|-
| 12_7mm_M2_HB_user_machinegun || 887 || ap_i_t_ball_M20
|-
| 14_5mm_KPVT_user_machinegun || 1000 || ap_i_t_ball
|-
|}

'''Radial scales and elements (block ballistics/bullet)'''

{| class="wikitable" style="width: 100%;"
|+
! style="width: 30%;" |Parameter
! style="width: 70%;" |Description
|-
| radial:b = no
| Choice of the scale type
|-
| circleMode:b = no
| Draw circles instead of lines on the scale (like on German Tzf9 sights)
|-
| move:b = yes
| Move or not with the introduction of correction
|-
| radialStretch:r = 1.0
| Radial scale extension factor (If the points are too close to each other)
|-
| radialAngle:r = 0.0
| The initial angular displacement of the scale in degrees
|-
| radialRadius:p2 = 0, 0
| Radius. x - radius; y - 0 or 1, where 1 means that the radius in the thousandth
|-
|}

'''In case with the radial scale the parameter crosshairDistHorSizeMain has the following meaning:'''
* x - circumference thickness
* y - radius of a circle

In case with the radial scale the parameter crosshair_distances/distance.z means the radius of a circle.

* '''drawUpward:b = yes''' - changes the scale displaying to a mirror one.

For maximum sight customization, you can use the drawLines and drawTexts blocks, with the help of which you can draw elements from the cutoffs and text, indicating their coordinates:

drawLines {
line { line:p4 = 0, -1.0, 0, -0.018; move:b = false; }
line { line:p4 = -50, 30, -50, 40; thousandth:b = true; }
}

To draw one line, you have to enter 4 coordinates – the offset in fractions of the screen of its start and end.
<br>'''line { line:p4 = 0.25, -0.25, 0, -0.0; move:b = false; }''' – this block draws one line which begins in the upper right quarter of the screen and ends in the center of the screen. It is static and does not move when a range is entered.

<gallery perrow=1 widths="460px" heights="260px">
File:THS1.jpg|Example of drawing one line
</gallery>

For convenience when creating historical reticules, thousandth can be set to true to represent editing units in mils by indicating the coordinate offset for the start and end of the line in thousands too. When thousandth is set to false, one mil is approximately to 0.04 units.

For example, <code>line { line:p4 = -32, -32, 0, 0; thousandth:b = true; }</code> will show a diagonal line extending 32 mils to the left:

<gallery perrow=1 widths="460px" heights="260px">
File:THS2.jpg|Example of drawing one line with coordinates in the thousands
</gallery>

Drawing Text:
drawTexts {
text {
text:t = "X" // desired symbol
align:i = 0 // offset relative to its indicated position
pos:p2 = 32, 0 // coordinates of the X and Y symbol positions in fractions of the screen
move:b = no // whether the text will move when a range is entered
thousandth:b = yes // or in thousands
size:r = 1.7 // text size
}
}

Drawing Circles:
drawCircles {
circle {
segment:p2 = 0.0, 360.0; // Sector of a circle
pos:p2 = 0.0, 90.0; // Position
diameter:r = 3.0; // Diameter. If thousandth=yes, then in thousandths
size:r = 2.0; // Line Thickness
move:b = no;
thousandth:b = yes;
}
}

Drawing painted figures on the basis of a quadrangle. With its help you can draw different types of figures that have 4 vertices and figures of arbitrary shape with 3 (triangle) or 2 (line) vertices.
drawQuads {
quad { // Simple fixed quadrangle
tl:p2 = -10, -10; // Top left top
tr:p2 = 10, -10; // Top right top
br:p2 = 10, 10; // Top right bottom
bl:p2 = -10, 10; // Top left bottom
thousandth:b = true;
}
quad { // Object that can be moved along the radius
tl:p2 = -10, -140;
tr:p2 = 10, -140;
br:p2 = 0, -96;
bl:p2 = 0, -96;
center:p2 = 0, -90; // The center of the figure is needed for correct rotation. By default the geometric center of a shape.
radialCenter:p2 = 0.0, 0.0;
radialAngle:r = 0;
radialMoveSpeed:r = 6.04;
moveRadial:b = yes;
thousandth:b = true;
}
}

== Example of implementing a historical sight reticule ==

Using the entire spectrum of possibilities for creating user-made sight reticules, one can create sight reticules that will be as close as possible to the historical versions.

As an example, here is the sight skin of the Italian P40 tank:

<gallery>
<gallery perrow=2 widths="460px" heights="260px">
File:P40HS1.jpg| Photo of the real P40 sight.
File:P40HS2.jpg| Example implementation of the P40 sight in the game.
</gallery>

And the settings block that can be used to create this sight:

it_san_giorgio_x4 {
crosshairHorVertSize:p2 = 0, 0
rangefinderProgressBarColor1:c = 0, 255, 0, 64
rangefinderProgressBarColor2:c = 255, 255, 255, 64
rangefinderTextScale:r = 0.7
rangefinderVerticalOffset:r = 15
rangefinderHorizontalOffset:r = 5
fontSizeMult:r = 1.25
lineSizeMult:r = 1.5
drawCentralLineVert:b = no
drawCentralLineHorz:b = no
crosshairDistHorSizeMain:p2 = 0.03, 0.02
crosshairDistHorSizeAdditional:p2 = 0.005, 0.003
distanceCorrectionPos:p2 = -0.2, -0.05
drawDistanceCorrection:b = yes

ballistics {
bullet {
bulletType:t = "apcbc_tank"
speed:r = 624.0

drawAdditionalLines:b = no
drawDistanceCorrection:b = yes
distanceCorrectionPos:p2 = -0.15, -0.15

distancePos:p2 = 0.03, 0.0 // line offset relative to center.
textAlign:i = 1
textPos:p2 = -0.012, 0.0
textShift:r = 0.0
crosshairDistHorSizeMain:p2 = 0.0075, 0.0075
crosshairDistHorSizeAdditional:p2 = 0.005, 0.003

crosshair_distances {
distance:p3 = 200, 0, 0 // + and - notches
distance:p3 = 400, 0, 0
distance:p3 = 600, 0, 0
distance:p3 = 800, 0, 0
distance:p3 = 1000, 10, 0.01
distance:p3 = 1200, 0, 0
distance:p3 = 1400, 0, 0
distance:p3 = 1600, 0, 0
distance:p3 = 1800, 0, 0
distance:p3 = 2000, 20, 0.01
}

t_san_giorgio_x4 {
crosshairHorVertSize:p2 = 0, 0
rangefinderProgressBarColor1:c = 0, 255, 0, 64
rangefinderProgressBarColor2:c = 255, 255, 255, 64
rangefinderTextScale:r = 0.7
rangefinderVerticalOffset:r = 15
rangefinderHorizontalOffset:r = 5
fontSizeMult:r = 1.25
lineSizeMult:r = 1.5
drawCentralLineVert:b = no
drawCentralLineHorz:b = no
crosshairDistHorSizeMain:p2 = 0.03, 0.02
crosshairDistHorSizeAdditional:p2 = 0.005, 0.003
distanceCorrectionPos:p2 = -0.2, -0.05
drawDistanceCorrection:b = yes

ballistics {
bullet {
bulletType:t = "apcbc_tank"
speed:r = 624.0

drawAdditionalLines:b = no
drawDistanceCorrection:b = yes
distanceCorrectionPos:p2 = -0.15, -0.15

distancePos:p2 = 0.03, 0.0 // line offset relative to center.
textAlign:i = 1
textPos:p2 = -0.012, 0.0
textShift:r = 0.0
crosshairDistHorSizeMain:p2 = 0.0075, 0.0075
crosshairDistHorSizeAdditional:p2 = 0.005, 0.003

crosshair_distances {
distance:p3 = 200, 0, 0 // + and - notches
distance:p3 = 400, 0, 0
distance:p3 = 600, 0, 0
distance:p3 = 800, 0, 0
distance:p3 = 1000, 10, 0.01
distance:p3 = 1200, 0, 0
distance:p3 = 1400, 0, 0
distance:p3 = 1600, 0, 0
distance:p3 = 1800, 0, 0
distance:p3 = 2000, 20, 0.01
}
}

bullet {
bulletType:t = "he_frag_tank"
speed:r = 552.0

drawAdditionalLines:b = no // draw notches on the central line

drawDistanceCorrection:b = no
distanceCorrectionPos:p2 = -0.09, -0.05

distancePos:p2 = -0.02, 0.0 //line offset
textPos:p2 = 0.02, 0.0
textShift:r = 0.0 //text offset
textAlign:i = 2 //text position relative to notches
crosshairDistHorSizeMain:p2 = 0.0075, 0.0075
crosshairDistHorSizeAdditional:p2 = 0.005, 0.003

crosshair_distances {
distance:p3 = 200, 0, 0
distance:p3 = 300, 0, 0
distance:p3 = 400, 0, 0
distance:p3 = 500, 5, -0.01
distance:p3 = 600, 0, 0
distance:p3 = 700, 0, 0
distance:p3 = 800, 0, 0
distance:p3 = 900, 0, 0
distance:p3 = 1000, 10, -0.01
distance:p3 = 1100, 0, 0
distance:p3 = 1200, 0, 0
distance:p3 = 1300, 0, 0
distance:p3 = 1400, 0, 0
distance:p3 = 1500, 15, -0.01
distance:p3 = 1600, 0, 0
distance:p3 = 1700, 0, 0
distance:p3 = 1800, 0, 0
distance:p3 = 1900, 0, 0
distance:p3 = 2000, 20, 0
}
}
}

crosshair_hor_ranges {
range:p2 = -60, 60
range:p2 = -50, 0
range:p2 = -40, 40
range:p2 = -30, 0
range:p2 = -20, 20
range:p2 = 20, 20
range:p2 = 30, 0
range:p2 = 40, 40
range:p2 = 50, 0
range:p2 = 60, 60
}

drawLines {
// Vertical lines
line { line:p4 = 0, -1.0, 0, -0.018; move:b = false; }
line { line:p4 = 0, 0.018, 0, 1.0; move:b = false; }

// Horizontal lines
line { line:p4 = -1.0, 0, -0.02, 0; }
line { line:p4 = 0.02, 0, 1.0, 0; }

//
line { line:p4 = -0.002, 0, -0.01, 0.00; move:b = false; }
line { line:p4 = 0.002, 0, 0.01, 0.00; move:b = false; }

line { line:p4 = 0.0, 0.002, 0.0, 0.01; move:b = false; }
line { line:p4 = 0.0, -0.002, 0.0, -0.01; move:b = false; }

line { line:p4 = -30, 30, -30, 40; thousandth:b = true; }
line { line:p4 = -40, 30, -40, 40; thousandth:b = true; }
line { line:p4 = -50, 30, -50, 40; thousandth:b = true; }

line { line:p4 = 30, 30, 30, 40; thousandth:b = true; }
line { line:p4 = 40, 30, 40, 40; thousandth:b = true; }
line { line:p4 = 50, 30, 50, 40; thousandth:b = true; }

line { line:p4 = -30, 0, -30, 10; thousandth:b = true; }
line { line:p4 = -40, 0, -40, 10; thousandth:b = true; }
line { line:p4 = -50, 0, -50, 10; thousandth:b = true; }

line { line:p4 = 30, 0, 30, 10; thousandth:b = true; }
line { line:p4 = 40, 0, 40, 10; thousandth:b = true; }
line { line:p4 = 50, 0, 50, 10; thousandth:b = true; }

line { line:p4 = 20, 0, 20, 3,5; thousandth:b = true; }
line { line:p4 = -20, 0, -20, 3,5; thousandth:b = true; }
line { line:p4 = 60, 0, 60, 5; thousandth:b = true; }
line { line:p4 = -60, 0, -60, 5; thousandth:b = true; }

line { line:p4 = 70, 0, 70, 5; thousandth:b = true; }
line { line:p4 = -70, 0, -70, 5; thousandth:b = true; }
}
}

== Upload, Download and share custom gun sights ==
* [https://live.warthunder.com/feed/sights/ Click here to upload and download user made gun sights! #Sights]
* [https://live.warthunder.com/feed/?q=%23sight Click here for even more custom gun sights #Sight]
* [https://live.warthunder.com/feed/?q=%23crosshair Click here for even more and more gun sights #Crosshair]

[[Category:War Thunder CDK]]
[[Category:Custom skins]]

User:U100138

2019-10-25T20:12:41Z

U100138: Created page with "(*´・ω・)/`"

(*´・ω・)/`

Talk:War Thunder CDK

2019-10-25T20:12:15Z

U100138:

It seems like quite a lot of pages related to the CDK cannot be edited.
Is it possible that we can have them open for edit, so that if new pages are created for topics related to the CDK, they can be linked to them?

The topic of Triggers and Actions for example is very vast and simply adding the information to the Mission Editor page will not be sufficient.
- Avarik
:*When you went to edit one of these pages, did you just get the message at the top regarding the page protection or did it actually prevent you from making edits? We have had other regular users who have made edits with no issues. If you are "locked" out of editing the page, you might create your "User" page (changes your name from 'Red' to 'Blue' - though you will have to wait for a moderator to approve before it turns blue.), this may be what the system is looking for as a "registered" user. Try these options out, if you are still having issues we can look into this further. There are a few pages which are locked for all but the administrators to edit, but you won't even get an option to edit (should be read-only and view history as options). --[[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 18:36, 21 October 2019 (UTC) (also, when signing a talk page, use four tildes's in a row <nowiki>~~~~</nowiki> and this will auto-populate your name and time stamp your message like it did mine here).
::* I don't have the option to edit [[Instructions_for_Using_the_Mission_Editor|this page]]. The edit buttons are replaced with "View source", in the same way they are for the main page. --[[User:U13682523|U13682523]] ([[User talk:U13682523|talk]]) 21:17, 21 October 2019 (UTC)
:::* Yes the page you listed can only be edited by administrators and above, I don't even have access to edit that page. --[[User:U64962917|U64962917]] ([[User talk:U64962917|talk]]) 21:42, 21 October 2019 (UTC)
::::* I don't have edit permissions for the main page, but [[Instructions_for_Using_the_Mission_Editor|the page Flame2512 listed]] is only protected for administrators and moderators, so you should have access to edit it...? -[[User:U38088265|U38088265]] ([[User talk:U38088265|talk]]) 21:47, 21 October 2019 (UTC)
:Some of the pages like the triggers page are only semiprotected. I believe those pages become editable after a wait period(the admin should know the exact reason).--[[User:U30585107|U30585107]] ([[User talk:U30585107|talk]]) 18:39, 21 October 2019 (UTC)

: Triggers [[Triggers|already have a very large article]] about them, written by myself and Paradoxorigins. You are welcome to help us finish the details of what each action does, and what each option for that action means. --[[User:U13682523|U13682523]] ([[User talk:U13682523|talk]]) 21:17, 21 October 2019 (UTC)
::That's the page he was talking about being protected. [https://wiki.warthunder.com/index.php?title=Special%3AProtectedPages&namespace=&type=edit&level=autoconfirmed&sizetype=min&size=| It's semiprotected. ]--[[User:U30585107|U30585107]] ([[User talk:U30585107|talk]]) 00:15, 22 October 2019 (UTC)
:::*Yes, I'm able to edit the semi-protected pages, but the problem still lies in the main article pages. I can understand they're locked but having some option to modify them will be great, not for me specifically but for anyone within the CDK community. [[User:U100138|U100138]] ([[User talk:U100138|talk]]) 20:12, 25 October 2019 (UTC)

User:U3312106

2019-10-22T09:36:07Z

U100138: V:

[[File:V-.png|thumb|V:]]
Just a test page.

== Multiplayer Missions ==

== How to create multiplayer missions ==

:1. Run mission editor (missioned.cmd in WarThunderCDK folder).
:2. Choose '''Scene view''' tab and load one of game levels (it is location "britain" by default) where you want to create your mission.
::''Note: Missions can be technically run on an location, choosing location scene is just a preview.''
:3. Go to tab Mission Editor.

::*Choose the side toolbar '''Mission Settings -> mission'''
::*Choose a name for your mission in '''name''' tab
::''Note: You can't use capital letters and there should be no spaces''
::*Choose a name for your mission that will be displayed for other players in '''locName''' tab (you can use space there and for example write down '''[Multiplayer Mission] Test''')
::*Choose a description for your mission in '''locDesc''' tab
::*Set a mission type to '''domination''' in '''type''' tab
::*Choose a location map in '''level''' tab
::*Choose time of a day and weather in '''Weather params''' tab

:4. Create a new unit by pressing '''Create unit''' icon and place it somewhere (you can control the map view by pressing '''SPACE''')
:5. Open it's properties (by for example pressing '''P''')

::*Change the '''Name:''' to '''t1_player01'''
::*Switch it's '''type''' to '''armada'''
::*Find a '''dummy''' unit in '''Class''' tab and select it

:6. Copy '''t1_player01''' unit
::''Note: We will need it to create slots for the mission, so it's preferable to create 16 of them, the game supports up to 32 players per team''

::*Select the unit
::*Press '''W'''
::*While holding '''Shift''' select one of displayed arrows and then drag it until a new unit appears
::*The CDK will show you a new window, in this window change the '''Count of clones:''' amount to the number that you want for your mission
::*Select '''Auto rename'''
::*Press '''Ok'''
::*Now you should see lots of copies of this unit named '''t1_player02, t1_player03, t1_player04 etc.'''

:7. Create the same amount of '''t2_player''' units by copying '''t1_player''' units

::*In Unit copying window change '''Name of clone(s):''' to '''t2_player01'''
::*Change the '''Count of clones:''' amount to the number that equals amount of '''t1_player''' units
::*Press '''Ok'''
::*Now you should see lots of copies of '''t1_player''' units named '''t2_player01, t2_player02, t2_player03 etc.'''

:8. Go back to side toolbar '''Mission Settings''' to add these units to make them usable as slots for players in your multiplayer mission

::*Select '''player_teamA'''
::*Press '''wing''' to add new slots and add all '''t1_player''' units there one by one there
::*Select '''player_teamB'''
::*Press '''wing''' to add new slots and add all '''t2_player''' units there one by one there

:9. Create respawn zones for players

::*Choose the side toolbar '''Triggers / Missions Obj. Navigation'''
::*Press the '''Trigger''' button to create a new trigger
::*Press the '''Properties and Trigger/MissionObj info''' icon which you can find on top toolbar to show the tab with trigger properties
::*Select your new trigger and change it's '''Name''' to for example '''respawn'''
::*Make sure that '''Enabled''' is switched on
::*In lower part of this toolbar select '''periodicEvent {time=1.00}''' in the '''Elements:''' window, then select '''Elements''' button on the bottom and press '''periodicEvent''' (if nothing happens then select one of folders in the '''Elements:''' window and then switch back to '''periodicEvent {time=1.00}''')
::*A new window should appear, select '''initMission''' there and press '''Ok''' or double click on '''initMission'''
::*Press the '''Action''' button and below '''Filter:''' type '''missionMarkAsRespawnPoint''' and press '''Ok''' or double click on '''missionMarkAsRespawnPoint'''
::*Now you need to create a zone on the place where you want to players to spawn, you can do that by pressing one of icons on the top toolbar and then pressing the ground on the map view if you selected the first icon and pressing and dragging (you change it's size buy doing that) it if you selected other icons (sphere, cylinder or box)
::*In the '''Object Properties''' window you can change it's '''Name:''', '''Zone type''', '''Position''' or size ('''Radius''', '''Height''', '''Box size''' - depending on which zone type did you select), you should preferably call it '''t1_spawnarea_01''' and make at least 10 of them, then copy all these areas and call them '''t2_spawnarea_01''', '''t2_spawnarea_01''', '''t2_spawnarea_01''' etc. because you need them for both teams
::''Note: If those spawns are meant to be for airplanes then place them in the air, if for tanks then place them on the ground, if for ships then place them on the sea level''
::*Go back to the side toolbar '''Triggers / Missions Obj. Navigation''' and select '''missionMarkAsRespawnPoint''' action in '''Elements:''' window, then assing all existing t1_spawnarea areas to the tab next to '''target''', you can create more of them by just pressing a wide '''target''' tab below. When you do that you can choose the '''loc_name''' (name of that spawn zone which will be visible in game, you can use spaces and capital letters), below it you should see lots of options which can be able or disabled, for now leave them in current state, then press a wide '''team''' tab, a new selectable tab should appear, then press it and select '''A'''. On the bottom of available option you should see a wide '''tags''' tab, by pressing it you will create and expandable window with tabs of all unit types available in the game, select those that you want to use in your mission ('''air''' for airplanes, '''tank''' for ground units, '''ship''' for boats and ships)
::*When you are done look below the '''Elements:''' window, there should be a '''copy''' tab, select '''missionMarkAsRespawnPoint''' action and then press this '''copy''' tab, then press '''Paste ...''' tab, a new window should appear. Select '''missionMarkAsRespawnPoint''' action there and press ok, now you should see two the same actions in the '''Elements:''' window, select the second one. Now you need to change all '''target''' areas to those that are meant to be for the second team (B / T2). When you do that scroll down and in the '''team''' tab switch '''A''' to '''B'''
::''Note: You can speed up changing '''target'<nowiki/>'''''<nowiki/>'''s by creating an '''area_squad''' unit and then putting all t2_spawnarea areas there, then selecting this squad in the ''missionMarkAsRespawnPoint'''''<nowiki/>'' action propeties''
:10. Save your mission

That's all, now all you need is to upload your mission somewhere (any hosting service will do as long as it's link will end as '''.blk''' and don't forget to delete '''https://''' part of that link, otherwise the game won't be able to read it unless it's a live.warthunder.com link) or live.warthunder.com site, but don't forget to add a proper image and description for your mission. More details you will find [[How to launch a custom mission in the game|here]].

File:V-.png

2019-10-22T09:34:04Z

U100138:

Talk:War Thunder CDK

2019-10-21T17:53:01Z

U100138:

Talk:War Thunder CDK

2019-10-21T17:44:49Z

U100138:

It seems like quite a lot of pages related to the CDK cannot be edited.

Is it possible that we can have them open for edit, or perhaps have the option to crew new pages and add them as extensions to the CDK?
The topic of Triggers and Actions for example is very vast and simply adding the information to the Mission Editor page will not be sufficient.
- Avarik

Talk:War Thunder CDK

2019-10-21T17:43:11Z

U100138: Created page with "It seems like quite a lot of pages related to the CDK cannot be edited. Is it possible that we can have them open for edit, or perhaps have the option to crew new pages and a..."