ToLiss AirbusA319 V1.3.3 SimulationManual

Simulation Solutions
ToLiss Aeronautical Simulation Solutions
ToLiss Airbus A319 V1.3.3 – Simulation manual

Version 1.3.3 from 2019/08/02
© 2019, ToLiss Inc. This software, digital art work and accompanying manuals are copyrights
and must not be reproduced or distributed without prior written consent from ToLiss Inc.
© Airbus 2019. AIRBUS, its logo and product & service marks are registered trademarks of
Airbus. All rights reserved. Officially licensed by Airbus.
1
Table of Contents
1 Introduction........................................................................................................................4
2 Aircraft installation and Xplane setup ...............................................................................5
2.1 Special requirements in Windows ...................................................................................5
2.2 Special requirements in Linux ........................................................................................6
2.3 Updating .........................................................................................................................6
2.4 Aircraft activation ..........................................................................................................7
2.5 Livery installation...........................................................................................................8
2.6 Alternative cockpit textures ...........................................................................................9
2.7 Joystick setup .................................................................................................................9
2.7.1 Other mapped x-plane commands ........................................................................ 10
2.7.2 Detailled axis setup and status check ................................................................... 11
2.7.3 Custom commands ................................................................................................ 13
2.8 Simulation configuration .............................................................................................. 14
2.8.1 Settings/Actions page ........................................................................................... 14
2.8.2 Audio-visual settings ............................................................................................. 17
2.9 Navigation data – location and update ........................................................................ 20
2.10 IAE sound pack activation ....................................................................................... 22
2.11 Third part add-on compatibility .............................................................................. 22
2.11.1 Smartcopilot use ................................................................................................... 23
2.11.2 System simulation/FMS 3rd party add-ons ........................................................... 23
3 Use of ISCS during the flight ........................................................................................... 24
3.1 Resume from last time.................................................................................................. 24
3.2 Special actions .............................................................................................................. 24
3.3 Situation loading and saving ........................................................................................ 26
3.4 Aircraft loading and TO performance calculation........................................................ 28
3.4.1 Selecting payload .................................................................................................. 28
3.4.2 Selecting fuel load ................................................................................................. 28
3.4.3 CG-GW diagram................................................................................................... 29
3.4.4 TO performance calculator ................................................................................... 29
3.5 Ground services ............................................................................................................ 30
3.5.1 Automatic pushback ............................................................................................. 31
3.5.2 Manual pushback .................................................................................................. 31
3.6 Control of the aircraft doors ......................................................................................... 32
2
3.7 Fault injection interface ............................................................................................... 32

3.7.1 Selection of specific faults ..................................................................................... 33
3.7.2 Random fault injection ......................................................................................... 35
4 Cockpit orientation........................................................................................................... 36
4.1 3d cockpit use ............................................................................................................... 36
4.1.1 Special view commands......................................................................................... 36
4.1.2 Popup displays ...................................................................................................... 37
4.1.3 Display brightness and cockpit illumination......................................................... 39
4.1.4 Mouse wheel use ................................................................................................... 41
4.1.5 FCU operation ...................................................................................................... 42
4.2 2d cockpit use ............................................................................................................... 44
4.2.1 2d cockpit lighting ................................................................................................ 46
4.2.2 FCU use in 2d cockpit .......................................................................................... 47
5 Troubleshooting................................................................................................................ 49
5.1 Aircraft does not load or looks strange after loading ................................................... 49
5.2 System crashes .............................................................................................................. 49
5.3 FMGS path jitter ......................................................................................................... 50
3
1 Introduction
Thank you for purchasing the ToLiss Airbus A319 and for trusting us to provide you with one of
the most realistic FBW simulation addons with complete custom systems for X-Plane.
This product has been developed since 2008. Its Fly-by-wire and Autopilot system are based on
the FBW technology provided by QPAC. The Flight Management System has been completely
reworked to provide a complete and accurate representation of the system in the real aircraft.
The hydro-mechanical and electrical systems of the aircraft model are also based on the latest
QPAC technology with numerous significant improvements. The simulation supports accurate
system behaviour in the presence of failures. For example, following the failure of an electrical bus,
associated equipment, i.e. cockpit displays, exterior lights, certain computers, etc. fed by that bus
will not be available anymore.
To improve the user experience, this model features situation saving and loading. Flights can
be stopped at any point in time and continued from the exact same conditions another day. The
model also provides situation autosaving; should something unforeseen happen during the flight,
the autosave allows resuming the flight to try again.
About the manual: The ToLiss Airbus A319 comes with three manuals:
• A “simulation manual” (this manual): Describes installation, and setup of the model as well
as usage of the “Interactive Simulation Control System”.
• A “tutorial flight”, which provides a step-by-step description of a complete flight from cold
& dark to aircraft shut-down after landing. This is the best manual to learn flying the
aircraft.
• An “aircraft manual”, which is primarily intended as a reference after the tutorial has been
completed. It provides a reference for standard operating procedures, as well as a more in-
depth look into the different systems of the aircraft.
Acknowledgements
ToLiss want to thank the following individuals and companies for their contributions to this
project:
• Turbine Sound Studios for providing us with the sound packages used in the aircraft,
• MattDesignsXP for normal texture rework, paintkit updates, the creation of the ToLiss
livery, and some sound improvement proposals,
• MaxWaldorf for Smartcopilot integration,
• Saso Kiselkov for the Librain library providing windshield rain affects,
• David Gutierrez for providing a high-quality alternative texture set free of charge.
(available for download at www.x-plane.org)
• R1 Aviation for making the official ToLiss Airbus A319 presentation video,
• Christopher Tantow for providing the Airbus house liveries,
• All Beta Testers for their constructive criticism without which this product would not
be what it is now,
• And of course, all livery painters for providing quality liveries free of charge to the
community.
4
2 Aircraft installation and Xplane setup

The installation of the aircraft follows the standard procedure for installing aircraft in X-Plane.
Unzip the content of the ToLiss 319 zip-file directly into your “Aircraft/Heavy Metal” folder (or
any other suitable aircraft folder.). Note that the updater tool is contained inside the aircraft folder.
The manuals are in a subfolder, called “manuals”.
Manuals
Updater client
Note that the aircraft delivered by default contains a 3d cockpit only. There is also a version
that features both a 2d and a 3d panel available. However, this version does not run on all platforms
(namely iMacs with Nvidia GTX graphics card) and it may be confusing to users, therefore it is
not delivered in the initial package. If you want the version with 2d and 3d panel, please contact
the x-plane.org store, they will provide you with the download link. Note that the combined 2d/3d
panel version does not have an updater feature; you will have to redownload the entire package
every time the aircraft is updated.
Inside the aircraft folder, there are 3 different aircraft files, two for use with X-plane 11 and one
for use with X-Plane 10.
In X-plane 11, you will see these two symbols under the airliners tab:
The “Hi Def” version of the aircraft uses higher resolution textures and is the recommended
aircraft to load if your hardware supports it. The “Std Def” version allows framerate improvements
for weaker hardware. Do NOT attempt to load the XP10 aircraft in X-Plane 11. In X-Plane 10,
only the aircraft file labelled a319-XP10.acf will work.
2.1 Special requirements in Windows

The SASL plugin used in the aircraft requires that the MSVC redistributable package 2013 for
64 bit platforms is installed. At time of writing, these can be downloaded from this location:
5
https://www.microsoft.com/en-ca/download/details.aspx?id=40784
If this link does not work, please google “Visual C++ Redistributable Packages for Visual Studio
2013”. Make sure to install the 64 bit version, called “vcredist_x64.exe”.
The sound player requires the MSVC redistributable package 2017 for 64 bit platforms. At time
of writing, this can be found here:
https://support.microsoft.com/en-ca/help/2977003/the-latest-supported-visual-c-downloads
2.2 Special requirements in Linux

For the aircraft to work in Linux, the “curl” package has to be installed. The aircraft requires
libcurl.so.4 together with libssl.so.1.1 and libcrypto.so.1.1. To be able to paste the serial number
into the activation screen, the “xclip”package has to be installed.
2.3 Updating
The aircraft comes with an updater tool that prevents you from having to redownload the entire
package every time there is an update available. It is a java-script file called X-Updater-Client.jar.
Double click the file to execute it and follow the instructions on the screen to update.
Make sure to select the correct

installation location for the
Enter the email address you used
product you are actually
in the store to purchase the
product, and the license key
delivered with your purchase.
Note that you will need to have the java runtime libraries installed to use this feature. You can
get them at http://www.java.com
6
2.4 Aircraft activation

After installation, the activation screen will be shown:
You can use this button to

paste the serial number from
Enter the serial number
your confirmation email (On
here:
Linux, xclip must be installed)
Set this to 1 in order to provide your approval that

we store your IP address. (Required for activation.)
Use this button to contact the

