Файл сценария — различия между версиями

Материал из База знаний
Перейти к: навигация, поиск
(Новая страница: «= Файл = Файл сценария - это обычный текстовый файл. Вы можете редактировать его с помощью л…»)
 
Строка 1: Строка 1:
 +
{{Незавершенная статья}}
 +
 
= Файл =
 
= Файл =
  
 
Файл сценария - это обычный текстовый файл. Вы можете редактировать его с помощью любого текстового редактора или с помощью специального редактора, такого как [http://www.craig-phillips.co.uk/ase/ Aircraft Situation Editor]. Файл считывается линия за линией. В нем нету разделов и Вы можете перемешивать разные типы строк. Единственное исключение, это позиции ВС, после которых должны следовать строки с полетным планом и с маршрутом.
 
Файл сценария - это обычный текстовый файл. Вы можете редактировать его с помощью любого текстового редактора или с помощью специального редактора, такого как [http://www.craig-phillips.co.uk/ase/ Aircraft Situation Editor]. Файл считывается линия за линией. В нем нету разделов и Вы можете перемешивать разные типы строк. Единственное исключение, это позиции ВС, после которых должны следовать строки с полетным планом и с маршрутом.
 +
 +
= ILS/Runway Definitions =
 +
 +
You can define four active runway for one session. It can be defined as an ILS:
 +
 +
<pre>
 +
ILS&lt;runway name&gt;:&lt;threshold latitude&gt;:&lt;threshold longitude&gt;:&lt;runway heading&gt;
 +
</pre>
 +
 +
The name of the runway will be shown in the four buttons.
 +
An example line:
 +
 +
<pre>
 +
ILS31r:N047.25.24.615:E019.17.35.260:310
 +
</pre>
 +
 +
= Holding Definitions =
 +
 +
You can define as many number of holding patterns as you need. The definition line is the following:
 +
 +
<pre>
 +
HOLDING:&lt;fix name&gt;:&lt;inbound course&gt;:&lt;direction&gt;
 +
</pre>
 +
 +
Where ''fix name'' can be anything (VOR, NDB, FIX) from the sectorfile. The ''direction'' can be '''1''' to indicate a right turn and '''-1''' for a left turn. Here are some examples:
 +
 +
<pre>
 +
HOLDING:AGMAS:310:1
 +
HOLDING:MAMOS:130:-1
 +
HOLDING:VEBOS:95:-1
 +
HOLDING:TPS:160:-1
 +
</pre>
 +
 +
 +
= Airport Altitude =
 +
 +
It is a single line definition:
 +
 +
<pre>
 +
AIRPORT_ALT:&lt;altitude&gt;
 +
</pre>
 +
 +
 +
An example:
 +
 +
<pre>
 +
AIRPORT_ALT:550
 +
</pre>
 +
 +
= Controllers Definitions =
 +
 +
There can be an unlimited number of simulated controllers in the simulation session. They also can be configured in the scenario file:
 +
 +
<pre>
 +
CONTROLLER:&lt;callsign&gt;:&lt;frequency&gt;
 +
</pre>
 +
 +
An example:
 +
 +
<pre>
 +
CONTROLLER:LHCC_CTR:133.2
 +
CONTROLLER:LHBP_TWR:118.1
 +
</pre>
 +
 +
= Aircraft Positions =
 +
 +
You can define as many number of aircraft as you need for the session. Be aware that simulating an aircraft probably needs more concentration than controlling them. To define an aircraft you should define the starting position and altitude:
 +
 +
<pre>
 +
@&lt;transponder flag&gt;:&lt;callsign&gt:&lt;squawk code&gt;:1:&lt;latitude&gt;:&lt;longitude&gt;:&ltaltitude&gt;:0:&ltheading&gt:0
 +
</pre>
 +
 +
Where
 +
* transponder flag can be N for normal or S for stand by transponder mode
 +
* latitude and longitude can be the format found in the sectorfile or simple double values
 +
* do not forget the static 1 at the 4th position and the three static 0 values at the end (they are there for some technical reasons only)
 +
* the heading value is a bit complicated, use the requested heading in degrees and use the following formula to decide the value to be put here: ((int) ( Heading * 2.88 + 0.5 )) << 2 ) - or if it is easier: ( Heading * 2.88 + 0.5 ) * 4.
 +
 +
Examples:
 +
 +
<pre>
 +
@N:MAH661:2622:1:N048.10.38.498:E018.10.36.537:15000:0:0:0
 +
@N:MAH1501:2632:1:46.793880004674:17.795807317989:17000:312:4192376:450
 +
@N:AZA525:2606:1:N047.26.41.961:E019.15.29.777:550:0:0:0
 +
</pre>
 +
 +
= Flight Plans =
 +
 +
Every aircraft position line should follow a flight plan line. Do not change the order as EuroScope can save the flight plan only for aircraft with position. The flight plan line looks like this:
 +
 +
<pre>
 +
$FP&lt;callsign&gt;:*A:&lt;flight plan type&gt;:&lt;aircraft type&gt;:&lt;true air speed&gt;:&lt;origin airport&gt;:
 +
  &lt;departure time EST&gt;:&lt;departure time ACT&gt;:&lt;final cruising altitude&gt;:&lt;destination airport&gt;:
 +
  &lt;HRS en route&gt;:&lt;MINS en route&gt;:&lt;HRS fuel&gt;:&lt;MINS fuel&gt;:
 +
  &lt;alternate airport&gt;:&lt;remarks&gt;:&lt;route&gt;#
 +
</pre>
 +
 +
Where ''flight plan type'' can be '''I''' or '''V'''. Do not forget the static '''*A''' from the second place. I think that the rest stands for the content.
 +
Examples:
 +
 +
<pre>
 +
$FPMAH661:*A:I:B736:370:EHAM:1720:1720:390:LHBP:1:40:2:23:LOWW:/V/:ARNEM UL620 BIRKA UZ21 OMELO UL620 KOPIT UM748 RUTOL
 +
$FPMAH1501:*A:I:B738:430:GCTS:1730:1730:340:LHBP:1:20:2:0:LOWW:/V/:KORAL UG5 ESS UN871 VJF UN851 MHN UM603
 +
  ALG UL5 VALMA UL865 ANC UM986 KOPRY UY53 VEBOS
 +
$FPAZA525:*A:I:MD87:430:LHBP:1730:1730:360:LIMC:1:20:2:0:LIRF:/V/:BAKOT UY52 SUNIS Q114 GRZ UP976 DETSA UM984 LUSIL
 +
</pre>
 +
 +
 +
= Route Description =
 +
 +
After the flight plan you should place a route description. The route is a point by point list of the route the plane should follow. It should not contain any information just the list of the waypoints. The original format is still available:
 +
 +
<pre>
 +
$ROUTE:&lt;callsign&gt;:&lt;point by point route&gt;[:&lt;start&gt;][:&lt;pilot minimum delay&gt;][:&lt;pilot maximum delay&gt;][:&lt;descend to waypoint&gt;:&lt;descend to altitude&gt;]
 +
</pre>
 +
 +
The ''start'' value here is a wait time in minutes after that the aircraft will be added to the simulation. This is an optional parameter. If you omit a '''0''' will be used that means join immediately. The delay is calculated on simulation time only. When the whole simulation is paused then the delay time is not counted further down.
 +
 +
The ''pilot minimum'' and ''maximum delay'' determines how fast the pilot will respond to an order. For every order you make in the simulation the aircraft will respond and start following it by random seconds of time between the minimum and the maximum value. The minimum is between 1 and 30, the maximum is between 2 and 31 seconds. If you omit these parameters then a minimum 12 and maximum 17 seconds will be used that were measured by real-life controllers as average response time.
 +
The ''descend to waypoint'' and the ''descend to altitude'' parameters are used to setup an initial descent for the arrival planes. That makes the trainer life easier as the initial values should not be set for every plane. The planes with specified descend to values will reach the altitude at the given point.
 +
 +
Examples:
 +
 +
<pre>
 +
$ROUTE:MAH661:RUTOL BP523 MAMOS BP522 BP521 BP520 BP519 BP518 BP512 BP416 BP415 BP414 BP413 BP049
 +
$ROUTE:MAH1501:VEBOS BP421 BP420 BP419 BP418 BP417 BP416 BP415 BP414 BP413 BP049:0:15:20
 +
$ROUTE:AZA525:BP713 MNR BP612 BP610 BP614 BAKOT SIRDU SUNIS:10:5:10
 +
$ROUTE:MAH663:RUTOL BP523 MAMOS BP522 BP521 BP520 BP519 BP518 BP512 BP416 BP415 BP414 BP413 BP049:10:5:10:RUTOL:19000
 +
</pre>
 +
 +
You can also split the ROUTE line into several lines. The callsign can be omitted and all the parameters from the end of the line can be put in subsequent lines.
 +
 +
<pre>
 +
$ROUTE:ABONY AGMAS BP539 TPS BP538 BP537 BP536
 +
START:2
 +
DELAY:2:5
 +
REQALT:ABONY:12000
 +
</pre>
 +
 +
= Aircraft Performance Data =
 +
 +
EuroScope already contains performance data file for several planes (A124, A30B, A306, A310, A318, A319, A320, A321, A332, A333, A342, A343, A345, A346, A3ST, A748, AAS, AC11, AC6T, AC90, AC95, AEST, AJET, AN12, AN24, AN26, AN72, AN74, AS32, ASTR, AT43, AT45, AT72, ATLA, ATP, B190B350, B461, B462, B463, B52, B703, B712, B721, B722, B732, B733, B734, B735, B736, B737, B738, B739, B741, B742, B743, B744, B74S, B752, B753, B762, B763, B764, B772, B773, BA11, BE10, BE20, BE30, BE33, BE36, BE40, BE50, BE55, BE58, BE60, BE76, BE95, BE99, BE9L, BE9T, BN2, BN2P, BN2T, C5, C12, C17, C130, C135, C141, C160, C172, C182, C206, C208, C210, C25A, C25B, C295, C303, C30J, C310, C340, C404, C414, C421, C425, C441, C500, C501, C510, C525, C550, C551, C560, C56X, C650, C680, C72R, C750, CL30, CL60, CN35, CRJ1, CRJ2, CRJ7, CRJ9, CVLT, D228, D328, DA42, DC3, DC6, DC85, DC86, DC87, DC9, DC93, DC94, DC10, DHC6, DHC7, DH8A, DH8B, DH8C, DH8D, E3TF, E3CF, E6, E110, E120, E121, E135, E145, E170, E195, EC35, F15, F16, F18, F117, F27, F28, F50, F70, F100, F406, FA10, FA20, FA50, F900, F2TH, G150, G159, G222, GA7, GALX, GL5T, GLEX, GLF2, GLF3, GLF4, GLF5, GY80, HARR, HAWK, H25A, H25B, H25C, H47, IL62, IL76, IL96, J328, JAGR, JS20, JS31, JS32, JS41, K35E, K35R, KC10, L101, L188, L410, LJ24, LJ31, LJ35, LJ45, LJ55, LJ60, M20P, M20T, MD11, MD80, MD81, MD82, MD83, MD87, MD88, MD90, MU2, MU30, NIM, P3, P68, P180, PA24, PA27, PA28, P28A, P28R, P28T, PA30, P31T, PA31, PA32, P32R, P32T, PA34, PA44, PA46, P46T, PAY1, PAY2, PAY3, PAY4, PC7, PC9, PC12, PRM1, RJ70, RJ85, RJ1H, S601, SB20, SBR1, SF34, SH33, SH36, SR20, SR22, SW2, SW3, SW4, T134, T154, T204, TBM7, TOR, TRIN, TRIS, TUCA, VC10, YK42) hidden in the code.
 +
 +
But you are able to override the default values and define planes not listed above. Use the following lines. The first line defines the type name. The next lines describe the capabilities. After the PERFLINE you must specify the following values: flight level, climb IAS, cruise IAS, descent IAS, climb Mach, cruise Mach, descent Mach, max climb rate, max descent rate.
 +
 +
<pre>
 +
PERFAC:B737
 +
PERFLINE:030:230:230:210:0:0:0:3700:1600
 +
PERFLINE:050:250:250:210:0:0:0:3600:1600
 +
PERFLINE:100:250:250:250:0:0:0:3400:1600
 +
PERFLINE:150:280:280:280:0:0:0:3000:1700
 +
PERFLINE:200:280:280:280:0:0:0:2600:1800
 +
PERFLINE:250:280:280:280:0:0:0:2300:2400
 +
PERFLINE:300:0:0:0:078:079:078:1500:2400
 +
PERFLINE:350:0:0:0:078:079:078:1100:2900
 +
PERFLINE:400:0:0:0:078:079:078:800:2800
 +
</pre>
 +
 +
{{Euroscope_manual}}

Версия 16:05, 19 января 2010

Wiki avsim 2.jpg Это незавершённая статья. Вы можете помочь проекту, исправив и дополнив её.

Файл

Файл сценария - это обычный текстовый файл. Вы можете редактировать его с помощью любого текстового редактора или с помощью специального редактора, такого как Aircraft Situation Editor. Файл считывается линия за линией. В нем нету разделов и Вы можете перемешивать разные типы строк. Единственное исключение, это позиции ВС, после которых должны следовать строки с полетным планом и с маршрутом.

ILS/Runway Definitions

You can define four active runway for one session. It can be defined as an ILS: 

ILS<runway name>:<threshold latitude>:<threshold longitude>:<runway heading>

The name of the runway will be shown in the four buttons. An example line: 

ILS31r:N047.25.24.615:E019.17.35.260:310

Holding Definitions

You can define as many number of holding patterns as you need. The definition line is the following: 

HOLDING:<fix name>:<inbound course>:<direction>

Where fix name can be anything (VOR, NDB, FIX) from the sectorfile. The direction can be 1 to indicate a right turn and -1 for a left turn. Here are some examples: 

HOLDING:AGMAS:310:1
HOLDING:MAMOS:130:-1
HOLDING:VEBOS:95:-1
HOLDING:TPS:160:-1


Airport Altitude

It is a single line definition: 

AIRPORT_ALT:<altitude>


An example: 

AIRPORT_ALT:550

Controllers Definitions

There can be an unlimited number of simulated controllers in the simulation session. They also can be configured in the scenario file: 

CONTROLLER:<callsign>:<frequency>

An example: 

CONTROLLER:LHCC_CTR:133.2
CONTROLLER:LHBP_TWR:118.1

Aircraft Positions

You can define as many number of aircraft as you need for the session. Be aware that simulating an aircraft probably needs more concentration than controlling them. To define an aircraft you should define the starting position and altitude: 

@<transponder flag>:<callsign&gt:<squawk code>:1:<latitude>:<longitude>:&ltaltitude>:0:&ltheading&gt:0

Where

  • transponder flag can be N for normal or S for stand by transponder mode
  • latitude and longitude can be the format found in the sectorfile or simple double values
  • do not forget the static 1 at the 4th position and the three static 0 values at the end (they are there for some technical reasons only)
  • the heading value is a bit complicated, use the requested heading in degrees and use the following formula to decide the value to be put here: ((int) ( Heading * 2.88 + 0.5 )) << 2 ) - or if it is easier: ( Heading * 2.88 + 0.5 ) * 4.

