1
0
Fork 0
No description
Find a file
2022-01-24 20:43:30 +00:00
.github/ISSUE_TEMPLATE Also request A320 version for bug reports 2021-07-26 16:05:18 +00:00
AircraftConfig Rewrite rendering warning 2022-01-14 16:35:42 +00:00
Engines Merge pull request #116 from legoboyvdlp/APU 2020-04-19 14:33:26 +00:00
Fonts Add OVERFLY function 2022-01-12 11:53:57 +00:00
gui Add OVERFLY function 2022-01-12 11:53:57 +00:00
Models Better long pressed CLR and check numeric format on plus/minus 2022-01-24 21:14:17 +01:00
Nasal Better long pressed CLR and check numeric format on plus/minus 2022-01-24 21:14:17 +01:00
Sounds Switches and options (#262) 2022-01-07 13:43:55 +00:00
Splash New splash screen by SXSA 2020-05-31 18:07:07 +01:00
Systems Don't comment out - better to remove it entirely 2022-01-24 20:43:30 +00:00
WebPanel web MCDU adtapt for new keys: OVFY. PLUSMINUS 2022-01-16 21:26:07 +01:00
.gitignore Fix entabing 2020-02-09 13:12:22 -05:00
A32X-Checklists.xml Whitespace 2020-05-10 12:25:36 +01:00
A320-100-CFM-set.xml Sound should also run at framerate as well 2021-02-08 16:14:41 +00:00
A320-100-CFM.xml Experimental cockpit oxygen system 2021-07-29 13:19:27 +01:00
A320-200-CFM-set.xml Sound should also run at framerate as well 2021-02-08 16:14:41 +00:00
A320-200-CFM.xml Experimental cockpit oxygen system 2021-07-29 13:19:27 +01:00
A320-200-IAE-set.xml Sound should also run at framerate as well 2021-02-08 16:14:41 +00:00
A320-200-IAE.xml Experimental cockpit oxygen system 2021-07-29 13:19:27 +01:00
A320-main.xml DATA / STATUS pages - cleanup with new font 2022-01-15 17:57:41 +00:00
A320neo-CFM-set.xml Sound should also run at framerate as well 2021-02-08 16:14:41 +00:00
A320neo-CFM.xml Experimental cockpit oxygen system 2021-07-29 13:19:27 +01:00
A320neo-PW-set.xml Sound should also run at framerate as well 2021-02-08 16:14:41 +00:00
A320neo-PW.xml Experimental cockpit oxygen system 2021-07-29 13:19:27 +01:00
Announcements.txt Merge changes to cabin alert (#194) 2020-11-20 17:27:49 +00:00
checklist.pdf Added printable checklist 2020-04-18 23:26:34 +00:00
CODE_OF_CONDUCT.md Code of Conduct 2019-10-19 12:23:39 +01:00
CONTRIBUTING.md Update README / CONTRIBUTING 2020-08-28 12:26:50 +01:00
INSTALL.md Update install.md to new link 2020-05-18 00:31:13 +01:00
LICENSE A320-family fork 2019-10-14 12:48:35 -04:00
PULL_REQUEST_TEMPLATE.md Remove ready to merge checkbox, replace with draft pull request. 2021-03-11 11:53:05 -05:00
README.md Commented out wabpro link in README 2021-07-27 15:57:16 +00:00
revision.txt VC: Fix mistake in rmp in the last commit 2021-12-10 11:33:34 -05:00
THANKS.md Add new font from MSFS2020 FBW team (GPL) 2021-12-05 17:46:12 +00:00
thumbnail.jpg New thumbnail 2019-10-19 13:37:02 +01:00

A320-family

A very advanced simulation of the Airbus A320 Family for FlightGear.

  • Flight Dynamics: Josh Davidson (Octal450)
  • Systems: Josh Davidson (Octal450), Jonathan Redpath (legoboyvdlp), merspieler, Matthew Maring (mattmaring)
  • Displays: Josh Davidson (Octal450), Jonathan Redpath (legoboyvdlp), merspieler, Matthew Maring (mattmaring)
  • 3D/Textures: Thorsten Herrmann (TH-555), Semir Gebran (CaptB)

Present pack includes the following Airbus A320 Family variants:

  • A320-111
  • A320-214
  • A320-232
  • A320-251N
  • A320-271N

You can find a Checklist to download and print here

Navdata

It is highly reccomended to purchase a NAVIGRAPH subscription and download their level d FMSDATA / waypoint / navaid data! If you do not wish to do that, there is older data linked below. But it won't have most of the newer procedures, and is only for a limited number of airports, as naturally it is not possible to distribute commercial data. If runway numbering changed, it is quite possible that it will not work due to FlightGear limitations in the routing code.

To install navdata, create a folder FMSDATA, and add it to your additional scenery folders, at the top of the list. Inside that folder, place all the XXXX.procedures.xml files, in the format FMSDATA/X/X/X/XXXX.procedures.xml. For instance, FMSDATA/Airports/E/G/K/EGKK.procedures.xml.

Remote MCDU

If you want to run the MCDU on a your smarthphone or tablet for better realism and easier input, run FlightGear with enabled HTTP server (i.e. command line --httpd=<Port; e.g. 8080>) then go to main menu -> Instruments -> Remote MCDU. You can generate a QR-code to lauch directly on your smartphone/tablet, first insert your local ip. Your device must run on the same local network of your computer.

Installation

If you have issues installing, please check INSTALL.MD! Specifically, make sure you remove -dev from the folder name!

External tools

Some external tools you might want to checkout and use with this Model.
NOTE: These are external tools so make sure to check their terms of use