activation sever to receive your key
Enter the serial key that was contained in your order confirmation email from the x-plane.org
store into the field. After that you will have to read the legal disclaimer required by the European
Union with respect to ToLiss’ handling of your personal data. Acknowledge that you read the
disclaimer and the you authorize ToLiss to store the IP address with which the aircraft was
activated. Once you gave your authorization, the “Activate” button becomes available. Subsequently
hit “Activate”. If the message “Serial Number Invalid” appears, the code was not entered correctly.
For all other failure messages please verify your internet connection and try again after half an
hour, If it still does not work, please contact us for assistance.
Note that under Linux and Mac OS X the message “Error code 10” can be caused by exceeding
the number of activations for the aircraft. In that case, please contact x-plane.org support with
your key and request an increase in activations.
Note that the activation code is stored both in the aircraft folder and in the X-plane main
directory. Reactivation is not required after updating or reinstalling the aircraft model. Note that
changes to the hardware or complete reinstalls of X-plane may require reactivation.
If you plan on reinstalling Xplane, it is recommended to backup the folders
“Xplane/Resources/plugins/ToLissData”, “Xplane/Resources/plugins/ToLissFlightPlans” and
7
“Xplane/Resources/plugins/ToLissTerrainData”. This will allow keeping the activation

information, saved situations and the data used for terrain display.
X-plane error message during activation: X-Plane will post a failure message about parsing of
the VR-config file when the aircraft is first activated. This is normal, as the non-activated plugin
does not register all datarefs required by VR. If you did not acknowledge the failure when activating,
the error message will be reposted after aircraft load. The message can be ignored and simply be
acknowledged.
Trouble shooting: If your activation appears successful, but on reload the activation windows
appears again, please delete the following files: ToLiss/plugins/AirbusFBW A319/license*.lic and
X-Plane/Resources/plugins/ToLissData/license319.lic
2.5 Livery installation

To install add-on liveries for this aircraft, please copy the associated folder into the “liveries”
subfolder located within the aircraft folder. There are numerous liveries available for this aircraft
for free on www.x-plane.org.
To use the “automatic engine type detection” feature, the livery name must be preceeded by the
engine type in square brackets. For example, if the Lufthansa livery is named “[CFM] Lufthansa”
instead of just “Lufthansa”, the plugin will automatically select the CFM engine if engine type is
set to “AUTO” in the Audio-visual settings tab (see section 2.8.2). The prefix for the IAE engine is
“[IAE]”.
To get the aircraft with 2 emergency exits, use the prefixes “[CFM2]” or “[IAE2]”. Note that 2
emergency exits are only visible, if you have engine type set to “AUTO”.
Sharklets can also be activated when using the AUTO setting for the engine type. To activate
sharklets, the engine/exit code must be followed by S. For example: [CFM2S] results in the aircraft
with 2 overwing exits and sharklets and CFM engines. [IAES] results in the aircraft with one
overwing exit, sharklets, and IAE engines.
Note: Sharklets can be manually selected via the ISCS when an engine type has been manually
selected. This is not possible for the dual emergeny exit option as this is strongly livery dependent.
Similarly, the SatCom antenna is activated via the letter T in the livery string. [IAE2ST] would
therefore give you the IAE engine with 2 emergency exits, sharklets and the satcom antenna.
8
2.6 Alternative cockpit textures

Texturing is to some degree a matter of taste and for those of you who don’t agree with our taste,
there is an alternative cockpit texture set available on x-plane.org:
https://forums.x-plane.org/index.php?/files/file/49553-toliss-cockpit-texture-replacement/
Follow the instructions provided on the website on how to install this texture pack.
2.7 Joystick setup

For the use of this aircraft, a joystick with yaw axis is recommended. Without a yaw axis on
the joystick, it is possible to deflect the nose wheel with the roll axis as described in section 2.8.1.
For an optimal flight experience with this aircraft, it is also recommended to have at least these
functions assigned to joystick buttons:
• Autopilot instinctive disconnect button
• Regular brakes hold and, if possible maximum brakes hold (unless using brake pedals)
• Reverse thrust toggle (unless using dedicated reverse levers)
All other commands can also be done via keyboard commands if no more joystick buttons are
available. The functions above should be on the joystick, because they are on the actual flight
controls in the real aircraft and pilots can use them without taking their hands of the controls. All
other commands, such as gear, flaps, spoilers, etc. are commands for which in real life one hand
needs to be taken off the controls. (Unless performed by the co-pilot.)
Most of the native X-Plane commands work well with this aircraft. However for all autopilot
related features, only the commands listed in the following table are mapped to the respective
plugin commands:
Function X-plane command name.
Pulling the ALT selector knob sim/autopilot/Autopilot altitude-hold ARM
Pulling the HDG selector knob sim/autopilot/Autopilot heading-hold
APPR button on FCU sim/autopilot/Autopilot approach
A/THR button on FCU sim/autopilot/Autopilot auto-throttle toggle
A/THR instinctive disconnect sim/autopilot/Autopilot auto-throttle off
AP Instinctive disconnect button (on pilot sim/autopilot/Flight-Dir Down (on-fdir-off)
sidestick)
In X-plane 11, these commands are located under “Navigation & Radios” and then under
“Autopilot”. Alternatively, use the term “autopilot” in the search field.
In X-plane 10, the commands are located as shown in the following screenshot:
9
ALT selector knob PULL

APPR button on FCU
A/THR Instinctive disconnect
A/THR Button on FCU push
HDG selector knob PULL
AP Instinctive disconnect button
An alternative way is to use the ToLiss plugin custom commands which have more intuitive naming;
see section 2.7.3.
2.7.1 Other mapped x-plane commands

The following native x-plane commands are mapped to specific ToLiss plugin functions. This list is
not complete but lists those commands for which the mapping is not necessarily intuitive.
sim/annunciator/clear_master_warning Press the Master Warn button
sim/annunciator/clear_master_caution Press the Master Caut button
sim/annunciator/clear_master_accept Press the ECAM CLR button
sim/instruments/map_zoom_out Increase range on Captain ND
sim/instruments/map_zoom_in Reduce range on Captain ND
sim/instruments/EFIS_mode_up Increase mode on Captain ND
sim/instruments/EFIS_mode_dn Decrease mode on Captain ND
10
2.7.2 Detailled axis setup and status check

The ToLiss Airbus A 319 supports numerous joystick axes to tie directly into the custom systems
modelling of the ToLiss plugin. It also supports the use of two sidesticks (pilot and co-pilot side)
as described below. A dual input and priority logic are available as on the real aircraft.
When using joystick axes for nosewheel tiller, brake pedals or a second joystick, it is important
to confirm the joystick configuration in the Interactive Simulation Control System (ISCS) at least
once after selecting the joystick setup1.
To open the ISCS, go into the Xplane menu, select plugins/ToLiss/Open ISCS screen. Select
the tab “Settings, Action”; you will see the following screen:
Verify that all axes that you

assigned are detected by the
plugin as expected.
Leave all axes centered and press this

button. Note: This also saves all your
current preference settings.
The button “Center to current pos (Tiller)” will only be available (i.e. not greyed out), if either
an axis for nose wheel tiller or a second joystick is found. In that case, leave your controls centered
and click this button.
Note: If any of these axes are assigned, but the ISCS indicates “NO”, move the axis through it’s
whole range of motion and verify that the status changes to “YES”.
Important: It is generally recommended to move all joystick axes through their range of motion
after loading this airplane!
1 X-plane does not provide an interface to retrieve the processed data for these axes and the plugin
has to decode the axes itself; it therefore requires user interaction to determine the center position for
nose wheel tiller or second joystick axes.
11
Note that the x-plane default axes “roll”, “pitch”, and “yaw” do not require this procedure.
Axes assignments
The following figure illustrates the setup (in X-plane 10) for two sidesticks, rudder pedals2 with
one set of brakes (independent pilot/co-pilot brakes are currently not supported) and nosewheel
tiller. For throttles, individual throttle and reverse levers are supported as well as a single lever
affecting all engines at the same time.
For the second sidestick, the X-plane axis “collective” is used for pitch and the axis “prop” is
used for roll. The second joystick must be activated by setting the switch “ENABLE SECOND
STICK” to ON. If you do not use a second sidestick, leave this switch set to OFF to avoid
interference with helicopter or other controls.
Axes assigned to
pilot sidestick
Axes assigned to
copilot sidestick
Joystick sensitivity in X-plane 11

As in real life, the gearing (i.e. the linearity) between the joystick deflection and the command
issued to the fly-by-wire control laws heavily affects the handling qualities of the aircraft. We have
coded the appropriate joystick response curves into our system simulation plugins. Therefore we
recommend to leave the joystick sensitivity to fully linear when flying the ToLiss Airbus A319.
It is important to set the “stability augmentation” sliders to 0, as the x-plane internal feature
interferes with the ToLiss custom fly-by-wire control laws.
2 Rudder pedals between pilot and co-pilot are mechanically linked in the real aircraft and the
position is only read once; hence we only support a single axes for rudder pedals.
12
Assignment of the sidestick priority buttons

When using two joysticks, the following custom commands should be assigned to each of the
instinctive AP disconnect buttons on the sticks in order to enable to sidestick priority logic:
- Pilot sidestick: toliss_airbus/ap_disc_left_stick
- Copilot sidestick: toliss_airbus/ap_disc_right_stick
Furthermore, it is imporant to switch off the option “Joystick Roll for NWS”, see section 2.8.1
for details.
2.7.3 Custom commands
The plugin also provides custom commands to trigger custom functions. These commands can be
assigned to keys or joystick buttons like any other command. On X-Plane 10, the box in the top-
right corner of the Joystick button configuration dialogue, labelled “custom cmnds from plugins”,
must be used.
- Custom command to open the ISCS via joystick button or keyboard command:
toliss_airbus/iscs_open
- Custom command to toggle the park brake lever on the pedestal. Note that the regular
Xplane brake commands also toggle the park brake, if the aircraft is not moving and the engines
are at idle or off:
toliss_airbus/park_brake_toggle
- Custom command to disconnect the nosewheel steering from the rudder pedals. This is used in
real life to allow performing the flight control check during taxi. The button for this is in real life
located on the nose wheel tiller:
toliss_airbus/ nws_disconnect_hold
- Custom commands to trigger pushing the AP-buttons on the FCU:
toliss_airbus/ap1_push
toliss_airbus/ap2_push
- Custom commands to trigger pushing the FD-buttons on the FCU:

toliss_airbus/fd1_push
toliss_airbus/fd2_push
- Custom commands to push or pull the Speed-Selector-knob on the FCU:
toliss_airbus/spd_push
toliss_airbus/spd_pull
- Custom command to trigger pushing/pulling the V/S-knob on the FCU:
toliss_airbus/vs_push
AirbusFBW/PullVSSel
- Custom command to trigger pushing/pulling the HDG-knob on the FCU:

AirbusFBW/PullHDGSel
13
AirbusFBW/PushHDGSel
- Custom command to trigger pushing/pulling the ALT-knob on the FCU:

AirbusFBW/PullAltitude
AirbusFBW/PushAltitude
2.8 Simulation configuration

On the ToLiss Airbus A319, the simulation configuration is set via the “Interactive simulation
Control System” (ISCS). To access the ISCS, go to the Xplane menu, “Plugins”/ “ToLiss” / “Open
ISCS Screen”:
The ISCS windows opens with 7 tabs; simulator configuration can be changed in the tabs “Audio-
visual settings” and “Settings/Actions”.
Note: As described in the previous section, the ISCS can also be opened via the
joystick/keyboard command toliss_airbus/iscs_open.
From aircraft version 1.0.2, the ISCS can be moved to a different location on the screen by
grabbing the title bar of the ISCS with the mouse.
2.8.1 Settings/Actions page
The settings and actions page provides:

• Version information about the version of the ToLiss Systems Plugin currently running.
• Information on the detected joystick configuration. (See section 2.7.2)
• Simulation-specific actions that can be used at certain times during the flight (see section
3.1)
• Preference settings.
14
In the column “Preferences”, the properties described below can be adjusted; to retain these
values, click “Save Preferences and default values” at the bottom of the screen once the desired
configuration is set.
The first two items allow adjusting the startup behaviour of the ToLiss Airbus A319.
Ovrd XP start setting:

When set to “true”, the aircraft will always load up in the configuration chosen in the next line,
independent of the XP setting “start with engines running”. If set to FALSE, the ToLiss Airbus
A319 will start with engines running, whenever XP is set to “Start with engines running”. If XP is
set to starting with engines off, the ToLiss Airbus A319 will start up in the configuration selected
in the next line.
Cold start type / Start up type:

This field offers three different cold start options, plus – if “Ovrd XP start” has been activated
– a fourth option to start with engines running. The three cold start options are:
a) COLD and DARK: In this case, the airplane is completely shut down after load. The
ADIRUs and all electrical supplies is off. This corresponds to the configuration in which a
pilot would find the aircraft after an overnight stay.
b) EXT POWER ON: In this configuration, the ADIRUs are still off and require a full
alignment which takes about 10 minutes. This is typically the configuration after a longer
turn-around with the aircraft remaining at the gate.
15
c) APU + ADIRU ON: In this configuration, the engines are off, but APU is running and
ADIRUs are already aligned. This is typically the case during very fast turn-arounds.
ILS AUTO ALIGN

This item addresses a frequent issue encountered when installing custom scenery that rotates
the runway; for these cases the ILS and the runway are not aligned anymore. The ToLiss Airbus
A319 plugin contains a feature that detects if there is such custom scenery installed and realigns
the ILS in the internal database with the new runway heading.
Note: Changes to this setting require an aircraft reload, as the ILS database is only built once
upon aircraft load.
JOYSTICK ROLL FOR NWS

This setting is useful for joystick setups without a yaw axis. It allows using the nose wheel
steering while taxiing on ground via the joystick roll axis. There are three different options for this
setting:
NO: The roll axis of the joystick does not control the nose wheel steering.
YES: Deflections of the roll axis on the joystick steers the nose wheel also, with full deflection
feasible at low speeds (below 20kts).
AUTO: the plugin attempts to automatically detect, if a yaw axis is assigned or not. This can
lead to undesired behavior before deflecting the yaw axis for the first time after loading the aircraft.
It is recommended to set this field to the appropriate value (YES/NO) according to the joystick
configuration.
REGULAR BRAKE STRENGTH

This slider allows adjusting the strength of the regular brakes to individual preferences. The left
most setting is 10% of brake force whereas the right-most setting is 60% of brake force. This setting
applies to the X-plane command “Hold brakes regular”.
USE MOUSE WHEEL

This setting determines the use of the mouse wheel in the 3d cockpit for the manipulation of
cockpit controls. The cockpit is optimized for mouse wheel use; only switch this off, when using a
mouse without wheel.
F1/F2 CAN TOGGLE REVERSERS

This setting allows choosing the desired behaviour of the Xplane native keyboard commands
for “throttle up” or “throttle down”. When set to OFF, the keyboard behaviour will be Xplane
default.
If set to ON, the F1 key (Xplane default key for “throttle down”) can be used to move the
throttle AFT below the idle detent into the REVERSE region and then apply full reverse thrust.
In this case the F2 key (Xplane command “throttle up”) is used to reduce the reverse thrust to idle
and return to forward thrust.
With this setting, the key function corresponds more to the physical motion of the thrust levers.
16
A/C HAS FLORENCE KIT

This setting determines if the simulated 319 is equipped with a special mod that deflects the
ailerons upward upon touchdown in order to reduce landing distances. This setting can be modified
without having to reload the aircraft and the ground spoiler logic will act accordingly.
XPDR COMPATIBILITY MODE

This can be used if you have trouble using the TCAS/XPDR panel with third-party add-ons.
The option eliminates the destinction between Alt Reporting On (Transponder Mode Charlie) and
Alt Reporting Off (Mode Alpha) which helps in this case. Leave this option off, unless you have
trouble with a third party traffic or ATC add-on.
SYNC BARO SETTINGS

If this option is selected ON, a change to one of the altimeter settings (captain or copilot side)
will automatically adjust the other side altimeter setting to the same values.
DEFAULT VALUES
The last two settings DEFAULT BARO UNIT and DEFAULT TRANSITION ALT affect how
the aircraft will be configured next time it is loaded. The baro unit selectors will be in accordance
with the selected setting and the transition altitude on the MCDU PERF pages TO and APPR will
reflect the value set here.
These settings do NOT affect the flight currently in progress.
2.8.2 Audio-visual settings
The ISCS tab AUDIO-VISUAL SETTINGS provides sound settings in the left column and
visual effect settings in the right column:
Aircraft version with

2d panel only
17
SOUND SETTINGS
The Master Volume slider changes the volume of all custom sounds as well as the X-plane
environmental volume. The only volume not affected by this is ATC and other radio traffic. This
slider allows to evenly adjust all volumes without messing up the relative tuning of the individual
components.
The component volume sliders allow adjusting the different sound effects to individual
preferences. Click on SAVE THESE SETTINGS at the bottom of the page to retain the settings
for the subsequent flights.
Note that the volume of the aural alerts like warning sounds, altitude callouts etc can be
adjusted both via the slider in the ISCS and via the rheostats in the cockpit. The position of these
rheostats is saved whenever the preferences/settings are saved through the ISCS.
The slider for external volume ratio allows to uniformly scale the volume of outside sounds
relative to the inside value. Scaling goes from factor 0.5 (6dB reduction) to 1.5 (3dB increase).
The option Doppler effect allows switching ON and OFF the doppler effect if the camera moves
relative to the aircraft. Of course, having this ON is the more realistic setting; however, under
certain conditions the user experience may be better with this option turned off.
The option 3D sound fading applies to system sounds and how they are audible while inside the
aircraft. When this option is set to ON, the sounds of flaps/slats, PTU etc are faded with the
distance from the current observer location. This means that most sounds are barely audible in the
cockpit as they are in real life. When set to off, the sounds are audible throughout the aircraft
independent of the current location.
Note that the ToLiss Airbus A319 mutes Xplane’s native volumes to prevent interference with
the custom sounds that come with the aircraft:
These sliders are set to zero by the ToLiss