Examples: 

@N:MAH661:2622:1:N048.10.38.498:E018.10.36.537:15000:0:0:0
@N:MAH1501:2632:1:46.793880004674:17.795807317989:17000:312:4192376:450
@N:AZA525:2606:1:N047.26.41.961:E019.15.29.777:550:0:0:0

Flight Plans

Every aircraft position line should follow a flight plan line. Do not change the order as EuroScope can save the flight plan only for aircraft with position. The flight plan line looks like this: 

$FP<callsign>:*A:<flight plan type>:<aircraft type>:<true air speed>:<origin airport>:
   <departure time EST>:<departure time ACT>:<final cruising altitude>:<destination airport>:
   <HRS en route>:<MINS en route>:<HRS fuel>:<MINS fuel>:
   <alternate airport>:<remarks>:<route>#

Where flight plan type can be I or V. Do not forget the static *A from the second place. I think that the rest stands for the content. Examples: 

$FPMAH661:*A:I:B736:370:EHAM:1720:1720:390:LHBP:1:40:2:23:LOWW:/V/:ARNEM UL620 BIRKA UZ21 OMELO UL620 KOPIT UM748 RUTOL
$FPMAH1501:*A:I:B738:430:GCTS:1730:1730:340:LHBP:1:20:2:0:LOWW:/V/:KORAL UG5 ESS UN871 VJF UN851 MHN UM603
   ALG UL5 VALMA UL865 ANC UM986 KOPRY UY53 VEBOS
