265
edits
ATC-pie user guide: Difference between revisions
Jump to navigation
Jump to search
no edit summary
Mickybadia (talk | contribs) (v1.3.1) |
Mickybadia (talk | contribs) No edit summary |
||
| 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 | '''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!), and to fill its location in the ''System'' settings dialog if it is not in your [[$FG_ROOT|FlightGear root directory]]. Also, aircraft will only be drawn properly if you have the appropriate [[Aircraft|models]] installed. In multi-player, the models required are those flown by the players. For simulated aircraft (e.g. traffic in solo games), read the <code>resources/acft</code> notice file section about <code>icao2fgfs</code> to understand how ATC-pie chooses models for its viewers. Initially included are a few ugly substitutions like B772 for A320 to avoid light installations to miss out on planes. But you can edit the file and use your own models. | ||
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. More options should also be considered, e.g. <code>--fdm=null</code>. Of course, scenery, models and liveries must also be available to the running process. | 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. More options should also be considered, e.g. <code>--fdm=null</code>. Of course, scenery, models and liveries must also be available to the running process. | ||