plugin; leave them at that setting.
This is intentional, and these sliders are not to be moved while flying the ToLiss Airbus A319.
When loading another aircraft, the previous volume settings are automatically restored.
18
VISUAL SETTINGS
In this section, the engine type, reflection levels, and some of the visual startup options can be
selected. For any of the following option, clicking “SAVE THESE SETTINGS” will store the settings
for subsequent aircraft loads.
If the drop down list “ENGINE TYPE” is set to auto, the plugin will attempt to automatically
select the engine type based on the currently loaded livery. For this feature to work, the livery
folder names must start with [CFM] for liveries using the CFM56 engine, and [IAE] for liveries
using the IAE V2500 engine. You can also force the use of one of these engine types by selecting it
in the drop-down list. Engine type selection affects exterior 3D model, Engine Warning Display
(EWD) configuration as well as aircraft performance. Note that livery names preceeded by [CFM2]
or [IAE2] will enable the 2 overwing exit option if AUTO engine type is selected.
The option “WINGTIPS HAVE SHARKLETS” allows switching between the classic wing tip
fences and the modern sharklets. If engine type is set to AUTO, the wingtip type is automatically
selected based on the livery control string (letter “S” in the livery control string). Hence, this option
is only available, if an engine type has been manually selected. Note that the aircraft drag changes
depending on the type of wing tip device.
The option “HAS SATCOM ANTENNA” allows selecting the satcom antenna manually in case
of manual engine type selection. If the engine type is set to AUTO, the satcom antenna option is
also determined via the livery control string. (letter “T” in the livery control string)
The sliders “Display Reflections” and “Window Reflections” are used to set the reflection levels
for the cockpit displays and window panes in the 3d cockpit.
When the option “DEFAULT TO COPILOT SEAT” is selected, the aircraft will start up with
the view aligned with the co-pilot seat. This is useful if you prefer flying from the right seat, e.g. if
you are an co-pilot in real life.
If the setting “STROBE FLASH IN COCKPIT” is set to ON, the light of the strobe will light
up the entire cockpit when flying through clouds. I personally found this a very annoying X-plane
feature. On large airliners, the strobes are always ON throughout the flight, and they have little
effect on the cockpit environment; hence, it is recommend to have this setting set to OFF. Effect
of this setting is immediate and does not require aircraft reload.
The option “USE POPOUT WINDOWS for POPUPS” (X-Plane 11 only) allows to choose if
you want the display popups to be displayed inside the Xplane screen or if you want to use the new
popout windows that X-plane 11 provides and that allow you moving the windows to a different
screen.
19
The option “SHOW WINDSHIELD RAIN EFFECTS” (X-Plane 11 only) allows switching on
and Off the rain effects on the windshield using Saso Kiselkov’s librain. Switching this off allows
improving you frame rate.
The option “SHOW XP PARTICLE EFFECTS” (X-Plane 11 only) allows switching off the X-
Plane particle effects for this aircraft in order to improve the frame rate.
The option “ENABLE AVITAB TABLET” (X-Plane 11 only) is only visible, if the avitab
freeware plugin is installed. (https://forums.x-plane.org/index.php?/files/file/44825-avitab-vr-
compatible-tablet-with-pdf-viewer-moving-maps-and-more/) Use this feature to switch the tablet
on the left side of the cockpit on or off.
The slider “Refresh PFD every X cycles” allows frame rate optimization. If this slider is set to
1, the PFD will be refreshed every cycle, which puts the highest demand on graphic card and CPU.
With the slider set to 2 or 4, the PFD is only redrawn every second or every fourth cycle
respectively. This improves frame rate, but may lead to non-smooth PFD appearance. Note that
the other displays are drawn at half the rate of the PFD.
The option “SAVE POPUP CONFIG ON QUIT” allows to store the positions to which the user
dragged with display popups. If this is set to 1, the aircraft will automatically use the popup
positions from the end of the last flight, even if the popups were popped out into separate windows.
Users that requested the aircraft version with an additional 2d panel from the store will also
see the option “START WITH 2D PANEL”. This option can be used to force x-plane to start up
in 2d panel view when loading this aircraft.
2.9 Navigation data – location and update

The ToLiss systems plugin uses the X-plane navigation data as shown in the following table.
Note that the plugin imports either the “Default Fixes” and “Default Navigraph Fixes” (XP10 only)
or the Custom Versions thereof, if available. It does not merge “Default XYZ” data with “Custom
XYZ” data.
20
X-plane 10 X-plane 11
Default Fixes Resources/default data/earth_fix.dat Resources/default data/earth_fix.dat
Default Navigraph Resources/GNS430/navdata/Waypoints.txt Not applicable
Fixes
Default Navaids Resources/default data/earth_nav.dat Resources/default data/earth_nav.dat
Default Airways Resources/GNS430/navdata/ATS.txt Resources/default data/earth_awy.dat
Default procedures Resources/GNS430/navdata/Proc/ICAO.txt Resources/default data/CIFP/ICAO.dat
Custom Fixes Custom Data/earth_fix.dat Custom Data/earth_fix.dat
Custom Navigraph Custom Data/GNS430/navdata/Waypoints.txt Not applicable
Fixes
Custom Navaids Custom Data/earth_nav.dat Custom Data/earth_nav.dat
Custom Airways Custom Data/GNS430/navdata/ATS.txt Custom Data/earth_awy.dat
Custom Procedures Custom Data/GNS430/navdata/Proc/ICAO.txt Custom Data/CIFP/ICAO.dat
When updating the navigation data, please only update the data in the folder Custom Data. In
X-plane 11, the ToLiss plugin performs the same integrity check as X-plane; that means, all data
in the Custom Data directory must be of the same navigraph cycle, otherwise the data located in
the Custom Data directory are rejected. Data format must match the X-plane default data format
according to your X-plane version.
If two valid databases are found, they are displayed on the MCDU status page, including the
corresponding cycle info. In order to switch to the currently non-active database, click on the Line
Selection Key (LSK) in the third row on the left. (LSK 3L):
Note: Changing the database will delete the current flight plan.
Note: Loading the new database can take up to 1 minute. During this time, X-plane will be
frozen.
If a custom database is installed, but it does not appear on the above screen, please verify X-
plane’s log.txt file located in X-Plane’s main folder. It will show the reason why the file was rejected
21
in one of the messages following the line: “ToLiss aircraft systems plugin: Building navigation
database.”
2.10 IAE sound pack activation

The aircraft comes out of the box with the CFM engine sound pack from Turbines Sound
Studios. As default, this sound pack is used independent of the selected engine type.
You can purchase the IAE engine sound pack through the x-plane.org store. To activate the
IAE sound pack, enter the key that you purchased in the store in the “Addons” tab of the ISCS:
Enter key from X-plane.org store here
Press activate
Activation status will be displayed on the screen:
Note that a reload of the aircraft is not necessary and the IAE sound pack can be used
immediately.
After sound pack activation, the plugin will automatically switch between CFM and IAE sounds
depending on currently selected engine type.
2.11 Third part add-on compatibility

Compatibility between 3rd party plugins and this product is constantly evolving. The goal is to
make it compatible with ground handling plugins and other products that bring life (outside the
systems simulation) to the aircraft.
At this stage, compatibility is confirmed with:
22
• Better Pushback (probably the best pushback tool in the X-Plane world.)
CAUTION: When releasing the parking brake too early, the aircraft may start rolling
before pushback starts. (Sometimes, in Xplane, the aprons are not level, and chocks
are not simulated.) Ensure to keep parking brake ON until, better pushback explicitly
asks you to release it.
• X-Plane 11 native ground handling: The aircraft file is set up to allow the native
ground handling feature of X-Plane 11 to place catering trucks, fuel truck and baggage
belts at the aircraft.
• The Avitab plugin to enable the in-cockpit pdf viewer.
2.11.1 Smartcopilot use

The ToLiss Airbus A319 ships with a ready-to-go smartcopilot config file. (Thanks to MaxWaldorf
for creating and testing the file.) Use of smartcopilot comes with the following restrictions:
• Don't use 2D MCDU pop-ups, as commands will not be exchanged with your partner.
• When entering the flight plan, errors might occur, depending on connection quality
between you and your partner. Always double check the plan.
• The integrated ToLiss pushback does not support smartcopilot. Please use
Betterpushback for the best experience!
2.11.2 System simulation/FMS 3rd party add-ons
The ToLiss Airbus A319 is compatible with:

• AirFMC: This product allows bringing the MCDU onto the iPad.
• WebFMC: This product allows using the MCDU through a Web Browser.
The ToLiss Airbus A319 is not compatible with:

• Any 3rd part FMGS solution (X-FMC, UFMC, vasFMC, etc.). The reason is that the
aircraft ships with a highly customized FMGS simulation, specially adapted to the type
of aircraft simulated. There is no need to use third party FMS solutions.
• Unfortunately, X-HSI is also not supported anymore. The data used to draw the ND
are highly complex and in part proprietary. The effort required to publish the data such
that X-HSI can access them could not be justified.
23
3 Use of ISCS during the flight

Besides being the interface to select simulation preferences, the ISCS also contains the ToLiss
equivalent of the IOS (Instructor Operator Station) found also on commercial simulators for real-
time use during the flight.
3.1 Resume from last time

A new function has been added in V1.1.1: Resume from last time. This function is accessible
via X-plane’s Plugins menu:
The function reloads one of the following two aircraft states:

• If x-plane quit normally after the last flight with the ToLiss, the ToLiss Airbus A319
will be reloaded with the exact conditions that it had last time X-plane was closed.
(Associated situation file name: “CURRENT SITUATION”). This can be used to
simulate the turn-arounds of a particular aircraft, as it always restarts the way the user
left it last time.
Note: If you had failures on the previous flight, you may want to enter the ISCS to reset
all faults prior to your next departure. (See section 3.7 for details.)
• If x-plane crashed during your last flight with the ToLiss, the ToLiss Airbus A319 will
recover the flight from the last autosave. (Associated situation file name:
“AUTOSAVED SITUATION”)
Note: This is only available when Autosave is selected ON. (See section 3.3 for details.)
3.2 Special actions

Special actions for use during the simulation are located in the last tab of the ISCS named
“Settings / Actions”:
24
ADIRU QUICK ALIGN