$FPAZA525:*A:I:MD87:430:LHBP:1730:1730:360:LIMC:1:20:2:0:LIRF:/V/:BAKOT UY52 SUNIS Q114 GRZ UP976 DETSA UM984 LUSIL


Route Description

After the flight plan you should place a route description. The route is a point by point list of the route the plane should follow. It should not contain any information just the list of the waypoints. The original format is still available: 

$ROUTE:<callsign>:<point by point route>[:<start>][:<pilot minimum delay>][:<pilot maximum delay>][:<descend to waypoint>:<descend to altitude>]

The start value here is a wait time in minutes after that the aircraft will be added to the simulation. This is an optional parameter. If you omit a 0 will be used that means join immediately. The delay is calculated on simulation time only. When the whole simulation is paused then the delay time is not counted further down.

The pilot minimum and maximum delay determines how fast the pilot will respond to an order. For every order you make in the simulation the aircraft will respond and start following it by random seconds of time between the minimum and the maximum value. The minimum is between 1 and 30, the maximum is between 2 and 31 seconds. If you omit these parameters then a minimum 12 and maximum 17 seconds will be used that were measured by real-life controllers as average response time. The descend to waypoint and the descend to altitude parameters are used to setup an initial descent for the arrival planes. That makes the trainer life easier as the initial values should not be set for every plane. The planes with specified descend to values will reach the altitude at the given point.

