Contents

Program Versions

vasFMC version 2.1 is a completely new program different from version 1.10, and should not be confused.

If you feel that vasFMC is worth it, please donate using the paypal donation button on the vasFMC homepage.

This manual covers the vasFMC version 2.1. Please report bugs to the vasFMC forum.

Overview

vasFMC version 2.1 is a free (for non commercial use, for details see the licence chapter below) Flight Management System (FMS) for Microsoft Flight Simulator (2002, 2004/FS9 and FSX) and X-Plane based on the FMS used in many Airbus models. Some of its features are:


The new features in version 2.1 are:



The following example screenshot shows the vasFMC captain side display in A-Style:

oviewastyle

Licence

Creative Commons License

vasFMC is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
This means, among other things, that vasFMC may not be used for commercial purposes!

If you feel that vasFMC is worth it, please donate using the paypal donation button on the vasFMC homepage.

Navigation Data

The navigation database used by vasFMC is directly supported by Navigraph which updates the data files for each monthly AIRAC cycle. Please see Navigraph for information on obtaining the data. The Navigraph installer will ask for the folder where you installed vasFMC and will install the files in the proper subfolder.

Note that this data is not the same as that used by the built-in MSFS GPS. Real world navigation data changes over time, but the MSFS GPS data format is not supported by Navigraph. This is another good reason to use vasFMC instead of the built-in GPS.

Installation of the Default Navdata

The standard vasFMC installation does not contain any navdata anymore. If you haven't already purchased up-to-date navdata from Navigraph you can download the default navdata from the VAS download site and install them after vasfMC was installed. The default navdata file can be found under the vasFMC 3rd party stuff download category named "Navdata - AIRAC 0609" and must be extracted into the "navdata" directory of your vasFMC installation.

Installation of the Windows Standalone Version (MSFS or XPlane)

vasFMC comes packaged as a standard executable installer. As with any installer, just run the program and follow the prompts.

vasFMC runs as a separate program independently from your flight simulator. To start vasFMC from your Windows start menu, select the vasFMC program group and the vasFMC item within it. If you use multiple monitors putting the vasFMC windows on a separate monitor is a convenient way of having them visible at all times. The window positions will be remembered from the previous placement and will always show up where you place them.

vasFMC communicates with MSFS through the free version of the FSUIPC library. FSUIPC is not included with vasFMC, however it is widely available on flight simulator enthusiast sites as well as from its author at www.schiratti.com/dowson.html. Some features of vasFMC require a registered version of FSUIPC.

Important: The vasFMC installation does not contain any navdata, see Navigation Data for details.

Installation of the MS FS FS9 & FSX Gauge Version

vasFMC comes packaged as a standard executable installer. As with any installer, just run the program and follow the prompts. You must provide the root directory of your MS FS (either FS9 or FSX) to the installer!

During the gauge installation a new folder will be created under your MS FS Aircraft folder: vasfmc_panel_a320. This contains the default vasFMC Airbus panel which uses the vasFMC gauges. Besides the vasFMC gauge version installer you can also find various Project Airbus model downloads on the VAS download page, all of them must be installed into the MS FS aircraft directory and are vasFMC-ready.

If you want to integrate vasFMC into any other aircraft panel you will have to adapt the aircraft.cfg file as follows:

[fltsim]
alias=vasfmc_panel_a320

This is how the gauges are used in vasfmc_panel_a320/panel.cfg:

gauge14=vasfmcgau!pfd, 28,708, 342,342, builtin id10001 a_style
gauge15=vasfmcgau!nd, 436,708, 342,342, builtin id10002 a_style
gauge16=vasfmcgau!uecam, 1160,690, 316,316, builtin id10003 a_style
gauge17=vasfmcgau!fcu, 601,433

The first two extra parameters ("builtin id10001") are necessary to let you left click on the gauge to make the gauge larger. The 3rd extra parameter controls the gauge style and can be either "a_style" or "b_style" (see the ND and PFD chapters for the differences in the two styles). Please note that the styles must not be mixed. The panel.cfg file also has entries for Window04 through Window07 which can be used as guides in building your own panel.