This action is available, if at least 1 ADIRU is in alignment mode. The picture above shows the
option in the ensabled state; when diabled, the field is greyed out. Executing this action completes
the alignment for any ADIRU that is not in NAV mode and not failed.
JUMP TO NEXT WPT / JUMP 100NM

The exact label of this action dependd on the length of the current flight plan leg. It is available
only during the CRUISE phase in flight. Also, the aircraft must be flying straight and be fully
stabilized on autopilot in NAV mode. It advances the position of the aircraft to 1NM before the
next waypoint (JUMP TO NEXT WPT) or by 100NM towards the next waypoint, if the next
waypoint is more than 100NM away.
AUTO-PAUSE
This feature allows the user to leave the computer during a flight and make sure that the
simulation pauses automatically if something happens that requires user interaction. The feature
allows automatic pausing of the simulation, if:
• A master warning is triggered (e.g. due to AP disconnect)
• A master warning or a master caution are triggered. (Any system fault)
• A master warning or caution is triggered, or the aircraft has passed the T/D, i.e. has
entered the DESCENT phase.
25
Note that the aircraft always loads with this option OFF. The intention is that the user has to
activate the option prior to leaving the simulation alone.
3.3 Situation loading and saving

The ToLiss systems plugin allows loading and saving situations such that a flight can be stopped
at any point in time and continued another day from the exact same conditions where it was
stopped. This is also useful to practice the same approach over and over again, without having to
do flight planning, take-off etc.
To access the situation loading/saving interface, open the ISCS (see section 2.8) and go to the
“POSITION/SITUATIONS” tab:
The left column contains the LOAD/SAVE SITUATIONS section. The large white textbox
contains all situations found by the plugin. This will naturally be empty when you install the
airplane the first time.
Note: The situation files are stored in the following folder inside the X-plane directory:
Resources/plugins/ToLissData/Situations.
Once you have stored a larger number of situations, the filter feature available via the text box
“Filter situations” may become useful. If you enter a text of at least 2 characters in this box, only
situations containing this string in the filename will be displayed. In the following example, the
situations are filtered for the string “EDDH”:
26
Highlighting a situation in the window marks it in amber color. Clicking the button LOAD
SELECTED SITUATION loads this situation and the ISCS windows closes automatically once the
load is complete.
Note: If the situation loading leads to large position changes, e.g. from one continent to another
or also from southern to northern Germany, the situation loading will take time as X-plane has to
reload all scenery.
To save a situation, enter the situation name in the text box SAVE SITUATION FILE NAME
and then click “SAVE SITUATION”.
It is also possible to automatically save situations at a given interval, e.g. to recover from
potential x-plane crashes. In order to do so, select AUTOSAVE ON/OFF to ON and move the
slider to the desired time interval in minutes. The possible intervals range from saving every minute
to every thirty minutes.
The autosaved situation has the name “AUTOSAVED SITUATION” and will be overwritten
when the next autosave triggers. If you want to recover the last autosaved situation after restarting
X-plane, you can do so as long as you stay on the ground without moving the aircraft. Autosave
only becomes active once the take-off has been initiated.
27
3.4 Aircraft loading and TO performance calculation

The loading of the aircraft, i.e. payload/fuel and the TO performance calculator are available
on the “Aircraft configuration” tab of the ISCS:
3.4.1 Selecting payload

In the top portion of the left column, the payload can be selected:
• Number of passengers, with each passenger weighing 100kgs (220lbs) – average weight of
a human + luggage.
• The passenger distribution determines how the passengers are distributed throughout the
cabin, for 0 passenger or full load this has of course no effect, as all seats are taken. Effect
is strongest with half load where the slider at the extremes means that all passengers are
sitting in the forward or the aft half with the other half of the cabin being completely
empty. Note: This throws the CG completely out of bounds!
• It is also possible to choose the amount of additional cargo in each of the cargo holds.
The resulting “Zero fuel weight” (ZFW) and the “Zero fuel weight CG” (ZFWCG) is shown
below these sliders and shown as the red cross in the CG-GW diagram in the right column. Make
sure that the red cross always falls within the red area of the diagram.
Once the payload configuration has been set, click the button APPLY THESE LOAD
SETTINGS and the aircraft load will be adjusted accordingly.
3.4.2 Selecting fuel load

The block fuel is selected in the bottom of the left column. Draw the slider to the desired fuel
volume. (Appropriate fuel load can be computed with the help of the FMS.) Check that the black
cross in the CG-GW diagram is within the black limits to ensure that your TO weight and CG are
28
acceptable. Click QUICK REFUEL/DEFUEL to change the fuel content of the tanks to the set
block fuel.
3.4.3 CG-GW diagram

This diagram assists to ensure aircraft loading for which that both the take-off CG and the
landing CG are within acceptable limits. It shows three different CG-Weight combinations
represented by different colours:
• The blue limits show the in-flight weight and CG limits. The blue cross represents the
current weight and CG. It does not move while manipulating the sliders on the left until
either the APPLY LOAD SETTINGS or the QUICK REFUEL/DEFUEL button are
clicked.
• The black limits are the TO weight and CG limits. The black cross shows what the
weight/CG configuration would be if both the payload and fuel settings currently
selected with the sliders were applied.
• The red limits are the landing weight and CG limits. The red cross represents the Zero
fuel weight (ZFW) and CG. Note: As some fuel left needs to be left at landing, make
sure the red cross has sufficient margin from the LDG CG limits.
Note: Maximum permissible ZFW for the 319 simulated with this product is 58500kgs.
3.4.4 TO performance calculator

The TO performance calculator is located at the bottom right of this tab. In order to access it,
the FMGS must have been initialized and a departure runway selected. The TO performance
calculator automatically gets the departure runway from the FMGS and retrieves weather
information from Xplane.
After selecting the departure runway in the FMGS, the TO performance calculator looks like
this:
In order to calculate the take-off speeds, select the desired F/S configuration and adjust the
RWY slope, if necessary. Slope information is available on the corresponding airport charts. After
selecting the flap/slat configuration, the calculator will compute the:
• Take-off speeds,
• Take-off trim setting
• Flex temperature
29
These values need to be entered on the TO PERF page in the MCDU. This data transfer does
not occur automatically, as the real life aircraft also require that this task is performed manually.
Note: Once the cruise phase has been reached, the TO performance calculator is replaced by
the METAR string for the selected destination airport.
3.5 Ground services

The ground services page allows access to external supplies to the aircraft, such as external power
or pressurized air. It also permits initiating the built-in pushback function. This page is also used
to control the aircraft doors. Other ground vehicles are planned as a future extension.
The QUICK SERVICES section allows activating the following three services that an airport
typically provides to aircraft (no external animations in this case):
• External power: Setting this to ON simulates the presence of an external power supply
plugged into the aircraft receptacle. It is then possible to switch on the external power
in the overhead panel and startup the aircraft without having to start the APU
immediately.
30
• High pressure air: This simulates the supply of external high pressure air supply to the
aircraft bleed system. This can be used to start one of the engines at the gate without
starting the APU. The 2nd engine is typically started after pushback, using cross-bleed
from the first engine.
• Low pressure air: At hot airports, the airport frequently provides conditioned air to the
aircraft to allow keeping the cabin temperature low without having to start the APU
while the aircraft is parked.
3.5.1 Automatic pushback

To push back from the gate, an automatic pushback can be initiated by clicking the button
“START AUTO PUSHBACK (NOSE WHEEL)”. Select the desired pushback length (straight) and
the subsequent angle prior to clicking this button.
Pushback sequence is as follows:

• After clicking the button, the pushback cart arrives.
• Once the pushback cart has come to a stop at the nosewheel, release the parking brake.
That the cart has connected to the nosewheel is indicated by the ECAM memo “NW
STRG DISC”
• The aircraft will be pushed back automatically the desired distance and turning angle.
• Once the aircraft comes to a stop, set the parking brake.
• The pushback cart will leave the aircraft and return to the original position.
It is possible to start the engines during the push back or to perform other cockpit actions,
except for stepping on the brakes. These will not disturb the pushback process.
3.5.2 Manual pushback

It is also possible to perform a manual pushback. In this case the user actually drives the
pushback truck.
Careful: The user steers the truck, not the aircraft; at the beginning keep it slow and steady.
It’s a difficult task, similar to reversing a car with a short-hinge trailer.
Pushback sequence is as follows:

• After clicking the button, the pushback cart arrives.
• Once the pushback cart has come to a stop at the nosewheel, release the parking brake.
That the cart has connected to the nosewheel is indicated by the ECAM memo “NW
STRG DISC”
• Now it’s the user’s turn to drive:
- The joystick pitch axis is used for speed control: forward (pushing) is accelerationg,
backward (pulling) is braking. If you have the joystick at neutral, the vehicle coasts,
slightly decelerating.
31
- The joystick roll axis is used to steer the truck left and right. Keep in mind, that the
joystick steers the truck, not the aircraft. The aircraft will move in response to what
the truck is doing to its nose wheel.
• Once the aircraft is in the desired position, slow down to a full stop (pitch backwards,
or pull up in aircraft terms). Then set the parking brake.
• The truck will leave the aircraft and return automatically to the original position.
Note that at the moment, it is not supported to pull the aircraft with the truck. (Truck moving
forward during the manual pushback.)
3.6 Control of the aircraft doors

