265
edits
ATC-pie user guide: Difference between revisions
Jump to navigation
Jump to search
v1.3.4
Mickybadia (talk | contribs) No edit summary |
Mickybadia (talk | contribs) (v1.3.4) |
||
| Line 1: | Line 1: | ||
{{forum|83|ATC-Pie support & development}} | {{forum|83|ATC-Pie support & development}} | ||
This article is a guide to | This article is a guide to '''[[ATC-pie]]''', describing some of its major features. A more exhaustive list can be found in the main article. For download and installation help, refer to the [[ATC-pie installation guide|installation guide]]. | ||
Anyone motivated to write a full user guide is obviously welcome to contact the developer, or improve this article. For support and troubleshooting, the [[ATC-pie FAQ]] might get you an answer first. Otherwise kindly ask on the FlightGear forum, where we have a dedicated sub-forum, so the discussion is public and its contents shared. | |||
Other sources to learn the program are: | Other sources to learn the program are: | ||
| Line 7: | Line 9: | ||
* the in-app '''quick reference''' available from the ''Help'' menu (summary of mouse/keyboard gestures, display conventions...); | * the in-app '''quick reference''' available from the ''Help'' menu (summary of mouse/keyboard gestures, display conventions...); | ||
* to '''play solo'''! | * to '''play solo'''! | ||
== Flight strips == | == Flight strips == | ||
| Line 52: | Line 52: | ||
There are two ways of activating a tower view. You may let ATC-pie start its own suitably configured FlightGear process, or have it connect to an external viewer, manually set up and accepting connections. | There are two ways of activating a tower view. You may let ATC-pie start its own suitably configured FlightGear process, or have it connect to an external viewer, manually set up and accepting connections. | ||
'''Running internally''' only requires FlightGear installed on your computer. A basic installation is enough, but you will need the [[scenery]] for your airport if you want anything exciting to see (and not sea!) | '''Running internally''' only requires FlightGear installed on your computer. A basic installation is enough, but you will need the [[scenery]] for your airport if you want anything exciting to see (and not sea!). Also, aircraft will only be drawn properly if the appropriate [[Aircraft|models]] are available. In multi-player, the models required are those flown by the players. For simulated aircraft (AI traffic in solo games and teacher-controlled aircraft), read about <code>icao2fgfs</code> in <code>resources/acft/Notice</code> to understand how ATC-pie chooses models and liveries for its viewers. Aircraft and scenery locations can be filled in the ''System'' settings dialog if they are not in your [[$FG_ROOT|FlightGear root directory]]. | ||
Connecting to an '''external viewer''' allows to run FlightGear on a different machine and thereby relieve your session from the CPU load a local instance induces. If you want to do so, get a hint of the required positioning options you should start your viewer with, from the tower view tab in the system settings dialog | Connecting to an '''external viewer''' allows to run FlightGear on a different machine and thereby relieve your session from the CPU load a local instance induces. If you want to do so, get a hint of the required positioning options you should start your viewer with, from the tower view tab in the system settings dialog. Of course, scenery, models and liveries must also be available to the running process. | ||
In either case, once activated from the ''View'' menu, the tower view '''control pane''' is enabled, from which you can turn to runway points, follow selected aircraft... Direct FlightGear input in the view window is also possible: right click and drag allows to look around, <code>x</code>/<code>X</code> keys change the zoom level, etc. | In either case, once activated from the ''View'' menu, the tower view '''control pane''' is enabled, from which you can turn to runway points, follow selected aircraft... Direct FlightGear input in the view window is also possible: right click and drag allows to look around, <code>x</code>/<code>X</code> keys change the zoom level, etc. | ||
=== Additional scene views === | === Additional scene views === | ||
You can connect '''additional viewers''' to your session, for example placed around your airport for exciting camera footage of challenging landings. You will not be able to control those viewers from ATC-pie like the tower viewer, but you will be able to activate/stop the connection | You can connect '''additional viewers''' to your session, for example placed around your airport for exciting camera footage of challenging landings. You will not be able to control those viewers from ATC-pie like the tower viewer, but you will be able to activate/stop the connection from the ''View'' menu. Additional viewers are registered by their host+port address, from the ''View'' menu at run-time or from a custom settings file (see <code>settings/Notice</code>), read at start-up and on explicit reload (''System'' menu). | ||
Every such viewer registered on host ''XXX'' and port ''YYY'' should be running on ''XXX'' and started with options <code>--multiplay=out,TTT,HHH,PPP</code> and <code>--multiplay=in,TTT,,YYY</code>, where: | Every such viewer registered on host ''XXX'' and port ''YYY'' should be running on ''XXX'' and started with options <code>--multiplay=out,TTT,HHH,PPP</code> and <code>--multiplay=in,TTT,,YYY</code>, where: | ||
| Line 222: | Line 222: | ||
* in OpenRadar, a handover must be acknowledged by the receiver for the sender to lose ownership and for all neighbouring OpenRadar users to see the handover complete, whereas ATC-pie considers that a strip sent through the hand-over pipe is gone and should land directly on a receiver's rack at the other end, without anybody else necessarily to know. | * in OpenRadar, a handover must be acknowledged by the receiver for the sender to lose ownership and for all neighbouring OpenRadar users to see the handover complete, whereas ATC-pie considers that a strip sent through the hand-over pipe is gone and should land directly on a receiver's rack at the other end, without anybody else necessarily to know. | ||
For most interactions to work while still respecting both philosophies as much as possible, the following principles and restrictions | For most interactions to work while still respecting both philosophies as much as possible, the following principles and restrictions apply: | ||
* ATC-pie users can only hand over strips that are linked to a radar contact (no lone strip can be sent); | * ATC-pie users can only hand over strips that are linked to a radar contact (no lone strip can be sent); | ||
* aircraft under ATC-pie control are not shown as "owned" to OpenRadar users; | * aircraft under ATC-pie control are not shown as "owned" to OpenRadar users; | ||
* handovers from ATC-pie | * handovers from ATC-pie will fail if an OpenRadar user is claiming ownership on the linked radar contact; | ||
* when sending to ATC-pie controllers, OpenRadar users will see their transfers acknowledged straight away, unconditionally. | * when sending to ATC-pie controllers, OpenRadar users will see their transfers acknowledged straight away, unconditionally. | ||