265
edits
ATC-pie user guide: Difference between revisions
r10h
Mickybadia (talk | contribs) (Version update + new tutorial video reference) |
Mickybadia (talk | contribs) (r10h) |
||
| Line 244: | Line 244: | ||
Background images allow to decorate radar scopes with all sorts of maps and useful information about the airspace, terrain or procedures. | Background images allow to decorate radar scopes with all sorts of maps and useful information about the airspace, terrain or procedures. | ||
There are two ways to add images to the radar background. One is to | There are two ways to add images to the radar background. One is to '''import pictures''' (pixmap files like JPEG or PNG, including transparency); the other is to write '''text drawing specification''' files to paint coloured lines and labelled points. This allows to import anything from the most complex coloured height map to the the most schematic airspace outline. All pictures and drawing points are positioned with lat/lon coordinates or navpoint names in map range. The <code>resources/bg-img/Notice</code> file explains how to import and draw background images. | ||
For example, you can map out SID | For example, you can map out procedures (SID, STAR, IAD...), grouping them by associated runways. Drawings are generally appropriate for that because they allow referring to named points as per the published procedures and avoid manual positioning. But if you want more than schematic line plots, you should create the picture yourself. Using an image processing tool like ''GIMP'', superimpose a transparent layer on top of a real map canvas, or over a screenshot of your ATC-pie radar with pinned navaids as landmarks, and freely decorate your picture. | ||
ATC-pie comes with | ATC-pie comes with a handful of '''helper tools''' to create or import background images: | ||
# The "download OSM background" option facilitates [[OpenStreetMap]] | # Located in the ''System'' menu, the "image positioning helper" allows to move and resize imported pictures, adjusting the corners visually rather than programmatically if you have no specification for them. All visible pixmap images will be moved simultaneously, so you can work with several at a time if you want to. On dialog box close, a file is generated in the <code>output</code> directory for you to copy from. | ||
# | # The "download OSM background" option facilitates map retrieval from the [[OpenStreetMap]] still image server. After specifying corners and a scale, a PNG map will be generated in the <code>output</code> directory for you to import. Caution: downloads can fail for large images; try reducing the requested size or resolution in such case. Also, the server is rather limited so make parsimonious use of it. | ||
# If you have a sector file for your area (.sct), the <code>sectorExtract.py</code> script will translate the contained diagrams into ATC-pie drawings. While the generated files always require some post-editing, it is generally the best option for things like SID/STAR diagrams. See the <code>README</code> file for a description. | |||
=== Text chat === | === Text chat === | ||
| Line 287: | Line 287: | ||
* global settings (all other entries): saved and restored regardless of location or game mode, e.g. preset text chat messages. | * global settings (all other entries): saved and restored regardless of location or game mode, e.g. preset text chat messages. | ||
You can '''customise the radar colours''' by editing the colour codes in the <code>settings/colours.ini</code> file generated on first run. | You can '''customise the radar & strip colours''' by editing the colour codes in the <code>settings/colours.ini</code> file generated on first run. | ||
'''Heading displays''' are mostly magnetic so they can be read out to pilots. The only exceptions perhaps are the navigator and handover list tooltips, for easier human identification on the scope. All directions are geodesic. | '''Heading displays''' are mostly magnetic so they can be read out to pilots. The only exceptions perhaps are the navigator and handover list tooltips, for easier human identification on the scope. All directions are geodesic. | ||
The grouped diamond and tick marks along the '''landing helper lines''' indicate best altitudes AMSL for final approach along the configured flight path angle: diamond marks read 5,000 ft each; every other tick mark is 1,000 ft. | |||
A <code>*</code> symbol in front of a strip callsign means that a comment is entered on the strip. Open the detail sheet to view, or hover the strip with your mouse to show it as a tool tip. | |||
The '''transition level''' displayed in the weather analysis is the lowest flight level that is still above the transition altitude. This does not mean the lowest to be expected in ATC clearances, which may be higher, for more vertical separation on either side of the transition layer or due to coordination with neighbouring zones and fields. | The '''transition level''' displayed in the weather analysis is the lowest flight level that is still above the transition altitude. This does not mean the lowest to be expected in ATC clearances, which may be higher, for more vertical separation on either side of the transition layer or due to coordination with neighbouring zones and fields. | ||
=== Radio communications === | === Radio communications === | ||