By default, the aircraft starts with the doors in automatic mode. Automatic mode means that
the front left door and the cargo doors open automatically at the gate. They close after a
predetermined amount of time. Closure is accelerating once the user switches on the aircraft beacon.
The bottom right of the “Ground Services” tab in the ISCS allows to control each door
individually to one of three states:
• Closed: The door is closed immediately and stays closed
• Open: The door is opened immediately and stays open
• Auto: The door opens and closes according to the plugin internal logic to detect if the
aircraft is parked at the gate.
3.7 Fault injection interface

From V1.1 on, the ToLiss Airbus A319 supports system fault injection. This can be performed
via two different methods:
• Selection of specific faults with different trigger options, such as speed, altitude, time, or
randomly during a given flight phase
• Random fault injection based on typical Mean Time Between Failures (MTBF) of the
failed component. This method allows having large number of computer failures, but
fairly rarely things like engine fires or jammed control surfaces.
Fault injection is performed via the ISCS, tab “Fault scenarios”:
32
Section for MTBF based

random fault injection
Section for user selection

of specific faults
3.7.1 Selection of specific faults
The section below the label “Custom fault selection” can be used to inject specific system faults
at a certain point during the flight. Faults are sorted by system and can be injected based on a
variety of triggers which will be discussed in the following.
A total of 5 different faults can be selected for one flight. To setup a new fault injection, click
on the button “Add new fault”. A new fault injection row will be created:
Click here
A new fault line appears
To select the desired fault, you need to first select the system that will suffer the failure, e.g.
FLT CTRL for flight controls. In a second step you can then select the component you want to
fail, e.g. ELAC 2. After these selections, the fault selection line looks like this:
The third column allows choosing the trigger for the fault. Possible triggers are:
• NOW: The fault will be injected as soon as the ISCS is closed
• AT TIME: The fault will be injected a given time (in seconds) after the ISCS is closed
33
• AT IAS: The fault will be injected as soon as the aircraft Indicated Airspeed exceeds a
given value
• AT ALT: The fault will be injected as soon as the aircraft exceeds a certain Altitude
• RANDOM: The fault will be injected randomly at a given flight phase.
For the items “AT TIME”, “AT IAS”, and “AT ALT”, a slider allows selecting the trigger
parameter. For example, in the following example ELAC2 will fail, once the aircraft speed exceeds
180knots:
For the item RANDOM, another Drop-down box will appear allowing to choose the flight phase
in which the fault should occur. For this feature to work properly, it is important to have a flight
plan filed properly, otherwise the system cannot know how long a given flight phase (e.g. climb or
cruise) will last, which makes it difficult to ensure that the fault occurs during that phase.
The following flight phases can be selected:
• Take-off (Earliest fault occurrence possible is around 60kts)
• Climb
• Cruise
• Descent
• Landing
• Flight – in this case the fault is randomly injected during one of the 5 phases listed
above.
The following example shows in the second row a failure of the AC ESS bus that will happen
at some point during the cruise phase:
Useful hints:
Press the “Delete” button on the right of a fault line to clear that fault line.
The “Reset all faults” button is your friend: It clears all selected faults and reinstates the system
functionality. (Including Halon cleanup in case you had to extinguish an engine fire – the engine
will run again, but the fire extinguishing bottle remains empty.). It also clears faults injected by
the random fault injection system.
34
3.7.2 Random fault injection
Random fault injection can be activated and deactivated by the switch “Enable Random faults”:
Set to “1” to enable random
fault injection function
Failures are fairly rare these days and if we used the real-life MTBFs you would rarely see
failures during your flights. This is resolved by the “Flight Time Factor”. This factor is used to scale
up the flight time such that faults are more frequent. A factor of 1 means that the rate of failure is
the same as in real life. The maximum possible factor is 1000, in this case, failures occur 1000 times
more often than in real life. Example:
• Most airborne computer systems have Mean Time Between Failures (MTBFs) in the
range of 10000 flight hours per failure to 100000 flight hours per failure. Using a factor
of 1000 means that this computer will fail once every 10 to 100 hours.
Overall, there are about 90 failures that can be injected with different probabilities. With the
slider set to 1000 you will encounter about 3-4 failure per hour. If you are lucky the failures affect
the same system and you may lose systems completely.
We recommend a factor between 100-300 for interesting flights, that do not end in emergency
landings every time.
Note that when a fault is injected by the random fault system, it will appear in the list under
“Custom Fault selection”.
35
4 Cockpit orientation.
The aircraft comes with two different cockpits. A fully functional 3d cockpit model as well as an
easy-to-use 2d cockpit panel, which is more targeted for study purposes.
4.1 3d cockpit use

By default, this aircraft loads up in 3d cockpit view, unless the user sets the preferences
differently. (See section 2.8.2.) To get from any other view (external view, 2d panel, etc.) to the 3d
cockpit view, the X-Plane default command can be used:
sim/view/3d_cockpit_cmnd_look
By default, this command is mapped to the keys “Shift + 9”.
Moving the camera in the 3d cockpit is done via the default x-plane commands. Unless the user
changed the keyboard assignment, these are mapped to the keys “q” and “e” for left/right swivel of
the head, “r” and “f” for tilting the head up/down and “,” and “.” for moving the camera forward or
aft. Zoom is frequently assigned to the mouse wheel (unless the mousewheel handler of the ToLiss
Airbus A319 takes control of the mouse wheel for button manipulation.)
4.1.1 Special view commands

The ToLiss Airbus A319 ships with preprogrammed view commands that facilitate navigation in
the cockpit. We recommend using these. To get to the 3d cockpit forward view, use the command
toliss_airbus/3d_cockpit_commands/view_3D_straight
Using this command places the camera directly into the “eye reference point” of the cockpit, i.e.
the location for which the pilots typically adjust their seat. The command also considers if the user
selected to fly from the pilot or the co-pilot side (see next command). When flying from the co-
pilot side, this command will bring the viewpoint back into the co-pilot seat. X-plane’s default
command does not do that.
Caution: The custom view commands do not reset the “zoom” setting. If the view is not as
expected, try zooming out.
Swapping between pilot and co-pilot seats

To swap between flying from the pilot and the co-pilot side, use the commad
toliss_airbus/3d_cockpit_commands/view_3D_capt_fo_toggle
This command influences all other commands described in the section. If the user selected co-
pilot side, all other view commands will give the corresponding view on the right aircraft side; if
the user selected pilot side, all views will be on the left aircraft side.
Viewing pedestal and overhead panel

There are three custom commands to allow pointing the camera towards the pedestal or the
overhead panel:
toliss_airbus/3d_cockpit_commands/view_3D_pedestal_fwd
toliss_airbus/3d_cockpit_commands/view_3D_pedestal_rear
36
toliss_airbus/3d_cockpit_commands/view_3D_overhead_panel
First time the user presses the button assigned to one of this commands, it will tilt the camera
to view either forward portion of the pedestal (MCDUs, ECAM control panel, etc.), the rear of the
pedestal (engine master switches, spoiler lever, flap/slat lever etc.) or the overhead panel. A second
push of the same button brings the viewpoint back to forward view. (Same as executing the view-
3d-straight command listed above!)
Views from the cabin

We also preprogrammed two camera locations in the cabin, the “wing observer” and the “engine
observer”.
toliss_airbus/3d_cockpit_commands/wing_observer
toliss_airbus/3d_cockpit_commands/engine_observer
The wing observer sits on a window seat behind the wing looking out at the trailing edge. The
engine observer sits in one of the first rows looking out and back towards the engine. Note that the
side of the view depends on the pilot/co-pilot setting mentioned in the previous section.
Example view for the engine observer:
4.1.2 Popup displays

The ToLiss Airbus A319 supports popping up the 6 main displays, the 2 MCDUs and the Integrated
Standby Instrument System (ISIS). This feature allows to have a magnified image of the
corresponding display compared to the one in the instrument panel.
37
Popping up the MCDUs also allows using the keyboard to enter text into the scratchpad, to
accelerate flight planning.
In order to popup a display, hover the mouse over the corresponding display in the 3d cockpit.
The mouse pointer changes to show a magnifying glass:
A single click pops up the display. If the display is already popped up, clicking the screen on
the panel again closes the popup. Popups can be dragged around by clicking and holding and then
dragging the popup to the desired location. A single click (without dragging) on the popup closes
the popup window.
To use the keyboard for text entry on a popup MCDU, the user needs to place the mouse cursor
over the MCDU popup window. If the mouse is located over the popup, key strokes will be
interpreted as text entry into the MCDU. To drag the MCDU popup around, place the mouse
pointer over the screen portion of the MCDU and apply the same technique as for the other popup
windows. The same applies for closing the popup window. Mouse clicks away from the screen of the
MCDU are interpreted as pressing the nearest MCDU key.
Note that it is possible to change the size of the popup displays (except MCDU and ISI) with
the help of the mouse wheel. Hover the mouse pointer over the popped up window and use the
mouse wheel to change size in 5 steps between 250px x 250px and 500px x 500px.
Use of popouts in X-Plane 11

The ToLiss Airbus A319 supports the Xplane 11 feature of having the popup displays in separate
windows that can then be dragged to a different screen. In order to use this, the ISCS option “Use
popout windows for popups” must be enabled. See section 2.8.2 for details.
Note that if the option “Save popout config on Quit” is selected in the ISCS, the popped out
screens will be popped out again upon next opening, if the popout window is closed via the operating
system “close” button. To return the window into the regular X-plane window mode, close it by
clicking once into the popout window.
38
Click here to close the