vasFMC communicates with MSFS through the free version of the FSUIPC library. FSUIPC is not included with vasFMC, however it is widely available on flight simulator enthusiast sites as well as from its author at www.schiratti.com/dowson.html. Some features of vasFMC require a registered version of FSUIPC.

Important: The vasFMC installation does not contain any navdata, see Navigation Data for details.

Installation on Mac OSX

Unpack the contents of the .zip-file to any location of your liking. No further installation necessary. vasFMC starts by double-clicking vasfmc.app.

Important: The vasFMC installation does not contain any navdata, see Navigation Data for details.

Installation on Linux

Unpack the contents of the .zip-file to any location in your $home-directory. We do NOT encourage installation in /usr/bin and /usr/lib respectively, as this is not tested. vasFMC is completely self-contained in its folder, breaking up the structure may cause vasFMC to not find navigational data, aircraft performance data and so on.
Start vasFMC by starting the vasfmc.sh shell script from the terminal, not by starting the vasfmc binary itself. For convenience, you can create a desktop shortcut to the shellscript. IMPORTANT: When doing so, it is neccesary to set the vasfmc-folder as "working directory" in which vasfmc.sh starts, otherwise you will get an error because vasFMC cannot find navigational data, performance data, etc.

Important: The vasFMC installation does not contain any navdata, see Navigation Data for details.

Setting up integration in MS Flight Simulator

vasFMC communicates with MSFS via the FSUIPC module which must be obtained and installed separately, see Peter Dowson's FSUIPC. A normal unregistered FSUIPC version will do the job, but if you want to control vasFMC via FSUIPC offsets you must obtain a registered FSUIPC version.

Important for Fly By Wire: If you are using FSUIPC to set up and calibrate your joystick, then it is critical that you use the following settings on the "Axis Assignment" page: For the elevator, use "Send to FS as normal axis" with "Axis Elevator Set". For the ailerons, use "Send to FS as normal axis" with "Axis Ailerons Set". In addition, on the "Joystick Calibration" page, make sure that the null zones for elevator and aileron are large enough so that the "Out" value is always zero when the joystick is in the central position. These settings are important to make sure the fly-by-wire controls work correctly. The other alternatives, i.e. "Send direct to FSUIPC calibration" and/or "Elevator Set" / "Aileron Set" (without the "Axis") will not work.

Setting up integration in X-Plane

vasFMC communicates with X-Plane via Simulator Communication System (SCS). The X-Plane plugin must be downloaded separately from the x-plane.org download manager.

Install the plugin by unpacking the .zip file and moving the scs directory to YOUR_X-PLANE_DIR/Resources/plugins/

Windows
Make sure you have the latest Microsoft Visual C++ 2010 redistributable package installed. If you haven't already, download it from Microsoft.

The vasFMC X-Plane integration is driven by CAN Aerospace technology:   CAN Aerospace

Use on a Remote System for MS Flight Simulator

The standalone version of vasFMC can be run on a separate system by using WideFS.

Be sure to start the simulator before starting vasFMC. Starting these in the wrong order can cause WideFS to consume 99% of the CPU.

Use on a Remote System for X-Plane

In 99.9% of all cases, there is NO further configuration required to run vasFMC over network on a different PC than X-Plane.

vasFMC and the X-Plane plugin communicate via UDP multicast. This works without further configuration, provided your firewalls allow incoming UDP connections. To ensure that, open port 50707 for UDP traffic on the firewalls of all machines you run vasFMC or X-Plane on.

If network connection does not work:
Stoneage network equipment may not be able to distribute multicasts. In that case, it is strongly recommended to upgrade your network infrastructure.

Note for Wireless LANs (WiFi):
The speed and reliability of multicast is dependent on the network stack implementation of your chipset. Transfer rates on the same machine differ extremely running Linux or Windows. Also some wireless access points and routers have problems handling dense UDP multicast traffic.
In case of low transfer rates the vasFMC displays will react slowly and with stuttering and jumping. For optimum results, we strongly recommend the use of a wired ethernet connection between the machines running vasFMC and X-Plane.