For all the questions which I reeled off at the end, goto and bookmark. If you’re having questions on installing planes, you’ll soon wonder about scenery, painting your planes, why there’s a extra person sitting in your cockpit in certain planes, why is my framerate slow, what GPUs are… (Note, I’ve not yet run out of questions or answers in over 6 months of reading and using FlightGear. I would first start here: - this is the getting started/ FlightGear manual. Now, without this sounding like I’m just being hard to get along with, and hopefully the fact I took the time to explain your question will go to that, I urge, beg of, plead with you to read, read, read, the documentation, wiki’s, etc. To do the latter, from the initial screen, choose “Advanced Features”, then select the “Others” tab and, finally, at the bottom of that screen, select “Install Addon Data”. Either use the “Browse Application Settings” and copy the aircraft folder to the appropriate location or use the FlightGear Application. Once you have it on the Mac, you have 2 choices.
Right image: You add the VOR (radial 250).To download - simply pick an aircraft from above and download the zip file to your Mac.Left image: ILS localizer and NDB (radial 250).In the two following screenshots, you use more than one navaid. On the extended runway, apart from the ILS localizer, there are also the VOR Frankfurt FFM and the NDB Frankfurt FR. In the following example you approach runway 25R at EDDF from southwest. The thick dot in their center is the beginning of the runway. ILS appear in the same way as VORs, as blue or green arrows.
Fly a little to the right to align both arrows: The NDB is at a heading of approximately 267 from you (long arrow), but you want to approach it at a radial of 250 (short arrow). The short arrow indicates the radial you defined in the radio settings dialogue. tells you where the NDB is relative to you. The long one points in the direction of the NDB, i.e. Note that there is traffic at your 5 o'clock. In the following screenshot, a VOR, for which you have set a radial of 080, is 10 nm away from you and you are flying directly to it. In the 737-400, when are 20 nm or closer, the VOR will show up on the screen. They point in the direction of the radial you defined in the radio settings (Equipment -> Radio Settings). VOR arrows (vectors) are blue if in NAV1 and green if in NAV2. The next waypoint is displayed on the screen as a yellow dot. The total distance to the last waypoint is 31.9 nm. The distance to the next waypoint OMOGI is 13.5 nm. Once route is programmed, it's displayed in the middle console. A voice will say "TCAS system test okay".įor example, I have set up the Route Manager to follow the fixes OMOGI, OKAVO, AKONI and OBERO. (This screenshot was taken at an airport.) Blue triangles: Other multiplayer pilots. Each bar on the white line in the middle marks 5nm. The TCAS ( Traffic Alert and Collision Avoidance System) displays other aircraft on the main screen. You can set almost all frequencies and Autopilot settings from the 3D cockpit, and very detailed information is given back to you on the screens and instruments. press "?" or "Help -> Aircraft Help" when the simulation is running.Īs far as I know, out of all airliners the 737-400 has the best modelled navigation panels available in FlightGear.
For information on engine startup, livery selection, auto brake, reject take off etc.