popup. Next time you
open it, it will again be in
a separate window.
Click here (without dragging) to

close the popup. Next time you
open it, it will open as a window on
the x-plane screen.
4.1.3 Display brightness and cockpit illumination

The brightness of the displays and the cockpit lighting are controlled via the same switches as in
the real aircraft. Primary flight display (PFD) and Navigation Display (ND) brightness are
controlled via the rheostats besides each PFD. The ND rheostat has a small and a large knob. The
small (inner) knob is used to control ND brightness, the outer knob is used to control the intensity
of the weather radar of the terrain display image – see figure below. Note that turning the brightness
knobs all the way to the left turns the associated display unit off and it will pass through a power-
on self test when it is switched it back on.
PFD brightness ND brightness
WX radar / terrain
image intensity
The brightness of the two ECAM displays in the center of the cockpit, the “Engine Warning
Display” (EWD) and the “System Display” (SD) is controlled via two rheostats located on the
“ECAM Control Panel” (ECP) directly forward of the thrust levers:
EWD brightness
SD brightness
39
MCDU display brightness is controlled by a knob of the MCDU itself; it is located to the bottom
right of the MCDU screen. Note: Here is an unfortunate misalignment between 3d model and popup
screen. On the 3d model, the brightness is changed via two push buttons labels “BRT” (brighter)
and “DIM” (less bright). On the popup screen and in the 2d panel, the brightness regulation is a
rheostat.
The brightness for the Integrated Standby Instrument System (ISIS) can be controlled via the
“+” and “-“ buttons directly on the unit.
Cockpit lighting consists of the Dome light, the pedestal and main panel flood lights as well as
the panel integrated lighting.
The dome light provides general illumination of the cockpit; it is powered by the essential DC
bus and is hence available on battery power only and during electrical emergencies. The dome light
control is located in the overhead panel on the “INT LT” panel. The light can be operated in three
modes: OFF (no light), DIM (half brightness), or BRT (full brightness):
The flood lights provide general lighting for the main panel and the pedestal. The associated
brightness controls are located in the pedestal just aft of the thrust levers:
Main panel flood light brightness
Pedestal flood light brightness
The integrated lights are the background lighting of the white labels and symbols in the main
panel, the pedestal and the overhead panels. The integrated lights can be controlled via 2 separate
rheostats, one for main panel and pedestal and a separate one for the overhead panel.
The main panel/pedestal integrated light intensity is adjusted via the knob on the left-rear of
the thrust levers.
Main panel and pedestal

integrated light brightness
Last but not least, there is a switch to control the brightness of the lights integrated into the
push buttons in main panel, pedestal and overhead panel. The associated switch is located in the
overhead panel in the “INT LT” section and is labelled “ANN LT”. It has three positions: DIM
(lights at half brightness), BRT (lights and full brightness) and TEST (power all lamps to check
for broken bulbs.) At daytime, this switch would be in position BRT, at night in position DIM and
prior to take-off you typically move it to position TEST for a short moment to check that all lamps
work:
40
4.1.4 Mouse wheel use

The 3d cockpit supports the use of mouse wheel for all rotary-type knobs in the cockpit. This
includes brightness knobs, loud speaker volume, Navigation display mode and range, altimeter
setting, Autopilot selection knobs and many others. Mousewheel use can be turned ON or OFF via
the appropriate option in the ISCS on the tab “Settings/Actions” – see section 2.8.1 for details.
When mousewheel support is on, the mouse pointer changes to the following shape, if the wheel
can be used to manipulate a cockpit knob, this is referred to as the mousewheel pointer:
For cockpit buttons that allow rotating and pushing and/or pulling, one or two dots appear in
the center of the mouse wheel pointer. If a single dot is visible in the mouse wheel pointer, clicking
the left mouse button triggers a “push” action on the corresponding cockpit control. If the mouse
pointer shows 2 dots, a left mouse button click triggers a “pull” action on the cockpit control. For
more details, see section 4.1.5.
If two rotary controls are nested inside each other, like for example with the ND brightness
button, the size of the mouse wheel pointer indicates which control is manipulated. The large
pointer is shown, if the outer knob is rotated, the small symbol is shown for rotation of the inner
knob.
Operation with mouse wheel off

If the mouse wheel option is switched OFF, the mouse pointer changes shape as usual to indicate
the actions associated with clicking the left mouse button:
• For knobs/rheostats that can be rotated, an arrow will appear showing the direction of
rotation that would be executed when the left mouse button is pressed. For concentric
rotary knobs (e.g. ND brightness and WX intensity knobs), the size of the arrow
indicates which of the two knobs will be rotated. The following image shows the pointer
size when the outer knob (WX intensity) will be rotated upon mouse click:
41
• Similar to the case with mouse wheel use activated, buttons allowing rotation and
pushing/pulling are shown by the rotary mouse pointer with one or two dots in the
center. In this case a single click, or click-and-hold rotates the knob, and a double click
either pushes (one dot shown) or pulls (two dots shown) the knob. The following image
shows mouse pointer interaction at the FCU speed selection button with a double click
pulling the button:
4.1.5 FCU operation

The FCU, or flight control unit, is used on the aircraft for interaction with the autopilot system.
To the left and right side of the FCU are the two EFIS control panels that are used to configure
the Primary Flight Display (PFD) and the Navigation Display (ND) for each pilot.
The four rotary knobs on the FCU can be rotated, pushed and pulled. The exact functionality
is described in the autopilot section of the “aircraft manual”, this section served to point out how
to achieve the specific action in the ToLiss Airbus A319. As discussed in section 4.1.4, rotating the
knobs is achieved via the mouse wheel, if selected, or via clicking-and-holding, if mouse-wheel is off.
Pushing the button (you push the aircraft away from you, i.e. revert to managed mode) is achieved
by placing the mouse pointer in the upper half of the button, so that a single dot appears in the
mouse pointer:
42
Circle indicating managed

mode for this control.
Clicking once (mousewheel function ON) or double-clicking (mouse-wheel selected off) then
pushes the selector and reverts to managed mode. The key indication for managed mode is the
appearance of the white circle next to the numbers/dashes. Note that, especially with mouse wheel
off, it may happen that you rotate the control at the same time that you push it. In this case, the
numbers will appear in the window instead of dashes. Managed mode will still be active, as long as
the associated white circle appears. Note that the altitude window in the FCU never shows dashes.
More details are available in the “Aircraft manual”
Analogously, for pulling the knob (you pull the aircraft towards you, i.e. revert to selected
mode), you place the mouse pointer in the lower half of the knob and two dots appear inside the
knob:
Clicking once (mouse-wheel on) or double-click (mouse-wheel off) now pulls the selector
reverting to selected mode. The dashes above the knob will be replaced by numbers and the white
circle next to the numbers disappears.
The baro-selectors for pilot and co-pilot PFD allow pushing action to toggle between QNH and
STD baro setting. Similarly to the FCU buttons, this is indicated by a single dot in the mouse
pointer when hovering over the knob and the action is performed by single-click (mouse-wheel on)
or double click (mouse-wheel off).
Three of the FCU knobs have a little two-way selector attached to it:
• The altitude-knob has the 100/1000 foot selector
• The 2 baro-setting knobs have the unit selector to switch between inHg and hPa as
units for the atmospheric pressure.
These selectors are manipulated by placing the mouse pointer above the knob such that a left-
right arrow appears:
When this arrow is visible you can use a single click of the left mouse button to toggle the
position of the selector. With the mouse wheel function active, you can ALSO use the mouse
wheel to change the position.
Note that the selection of baro-pressure, flight director, landing scales for the PFDs and the
selection of the ND mode, range, and other options is completely independent between the left and
43
right side. You can have the left ND operating in mode Arc with a range of 160NM, while the right
ND is in mode NAV with 10NM, if you wish. For landing, you could, for example, place one ND in
mode ILS and select mode ARC for the other. For the baro pressures it is important to always do
the appropriate selection on both sides, otherwise you will get the ECAM warning “NAV BARO
REF DISCREPANCY”:
This message disappears, as soon as you have selected the same baro-setting for the left and
right side.
4.2 2d cockpit use

Note: This section only applies to the aircraft with combined 2d and 3d panel. (Ask x-plane.org
support for a download link if you think you will use the 2d panel also.)
When using the aircraft with 2d panel, 2d cockpit from the precursor of this product, the QPAC
320, is still available, as for some simulation uses, this may be more practical. This section
summarizes the use of the 2d panel, especially with respect to popups and the different click ones
for the FCU.
To transition from the 3d cockpit to the 2d panel, use the X-plane standard commands:
sim/view/default_view, or
sim/view/forward_with_2d_panel
These commands are by default mapped to the keys “w” and “Alt+w”.
The panel itself is larger than a screen with 1920 pixel width, it therefore needs to be scrolled
to access certain areas. Scrolling is performed using X-plane standard commands, which are usually
mapped to the cursor (arrow) keys.
Pedestal popup
In order to see the pedestal and gain access to all the relevant controls on it (Thrust levers,
communication frequency selection, transponder, parking brake etc.) click into the area showing
the captain’s or the copilot’s pedals. To remove the pedestal from view, click into the area next to
the Speedbrake lever (captain’s side) or the flap/slat lever (copilot’s side).
44
Click on the
pedals
Click next to
Speedbrake
lever
Display popups
Similarly to the 3d cockpit, the different display units (PFD, ND, EWD, SD, ISI, MCDU) can
be popped up and moved around. In order to popup a display, just click once on the desired display.
To close the popup, click again on the display or on the popup. To move the popup simply click
on it and while holding the left mouse button, drag it to the desired position.
Popups of the 6 display units (PFD, ND, EWD, SD) can be scaled in size by using the mouse
wheel when the mouse pointer is hovering over the popup.
If you close a popup window, its size and position are remembered for the next time you pop it
up again.
Click in screen to
remove popup.
Click in screen to
remove popup.
Click in this area to Click in this area to