Examples: 

$ROUTE:MAH661:RUTOL BP523 MAMOS BP522 BP521 BP520 BP519 BP518 BP512 BP416 BP415 BP414 BP413 BP049
$ROUTE:MAH1501:VEBOS BP421 BP420 BP419 BP418 BP417 BP416 BP415 BP414 BP413 BP049:0:15:20
$ROUTE:AZA525:BP713 MNR BP612 BP610 BP614 BAKOT SIRDU SUNIS:10:5:10
$ROUTE:MAH663:RUTOL BP523 MAMOS BP522 BP521 BP520 BP519 BP518 BP512 BP416 BP415 BP414 BP413 BP049:10:5:10:RUTOL:19000

You can also split the ROUTE line into several lines. The callsign can be omitted and all the parameters from the end of the line can be put in subsequent lines. 

$ROUTE:ABONY AGMAS BP539 TPS BP538 BP537 BP536
START:2
DELAY:2:5
REQALT:ABONY:12000

Aircraft Performance Data

EuroScope already contains performance data file for several planes (A124, A30B, A306, A310, A318, A319, A320, A321, A332, A333, A342, A343, A345, A346, A3ST, A748, AAS, AC11, AC6T, AC90, AC95, AEST, AJET, AN12, AN24, AN26, AN72, AN74, AS32, ASTR, AT43, AT45, AT72, ATLA, ATP, B190B350, B461, B462, B463, B52, B703, B712, B721, B722, B732, B733, B734, B735, B736, B737, B738, B739, B741, B742, B743, B744, B74S, B752, B753, B762, B763, B764, B772, B773, BA11, BE10, BE20, BE30, BE33, BE36, BE40, BE50, BE55, BE58, BE60, BE76, BE95, BE99, BE9L, BE9T, BN2, BN2P, BN2T, C5, C12, C17, C130, C135, C141, C160, C172, C182, C206, C208, C210, C25A, C25B, C295, C303, C30J, C310, C340, C404, C414, C421, C425, C441, C500, C501, C510, C525, C550, C551, C560, C56X, C650, C680, C72R, C750, CL30, CL60, CN35, CRJ1, CRJ2, CRJ7, CRJ9, CVLT, D228, D328, DA42, DC3, DC6, DC85, DC86, DC87, DC9, DC93, DC94, DC10, DHC6, DHC7, DH8A, DH8B, DH8C, DH8D, E3TF, E3CF, E6, E110, E120, E121, E135, E145, E170, E195, EC35, F15, F16, F18, F117, F27, F28, F50, F70, F100, F406, FA10, FA20, FA50, F900, F2TH, G150, G159, G222, GA7, GALX, GL5T, GLEX, GLF2, GLF3, GLF4, GLF5, GY80, HARR, HAWK, H25A, H25B, H25C, H47, IL62, IL76, IL96, J328, JAGR, JS20, JS31, JS32, JS41, K35E, K35R, KC10, L101, L188, L410, LJ24, LJ31, LJ35, LJ45, LJ55, LJ60, M20P, M20T, MD11, MD80, MD81, MD82, MD83, MD87, MD88, MD90, MU2, MU30, NIM, P3, P68, P180, PA24, PA27, PA28, P28A, P28R, P28T, PA30, P31T, PA31, PA32, P32R, P32T, PA34, PA44, PA46, P46T, PAY1, PAY2, PAY3, PAY4, PC7, PC9, PC12, PRM1, RJ70, RJ85, RJ1H, S601, SB20, SBR1, SF34, SH33, SH36, SR20, SR22, SW2, SW3, SW4, T134, T154, T204, TBM7, TOR, TRIN, TRIS, TUCA, VC10, YK42) hidden in the code.