popup MCDU1 popup MCDU2
Note: Same as with the 3d cockpit, all keyboard inputs will be interpreted as pressed MCDU keys,
as long as the mouse pointer is hovering over the popup MCDU.
45
4.2.1 2d cockpit lighting

The 2d panel features the same adjustable lights for illuminating the cockpit as the 3d cockpit.
The dome switch on the Overhead Panel is to control both dome lights, providing a general
background lighting to the cockpit. To the left of the dome switch is the INTEG LT brightness
knob which adjusts the brightness of integral lighting for the overhead panel and turns it on and
off.
Choose bright, dimmed or off Dome light
INT LT panel located on the overhead panel
The “ANN LT” switch to the right of the Dome light switch can be used to select the brightness
level of the annunciator lights that are integrated into the push buttons. Setting it to position
TEST illuminates all the annunciator lights at the same time. This is used in real life to verify that
no bulbs are burnt.
ANN LT switch set

to position TEST
Pedestal and main panel illumination is controlled via two knobs located on the pedestal to the
right and the left of the thrust levers:
46
Turn for adjusting the integral

Turn for adjusting flood lighting lighting
The FLOOD LT MAIN PNL located to the left of the thrust levers adjusts the brightness of
the flood lighting for the center instrument panel and turns it on and off. The pedestal flood light
can be adjusted via a separate knob labelled FLOOD LT PED located to the right of the thrust
levers. The INTEG LT adjust the brightness of integral lighting for the main panel and pedestal
and turns it on and off.
4.2.2 FCU use in 2d cockpit

The FCU, or flight control unit, is used on aircraft for interaction with the autopilot system.
The four rotary knobs on the FCU can be rotated, pushed and pulled. The exact functionality is
described in the autopilot section of the “aircraft manual”, this section served to point out how to
achieve the specific action in the ToLiss Airbus A319. Specific click-zones are defined for each of
the possible actions with the rotary knobs (push/pull/rotate). These are shown in the following
figure:
Heading Selector knob Altitude Selector knob PUSH V/S selector knob
PUSH (arms NAV mode) (engages CLB or DES mode) PUSH (Engages V/S
mode with target 0fpm)
(selected mode)
Speed Selector knob
PUSH (managed target) V/S selector knob
PULL (Engages V/S
mode on current V/S)
Speed Selector knob (selected mode)
PULL (selected target)
Arm LOC and GS mode
Heading Selector knob Altitude Selector knob PULL (engages

PULL (engage HDG mode) Arm LOC mode OP CLB or OP DES mode)
EXPED button. Engages EXP CLB or
EXP DES mode (Selected modes!)
Pushing the button (you push the aircraft away from you, i.e. revert to managed mode) is
achieved by placing the mouse pointer above the button and clicking the left mouse button. The
key indication for managed mode is the appearance of the white circle next to the numbers/dashes.
Analogously, for pulling the knob (you pull the aircraft towards you, i.e. revert to selected
mode), you place the mouse pointer centrally on the knob and click the left mouse button. The
respective mode will revert to selected mode, the dashes above the knob will be replaced by numbers
and the white circle next to the numbers disappears.
47
Rotating a knob is achieved by clicking to the left (reduce the value shown in the window) or
to the right (increase the value shown in the windows) of the rotart knob. The mouse pointer
changes appropriately to indicate the current click action.
48
5 Troubleshooting
The ToLiss Airbus A319 is a very complex product and naturally you may encounter issues. During
testing we may have identified some issues that may occur under certain circumstances for which
we will provide a solution in this section. Please verify this section prior to asking for support in
the forums.
5.1 Aircraft does not load or looks strange after loading

The following issues have been encountered by users causing the airplane not to load at all or to
load without buttons working:
• The XP11-version of the addon requires XP11.30 or newer. XP11.00 to 11.26 are not
supported. Update your X-Plane 11 if required.
• Windows-Specific: If none of the switches work under windows, you may have exceeded
the dll-limit. X-Plane has a limitation on the number of dlls that plugins can link in
and on installation with lots of scenery (using the ground traffic plugin), this limit may
be exceeded. In that case the ToLiss Airbus A319 cannot load it’s plugins. Reduce the
amount of scenery with the ground traffic plugin.
• Linux-specific: The aircraft requires the following libraries to be installed: libcurl.so.4,
libssl.so.1.1 and libcrypto.so.1.1. On the current main Linux distributions, these libraries
are standard. On older software versions they maybe missing. Check the log file for the
exact missing library. The relevat line is where x-plane loads the plugin:
AirbusFBW_A319_XP11/64/lin.xpl.
Note that installing libcurl.so.4 normally will also install libssl.so.1.1 and
libcrypto.so.1.1.
5.2 System crashes

We have done extensive debugging and code verification exercises in order to minimize the risk for
system crashes. Nevertheless they may happen; x-plane itself is not 100% crash-free. If you
encounter crashes, please consider the following:
• Always fly with “Autosave enabled” – like that if you have a crash you can simply
restart x-plane and continue where you left off
• In X-plane 11, our implementation of the popup displays may be causing issues. If you
experience crashes please minimize the use of popups. Close them once your done with
them and don’t swap between inside and outside views with the popups open.
• If you encounter crashes for which the x-plane log states that the application crashed
due to one of the following plugins:
o AirbusFBW A319
o ToLiSs SoundPlayer
Please submit the log-file and the last autosave situation on the website
www.toliss.com together with a detailed description what you were doing between the
time of the autosave and the crash so that we can reproduce the issue. Crashes that are
49
not indicated by X-plane to be caused by one of the plugins above will not be
investigated.
5.3 FMGS path jitter

If you encounter a case in which the flight plan jitters, i.e. the ND shows many different paths in
very quick succession (looks almost like a flashing screen) and the waypoints on the MCDU toggle
position, please do the following:
• Perform a situation save via ISCS so that you can submit this issue later on the ToLiss
issue tracker.
• Select another SID or another STAR Via. Chances are that another route will not have
this issue.
Don’t forget submitting the situation file on our website www.toliss.com
© Airbus 2019. AIRBUS, its logo and product & service marks are registered
trademarks of Airbus. All rights reserved. Officially licensed by Airbus.
50

ToLiss AirbusA319 V1.3.3 SimulationManual

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ToLiss AirbusA319 V1.3.3 SimulationManual

Uploaded by

Copyright:

Available Formats

Simulation Solutions

ToLiss Aeronautical Simulation Solutions

ToLiss Airbus A319 V1.3.3 – Simulation manual

3.7 Fault injection interface ............................................................................................... 32

2 Aircraft installation and Xplane setup

2.1 Special requirements in Windows

2.2 Special requirements in Linux

Make sure to select the correct

2.4 Aircraft activation

You can use this button to

Set this to 1 in order to provide your approval that

Use this button to contact the

“Xplane/Resources/plugins/ToLissTerrainData”. This will allow keeping the activation

2.5 Livery installation

2.6 Alternative cockpit textures

2.7 Joystick setup

ALT selector knob PULL

A/THR Button on FCU push

HDG selector knob PULL

AP Instinctive disconnect button

2.7.1 Other mapped x-plane commands

2.7.2 Detailled axis setup and status check

Verify that all axes that you

Leave all axes centered and press this

Joystick sensitivity in X-plane 11

Assignment of the sidestick priority buttons

2.7.3 Custom commands

- Custom commands to trigger pushing the FD-buttons on the FCU:

- Custom command to trigger pushing/pulling the HDG-knob on the FCU:

- Custom command to trigger pushing/pulling the ALT-knob on the FCU:

2.8 Simulation configuration

2.8.1 Settings/Actions page

The settings and actions page provides:

Ovrd XP start setting:

Cold start type / Start up type:

ILS AUTO ALIGN

JOYSTICK ROLL FOR NWS

REGULAR BRAKE STRENGTH

USE MOUSE WHEEL

F1/F2 CAN TOGGLE REVERSERS

A/C HAS FLORENCE KIT

XPDR COMPATIBILITY MODE

SYNC BARO SETTINGS

2.8.2 Audio-visual settings

Aircraft version with

These sliders are set to zero by the ToLiss

2.9 Navigation data – location and update

2.10 IAE sound pack activation

Enter key from X-plane.org store here

2.11 Third part add-on compatibility

At this stage, compatibility is confirmed with:

2.11.1 Smartcopilot use

2.11.2 System simulation/FMS 3rd party add-ons

The ToLiss Airbus A319 is compatible with:

The ToLiss Airbus A319 is not compatible with:

3 Use of ISCS during the flight

3.1 Resume from last time

The function reloads one of the following two aircraft states:

3.2 Special actions

ADIRU QUICK ALIGN

JUMP TO NEXT WPT / JUMP 100NM

3.3 Situation loading and saving

3.4 Aircraft loading and TO performance calculation

3.4.1 Selecting payload