But you are able to override the default values and define planes not listed above. Use the following lines. The first line defines the type name. The next lines describe the capabilities. After the PERFLINE you must specify the following values: flight level, climb IAS, cruise IAS, descent IAS, climb Mach, cruise Mach, descent Mach, max climb rate, max descent rate. 

PERFAC:B737
PERFLINE:030:230:230:210:0:0:0:3700:1600
PERFLINE:050:250:250:210:0:0:0:3600:1600
PERFLINE:100:250:250:250:0:0:0:3400:1600
PERFLINE:150:280:280:280:0:0:0:3000:1700
PERFLINE:200:280:280:280:0:0:0:2600:1800
PERFLINE:250:280:280:280:0:0:0:2300:2400
PERFLINE:300:0:0:0:078:079:078:1500:2400
PERFLINE:350:0:0:0:078:079:078:1100:2900
PERFLINE:400:0:0:0:078:079:078:800:2800
Руководство по EuroScope
Быстрое начало работы Быстрое начало Установка Где сохраняются настройки
После подключения Подключение Настройки подключения Настройка голосовой связи Настройка оборудования для голосовой связи Скачивание файлов секторов Голосовой ATIS Voice alias Особенности подключения
Некоторые детали Симуляция проф. радиолокатора
Радарный экран Экран Панель меню Основные списки Продвинутые списки
Формуляры Формуляр сопровождения Редактор формуляров
Настройки Связь между диспетчерами Основные настройки Меню символов Plug-ins
Тренажер Тренажер
Приложения Описание ESE файла Файл сценария
Источник — «https://www.avsim.su/w/index.php?title=Файл_сценария&oldid=3737»