The Navigation Display (ND) on the iniBuilds A350 Airliner can display terrain and obstacles information when the TERR ON ND pushbutton is pressed. This function relies on a Terrain Database which is downloadable via the OIS - 3RD PARTY OPTIONS page.

(Click to enlarge image)

Why is this required?

• This process helps ensure terrain data integrity by minimizing risk of corruption whilst streaming the package.
• This process reduces overall bandwidth usage whilst streaming the package.

When is this required?

• This process only needs to be done once when you first launch the A350 Airliner after your purchase.
• The process does not need to be repeated when updating the aircraft - unless stated specifically in the changelog.
• The process is only required again IF you manually delete your Terrain database (.bin) file which is located within the WASM/Work folder.

Quote

Note: Clearing your WASM/work folder will also delete the Terrain database file. You will need to repeat the process in that instance.

How to download terrain data?

1. Navigate to the Options > 3rd Party  > Download Terrain Data section on the EFB
2. Press the START DOWNLOAD button and wait for the download to complete.
3. Once completed, you will see a notification at the top of the EFB Display.
4. Press ESC to return to main menu and restart your flight for the changes to take effect properly.
    

Quote

Note: The Terrain database (.bin) file is approximately 292 MB in full which is downloaded in two parts. These are automatically combined into a single file at the end. Please be patient and allow some time for the process to complete. 

On a 100mpbs connection, the process is usually completed within 60s.

Quote

Note: The sim may freeze during the process as data is transferred within the sim Virtual File System (VFS). Please be patient and allow some time for the process to complete.

(Click to enlarge image)

 Taxi Camera Lights - ON vs OFF  - FS20
(Click to enlarge image)

To Enable Taxi Camera Lights

You must ensure all of the following:

• Under OIS Equipment Settings > Taxi Camera Light is set to ON; and

(Click to enlarge image)

• TAXI pushbutton on EFIS CP is set to ON; and

(Click to enlarge image)

• NOSE LT switch is set to TAXI or T.O.; and

• Main Landing Gear (MLG) is on the ground

Quote

NOTE: FS2024 Users - The OIS Equipment setting - Taxi Camera Light may be controlled by your airline configuration file that comes included with the installed livery.

(Click to enlarge image)

To manually override, you may edit the LiveryConfig.cfg file included in the livery package and ensure it reads INI_OPTION_TAXI_CAM = 1  accordingly. The changes will take effect after sim restart.

(Click to enlarge image)

For more information on the Livery Config file, see 

 

Accessing the Planner
The new planner has its own dedicated page which can be reached via FLT OPS MENU > FLT OPLS PLAN. 

(Click to enlarge image)

Quote

Note: You must connect to your Navigraph account & enter your Simbrief ID (numbers only) on the third-party options page which can be reached via FLT OPS MENU > OPTIONS > 3RD PARTY. You can connect by

• Scanning the shown QR Code, OR
• Navigating to https://navigraph.com/code and enter the code shown on the OIS.

(Click to enlarge image)

After you have completed the authentication steps the OIS will update to show the additional 'UPDATE DATA' and 'RESET NAVIGRAPH' options.

(Click to enlarge image)

 

Creating a SimBrief Flightplan via the Planner

In order to create your flight plan, only the following fields are mandatory

• FROM* - Input your Departure airport's 4-letter ICAO code here (e.g. LPFR)
• TO* - Input your Arrival airport's 4-letter ICAO code here (e.g. EGLL)

Then, press the GENERATE PLAN button to create a SimBrief Flightplan using the default "AUTO" values. 

(Click to enlarge image)

 For additional customization, you can also tweak the below fields which are optional

• ALTN - Input your Alternate airport's 4-letter ICAO code here (e.g. EGCC). Default value is AUTO.
• AIRLINE - Input any 3-letter ICAO airline code (e.g. BAW)
• FLT NUM - Input any alpha-numeric flight numer (e.g. 25A)
• FROM RWY - Select your Departure airport's desired runway. Default value is AUTO.
• TO RWY - Select your Arrival airport's desired runway. Default value is AUTO.
• PAX - Input the number of desired passengers. Values exceeding the MAX will use MAX instead. Default value is AUTO.
• FREIGHT - Input the desired weight (KG/LBS) of cargo. Values exceeding the MAX will use MAX instead. Default value is AUTO.
• CRZ FL - Enter your desired Cruise altitude in 3-digit flight levels (e.g. 380 for 38,000ft). Default value is AUTO.
• REG - Enter your desired aircraft registration. Default value is autofilled from the ATC ID field of aircraft.cfg.
• CPT NAME - Input custom Captain's Name on the OFP. Default value is AUTO.
• FO NAME - Input custom First Officer's Name on the OFP. Default value is AUTO.
• PLAN - Choose the desired OFP format from the list that shows on screen. Default value is LIDO.
• FUELING section -  Choose between WEIGHT or MIN units and enter the desired numeric value for that particular fuel section on your OFP. Default value is AUTO. 

To reset the page back to its default state, click the CLEAR button.

(Click to enlarge image)

To change the planning units between KG/LBS, change the Aircraft Weight Units from the OIS Settings page.

(Click to enlarge image)

Using your New Flightplan - OFP

Once you have successfully generated a flight plan, the OIS will automatically go to the OFP page and give you a 'PLAN GENERATED SUCCESSFULLY' notification at the top of the screen. That's it! Your new flightplan is now active on SimBrief, same as if you had generated via their Dispatcher Tool or Website.

Now you may use this new plan on the FLT OPS STATUS, LOADSHEET, TO PERF or LDG PERF pages of the OIS by Importing or syncing with Simbrief as usual. You may also request your new flightplan on the FMS via the CPNY F-PLN REQUEST button on the INIT Page.

For more information please see the following guides:

Creating Custom Saves via the OIS

To create a custom save via the OIS:

• Navigate to OIS Autosave Page (FLT OPS MENU > AUTOSAVE)
• Click 'SAVE NOW' button at the top right corner
• Enter a desired name for the autosave
• Your custom save will appear on the list on the right side of the page. 

(Click to enlarge image)

Quote

Note: All custom and auto saves are deleted whenever you clear your WASM folder.

Loading Custom / Auto Saves via the OIS

To any save file via the OIS:

• Navigate to OIS Autosave Page (FLT OPS MENU > AUTOSAVE)
• Click the desired save from the AUTOSAVES or CUSTOM SAVES list.
• The sim may take a few seconds to load the proper panel states after teleporting you to save location.

(Click to enlarge image)

Sharing Custom Saves

All custom and auto saves are stored as ".bin" files in your WASM folder. These can be shared with other users or our staff for support requests. Simply drop the save files in the folders listed below and then reload the OIS autosave page to see it on the list.

The autosaves folder is found at the various paths listed below:

Quote

FS20 Steam:
%APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a350\work\autosaves

FS20 MS Store:
%LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a350\work\autosaves

FS24 Steam:
%APPDATA%\Microsoft Flight Simulator 2024\WASM\MSFS2024\inibuilds-aircraft-a350\work\autosaves

FS24 MS Store:
%LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\inibuilds-aircraft-a350\work\autosaves

(Click to enlarge image)

The WebAssembly Module (WASM) is a container for running programmes written in other langauges (eg C/C++) that is then converted to native code ahead of time (as DLLs) during first launch (WASM Compilation). This helps improve performance for subsequent uses but causes longer load times on first launch. See for more info: 

This improves security of the sim and portability of projects across PC/Xbox. In case of issues, only the WASM crashes instead of the rest of the sim along side with it. This is why the sim and some functions may continue to work, however other systems and displays that use WASM on the aircraft become unresponsive or "freeze" in place. 

So what to do in case of WASM crash?

• Do not close the sim/restart flight immediately
• Verify the WASM error message
• Report the WASM error message with reproduction steps using the guide below.

Verify WASM Crash in Sim

Step 1. Enable Developer Mode 

(FS20) Options > General Options > Developers


(FS24) Settings > General > Advanced Options 

Step 2. Enable the Console by pressing "~" key on your keyboard or using the Dev Toolbar at the top of the screen

Step 3. Filter the Console by ❌Error messages only by clicking on ⚠️Warning and ℹ️Messages to disable them
(remove blue box border around them). 

Step 4. Type 'WASM' in the search box. Find the WASM Error and Copy the message. Also take a screenshot of this console window for making a report.

Report WASM Crash on Forum

Step 5. Paste the WASM Error message and screenshot of the Console obtained in Step 4 above into a forum post WASM Crash Report.

Step 6. Take note of what you pressed or things you did, just before you noticed this crash happen.

Step 7. Verify if you are able to repeat the crash by following those same steps.

Step 8. Please provide the following information

• Aircraft: A350-900 or -1000
• Simulator: FS2020 or 24
• Navdata Method: SIM DEFAULT or NAVIGRAPH
• OFP: Include a PDF of your Operational Flightplan (OFP) if related to FMS/Route Procedures crashes
• WASM Error: The error you copied in Step 4 above
• Specs: CPU, GPU and RAM of your system.
• Autosave File:  Please include the latest ".bin" autosave file prior to your crash. 

Step 9. Where possible, include on your report

• a Screenshot / Video showing what you pressed/did just before the crash happened to give us more clues. 
• steps on how to reproduce the crash so that we can try ourselves with debugging tools to identify the cause of crash.
• the ".bin" Autosave File which is the latest save from prior to your crash to help us reload into same scenario.
  
  FS24 Autosave Folder Paths
  - Steam: %APPDATA%\Microsoft Flight Simulator 2024\WASM\MSFS2024\inibuilds-aircraft-a350\work\autosaves
  - MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2024\inibuilds-aircraft-a350\work\autosaves
  
  FS20 Autosave Folder Paths
  - Steam: %APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a350\work\autosaves
  - MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a350\work\autosaves
  
  

These types of WASM crashes are actionable depending on your reports of the steps taken immediately before the crash happened. If reproducible on our end by following the same steps, can be debugged and resolved more efficiently. 

Quote

Example WASM Crash Report

I had this WASM crash when I clicked the VIDEO button on the center pedestal.

To reproduce

• Load at gate
• Power on aircraft (Battery, GPU)
• Click VIDEO button
• Systems freeze 

Information

• Aircraft: A350-900
• Simulator: FS24
• Navdata Method: NAVIGRAPH
• OFP: Not required, happens on any route
• Specs: Ryzen 5800X, RTX 3070, 16GB RAM
• Autosave: Attached latest .BIN file before crash
• WASM: Error during MFD_gauge_draw execution. Error code : 0xc0000005

If you find yourself with your EFIS CP displays blank as above, ensure that on the MFD FCU BKUP page that EFIS CP BACKUP is disabled as follows:

• On the MFD Menu Dropdown select the FCU BKUP option
  
   
• Ensure you are on the EFIS CP page and verify that the the EFIS CP BACKUP button light is off (not green)
  

Quote

Note: Changing units will clear all weights from the FMS and can affect VNAV calculations, so you should only change these units whilst on the ground or whenever safe to do so.

The aircraft weight measurement units (LBS / KGS) are changed on the OIS Settings Page which can be reached via FLT OPS MENU > OPTIONS > OIS SETTINGS. Select your desired unit by clicking on its respective button. 

(Click to enlarge image)

Quote

Note: This process may take upto 10 minutes and you will see an OIS NOT AVAIL alert whilst that happens.

Change OIS Boot Time

You can change the OIS Boot Time via the OIS Settings page (FLT OPS MENU > OPTIONS > OIS SETTINGS)

• REAL: Set by default - can take up to 10 minutes.
• FAST: Can take up to 5 minutes
• INSTANT: Will boot up instantly upon availability of GPU/APU power.

As with all other WASM aircraft, the simulator needs to compile the necessary WASM files on first launch. However it will be much faster to load on subsequent launches.

Quote

Note: This may take upto 20 minutes on the first launch of the selected variant (depending on your hardware).

Quote

Note: Do not close your sim or return to menu whilst this is happening. Please be patient and wait for the WASM compilation to complete or else you risk having an incomplete WASM compile which may lead to instability/weird behaviours.  

In case your sim crashes or you exit to menu during this initial WASM compile, please see the guide below to clear your WASM folder and try again:

Example if your flight plan page shows EGLL but you have inserted a runway and STAR along with ILS then reselect them until you have EGLL27L shown on the F-PLN page, this goes for all airports. If not done the aircraft can possibly not work out the VNAV path and cause a WASM crash.

Throttle Calibration Page (OIS)

Before you fly, you must calibrate your throttles via the On-board Information System (OIS) display Options > Throttle Calibration Page.

(Click to enlarge image)

Reverser on Axis Option

Verify whether your hardware has a reverse thrust on an axis or not then choose the appropriate option.

'REVERSER ON AXIS' is set to NO:  

• The bottom most position of your hardware axis (0%) will be assignable to the IDLE detent position.
• You may have to bind 'HOLD' / 'TOGGLE  REVERSE THRUST' sim control binding to an additional button / input on your hardware to use reverse thrust.
• This option is recommended for majority of the more commonly used hardware equipment (including Xbox Controllers).

'REVERSER ON AXIS' is set to YES:  

• The bottom most position of your hardware axis (0%) will be assignable to the MAX REV detent position for thrust reverser operation.
• You can additionally define separate IDLE and IDLE REV detent positions.
• This option is recommended for hardware such as the TCA Airbus Throttle Quadrant.

(Click to enlarge image)

Global Deadzone Option

You may define a 'Global Deadzone %' for all detents or input an individual 'DZ%' manually for each detent during the Throttle Calibration Process which we will cover below.

The present deadzone % boundary is also shown visually on the axis diagram to the right via white lines above/below your present AXIS % value. These lines indicate that the assigned detent will activate whenever AXIS 1 & AXIS 2 % values are within the two white lines. The larger the number, the further apart the white lines will be meaning the the detent is engaged for a larger range of hardware axis movement.

'USE GLOBAL DEADZONE' is set to YES:  

Quote

Note:  If you want to change the 'GLOBAL DEADZONE %' value, it will only apply after you conduct the Throttle Calibration Process again. 

• Use this option if you want all the detents to have the same deadzone value automatically after you complete the Throttle Calibration Process described below.
• Enter a number in the 'GLOBAL DEADZONE %' text box immediately below (Default is 2.5%).
• The value entered will be applied to all detents (MAX REV / IDLE REV / IDLE / CLB etc.) whenever you click any of the detent buttons.

'USE GLOBAL DEADZONE' is set to NO:  

Quote

Note: If you want to change the 'DZ %' value for any detent, it will only apply after you conduct the Throttle Calibration Process again.

• Use this option if you want some of the detents to have a different deadzone value when you complete the Throttle Calibration Process described below.
• Enter a number in the 'DZ %' text box immediately below the detent buttons.
• The value shown will be applied ONLY to whichever detent button (MAX REV / IDLE REV / IDLE / CLB etc.) you click.
• You can then change this value and click a different detent button, and it will apply the shown value as the deadzone for that detent.

(Click to enlarge image)

Throttle Calibration Process

Quote

Note: You will have to repeat this process if you want to change DEADZONE % or REVERSER ON AXIS option.

You may begin the calibration process by physically moving your hardware axis to your desired position, then clicking the desired detent button (e.g. IDLE/CLB etc.) on the OIS to assign the shown AXIS 1 & AXIS 2 % to that respective detent.

Example #1  - Reverser On Axis = NO

To define the IDLE detent on hardware without reverser on axis:

(Click to enlarge image)

• Move your hardware axis physically to its idle position (e.g. AXIS 1 & AXIS 2 will typically read 0%)
• Set your desired 'GLOBAL DEADZONE %' or Deadzone (DZ%) for the current detent.
• Press the 'IDLE' detent button on the OIS.
• A green notification at the top of the screen ('Calibration: Idle Set') will confirm the IDLE detent is set to your present hardware axis position.
• Repeat the same process for each desired detent from IDLE to TOGA.

Example #2  - Reverser On Axis = YES

To define the CLB detent on hardware with reverser on axis:

• Move your hardware axis physically to the desired position ( e.g. AXIS 1 & AXIS 2 may read ~50% on TCA Airbus Throttle Quadrant on its physical CLB detent but may vary per your hardware)
• Set your desired 'GLOBAL DEADZONE %' or Deadzone (DZ%) for the current detent.
• Press the 'CLB' detent button on the OIS.
• A green notification at the top of the screen ('Calibration: Climb Set') will confirm the IDLE detent is set to your present hardware axis position.
• Repeat the same process for each desired detent from MAX REV to TOGA.

(Click to enlarge image)

Quote

Note: TCA Airbus Throttle Quadrant users - Ensure you assign your throttles to THROTTLE 1 AXIS (0 to 100%) and THROTTLE 2 AXIS (0 to 100%) for the best results.

 

Our aircraft are best used with linear sensitivity settings for your axis, with deadzones as necessary for your hardware. To set this, go to your Settings > Control Options > Sensitivity Settings and set it up as shown below.

iniBuilds A350 Airliner.pdf

On the iniBuilds A350 Airliner you can set the visual weathering on the aircraft exterior via the On-board Information System (OIS) display. This adds affects of weathering around rivets and general dirt/grime over various components of the exterior that is persistent per variant.

OIS Weathering Slider

You can control the various levels of weathering on the OIS Aircraft settings page which can be reached via FLT OPS MENU > OPTIONS > AIRCRAFT.

(Click to enlarge image)

Fixed vs Dynamic Weathering

The weathering behaviour differs depending on the simulator in use as follows

• MSFS 2024 - Dynamic: The initial weathering state is set by the OIS Weathering slider and continues to dynamically increase over time. It will be manually "reset" by adjusting the slider.

  Quote

  Note: The OIS Weathering slider itself does not dynamically move over time. It is only used to set the initial weathering state whenever moved. However you will notice the dirt, grime and weathering of rivets change over time externally.

  
   
• MSFS 2020 - Fixed: The weathering state is set by the OIS Weathering slider and remains at that that setting until until manually "reset" by adjusting the slider.

  Quote

  Note: The weathering state is persistent, per variant, over different sim sessions until manually "reset" by adjusting the slider.

Overview

The iniBuilds A350 Airliner comes with a plethora of liveries made by our in-house artists for you to faithfully re-create your preferred Airlines experience. These liveries are available for download via the iniManager directly into your sim's Community folder.

IniManager - Installation & Setup
New Users

1. Download the latest version of iniManager from https://inibuilds.com/pages/inimanager-v2
2. Log in using your iniBuilds Store account.
3. Set your MSFS 2024 / 2020 Community Packages Folder paths:
   a. Default Location: Press the 'Scan Now' button to run an automatic scan for the default Community folder path. 
   b. Custom Location: Press the '...' button to manually navigate to your custom Community folder path.
   
    
4. Done! You may now download your desired products and liveries.

Existing Users

1. Ensure you have the latest version of iniManager from https://inibuilds.com/pages/inimanager-v2
2. Go to the iniManager 'Settings' page by clicking on your name on the top left corner.
   
    
3. Verify your MSFS 2024 / 2020 Community Packages Folder paths are defined correctly under the 'Configure Sim Path' section:
   a. Default Location: Press the 'Scan Now' button to run an automatic scan for the default Community folder path. 
   b. Custom Location: Press the '...' button to manually navigate to your custom Community folder path.
   
   
    

   Quote

   Note: The iniManager cannot change your community folder's location. The path chosen here is simply instructing iniManager where to install the packages downloaded via the iniManager. 

4. Done! You may now download your desired products and liveries.

IniManager - Liveries Management
Accessing Liveries

1. Open the iniManager
2. Select the 'Liveries' from the sidebar
   
    
3. Select the 'A350 Airliner FS24' or A350 Airliner FS20'
   
   
    
4. Find your desired livery from the list. You may use the 'Filters' or 'Search Liveries' section at the top-right corner.
   

Installing Liveries

1. Click the 'Install' button on the desired livery.
   
    
2. Read the disclaimer and press 'I Understand' button.
   
    
3. Wait for the download to complete. You can see the status of your download via the Active Downloads icon on the top right corner.
   
    

   Quote

   Note: Your download will be queued in case there is already an active download running. You may queue multiple liveries at once for download.

4. Done! You may now close the iniManager.

Uninstalling / Updating Liveries

1. Click the 'Uninstall' or 'Update' button on the desired livery. 
2. Done! You may now close the iniManager.

SYSTEM OVERVIEW

The Surveillance (SURV) system consists of the following system that perform surveillance functions:

• Traffic Collision Avoidance System (TCAS)
• Automatic Dependent Surveillance - Broadcast - Traffic (ADS-B Traffic)
• Transponder (XPDR)
• Weather Radar (WXR) system
• Terrain Awareness and Warning System (TAWS)

This FAQ will cover the WXR and TAWS features of the SURV system. For TCAS, ADS-B Traffic and XPDR systems, see: 

SURV - CONTROLS AND INDICATORS

The SURV system functions can be controlled via

1. SURV Panel on the Pedestal
2. SURV Page on the on the MFD

 
(Click to enlarge image)

1. SURV Panel on the Pedestal

For the purpose of this guide, we are only interested in the WXR SYSTEMS and G/S Mode pushbutton of this panel.

• G/S Mode Pushbutton: Toggles the GPWS (Mode 5) function which monitors for excessive descent below the glide slope. A white OFF light is on when this is switched off.
• WXR SYS1 / 2 Pushbuttons: Toggles the primary SURV system responsible for interpreting Weather Radar Antennae data.

(Click to enlarge image)

2. SURV Page on the MFD

For the purpose of this guide, we are only interested in the WXRand TAWS CONTROLS sections of this page.

To access the SURV page on the MFD,

• Select SURV from the MFD Page Options List at the top left corner of the MFD, OR
• Press the SURV shortcut key on the KCCU

(Click to enlarge image)

CHANGING WXR MODES - MFD SURV CONTROLS PAGE

• WXR/PWS toggle: Toggles the Weather Radar (WXR) and Predictive Windshear System (PWS) between AUTO and OFF. When set to OFF, the respective system display, warnings and audio alerts are disabled.
• TURB toggle: Toggles the Turbulence Detection (TURB) system between AUTO and OFF.
• MODE toggle:  Toggles the radar function between Weather display (WX) and ground mapping (MAP).*
• GAIN toggle: Toggles between AUTO or Manual (MAN) gain control for the WXR.*
• ELEVN/TILT Option List: Toggles between AUTO or Manual (MAN) control of elevation (ELEVN) mode or WXR tilt (TILT)*
  * = Not available in sim currently due to limitations of the sim weather API.

(Click to enlarge image)

CHANGING TAWS MODES - MFD SURV CONTROLS PAGE

• TERR SYS toggle: Toggles the terrain awareness and display (TERR) functions between ON and OFF. When set to OFF, the respective system display, warnings and audio alerts are disabled.
• GPWS toggle: Toggles the Ground Proximity Warning System (GPWS) functions between ON and OFF. 
• G/S MODE toggle: Toggles the GPWS (Mode 5) function which monitors for excessive descent below the glide slope. When set to OFF, the respective system display, warnings and audio alerts are disabled.
• FLAP MODE toggle: Toggles the GPWS (Mode 4B) functions which monitors for appropriate flaps configuration at low altitude in landing phase. When set to OFF, the respective system display, warnings and audio alerts are disabled.

(Click to enlarge image)

RESET ALL SURV MODES TO DEFAULT SETTING - MFD SURV PAGE

When clicked, the DEFAULT SETTINGS button automatically sets all the WXR, TAWS, TCAS and XPDR settings to their default position on both MFDs. A confirmation dialog is necessary to confirm selection. For WXR and TAWS sections, when pressed,

• WXR/PWS system is set to AUTO
• TURB function is set to AUTO
• MODE function is set to WX
• GAIN function is set to AUTO
• ELEVN/TILT Option List is set to AUTO
• TERR SYS mode is set to ON
• GPWS system is set to ON
• G/S MODE system is set to ON
• FLAP MODE system is set to ON

 
(Click to enlarge image)

Your planned SimBrief flightplan may be imported directly into the FMS via the INIT page. This flightplan can also be loaded onto the On-board Information System (OIS) display to view the Operational Flight Plan (OFP). Please follow below steps for setting up and using this feature.

Setting Up SimBrief Import

Verify you have set-up your Simbrief Pilot ID (numbers only) on the FLT OPS MENU > OPTIONS > 3RD PARTY settings page. 
Click on the SIMBRIEF USER ID text field and then use the On-Screen Keyboard. 

Quote

Note: Your Simbrief Pilot ID is found on the 'Account Settings' page on the Simbrief.com website.

(Click to enlarge image)

Importing into OIS

You can import your Simbrief Flight information on the OIS through the FLT OPS MENU > FLT OPS STS page. 
Click on the SIMBRIEF IMPORT button on the top-right corner to populate the fields below and add your Operational Flight Plan (OFP) to the OIS.

Click to enlarge image)

Importing Route into FMS

You can import your route on the FMS through the INIT  page via the CPNY F-PLN REQUEST button.

(Click to enlarge image)

After a few seconds, the button status will update to RECEIVED CPNY F-PLN. Click this and select INSERT * from the drop-down to complete the uplink. The fields on this page will auto-fill and you will see a white AOC RTE UPLINK message at the bottom confirming successful import.

(Click to enlarge image)

(Click to enlarge image)

Lastly, you may also request a wind up-link from Simbrief by clicking on the CPNY WIND REQUEST * button as shown in above screenshot.

Quote

Note: Your winds aloft data from the OFP will import automatically if you have done a CPNY-FPLN REQUEST from above.

Quote

Note: This will reset key files so you must re-do the following on next launch

• Throttle Calibration
• Connect to Navigraph
• Download Navigraph Data via the OIS

Click the above items to re-direct to the FAQ for each.

1.  Close the simulator if it is running.
2. Navigate to your your FS20 WASM Folder:

   Steam:

   Quote

   %APPDATA%\Microsoft Flight Simulator\Packages\inibuilds-aircraft-a350

   MS Store:

   Quote

   %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\Packages\inibuilds-aircraft-a350

3. Delete all the contents of this folder. This folder and its contents will be re-generated next time you load into a flight with the aircraft.
   

Quote

Note: The names of these files, as well as the number of them may vary per installation. The above image is shown for illustrative purposes only.

SYSTEM OVERVIEW

The Brake To Vacate (BTV) function optimizes the autobrake deceleration on landing in order to reach the selected runway exit point/ manually entered landing distance. The system takes into account the selected runway condition/braking action in its calculations.

Once armed, the system works autonomously to delay braking in order to reduce brake wear, optimize the runway occupancy time (ROT) and improve passenger comfort.

SETTING UP BTV

In order for BTV to function, it needs information such as your stopping target stopping distance and runway condition. This information can be provided by 2 ways:

1. via Exit Selection on the ANF (airport moving map on ND), OR
2. via Manual Distance Entry

Instructions on how to set up BTV using each method is shown below.

1. Exit Selection on the ANF [*Navigraph Only]

Quote

Note: This feature requires an active Navigraph Unlimited subscription. A valid airport map must be loaded on the ANF, which can only be done after successfully connecting your Navigraph account on the OIS Third Party Settings page.

For more information, see the below CONNECT TO NAVIGRAPH section of the ANF FAQ post:

Step 1: Choose Landing Runway on FMS

• Press the F-PLN shortcut key to go to the FMS F-PLN page
• At the bottom left corner, select your DEST airport and select the Landing RWY
  - you can also select your APPR and STAR on this page, however the BTV system only requires the runway at minimum to function
• Choose TMPY F-PLN and then INSERT TMPY to confirm the selection.

(Click to enlarge image)

Step 2: Set ANF to your DEST airport

Whilst on the ANF display, the currently displayed airport map can be changed via the ARPT SEL function page as follows:

• Change to PLAN mode via the ND Mode Selector Knob
• Change the range to ZOOM via the ND Range Selector knob
• Move the KCCU cursor to the ND screen by
  - Clicking anywhere on the ND screen, OR
  - Clicking the ND key on the KCCU
• Click the double-arrow Additional Function Button at the bottom-right corner of the ND
• Select the (A) ARPT SEL tab
• Choose from the (B) FMS AIRPORTS list to display your Destination
• Click the (D) DISPLAY AIRPORT button to make it the active displayed airport.

(Click to enlarge image)

Quote

Note: You can only view other airports in the ND PLAN mode. The airport navigation display is locked to the aircraft position in NAV or ARC modes, so you must switch to PLAN mode in order to center the map on the selected airport.

Quote

Note: Your selected airport ICAO/IATA/Info will appear in

• Yellow when it is the not active airport displayed on the ND
• Green when it is the active airport displayed on the ND

 

Step 3: Choose the Braking Action / Runway Condition

• Pull the RWY COND/BRAKING ACTION KNOB-SELECTOR to bring up the RWY CONDITION / BRAKING ACTION matrix on the SD
  (this knob is located just above the landing gear lever)
• Rotate the selector clockwise (or anti-clockwise) to choose between the various RWY CONDITION / BRAKING ACTION options
• After a few seconds, the selected option is validated automatically
• Push the knob selector to hide the RWY CONDITION / BRAKING ACTION matrix on the SD

 
(Click to enlarge image)

Step 4: Choose target Exit via ANF

• Click-and-drag to center the map on your desired exit
• Click the interactable taxiway icon on the runway (interactable elements have a blue border around them)
• Select SET BTV EXIT from the options list
  (You can also UNSET BTV EXIT from the same options list to remove your selection)

Once a target Exit is chosen,

• A blue line will appear along the landing runway to the selected exit showing the chosen BTV target exit, AND
• On the top left corner of the ND, you will see the chosen RWY (and its LDA), BRAKING CONDITION and EXIT as well as the corresponding Runway Occupancy Time (ROT)(in seconds) and TURNAROUND time (in minutes) for MAX REV or REV IDLE usage respectively.

(Click to enlarge image)

Quote

Note: You must choose an exit beyond the DRY or WET ROW Stop Bar depending on your runway condition/braking action. These stop bars move as you change the runway condition/braking action.

If you chose an exit that is before the DRY or WET ROW line, the BTV will not be able to stop to reach the exit in time.

2. Manual Distance Entry

Step 1: Choose Landing Runway on FMS

• Press the F-PLN shortcut key to go to the FMS F-PLN page
• At the bottom left corner, select your DEST airport and select the Landing RWY
  - you can also select your APPR and STAR on this page, however the BTV system only requires the runway at minimum to function
• Choose TMPY F-PLN and then INSERT TMPY to confirm the selection.

(Click to enlarge image)

Step 2: Open the LANDING function page

• Change to PLAN mode via the ND Mode Selector Knob
• Change the range to ZOOM via the ND Range Selector knob
• Move the KCCU cursor to the ND screen by
  - Clicking anywhere on the ND screen, OR
  - Clicking the ND key on the KCCU
• Click the double-arrow Additional Function Button at the bottom-right corner of the ND
• Select the (A) LANDING tab
• Enter the BTV Exit (B) DISTANCE from threshold for your target
  (This information can normally be obtained from the Airport Ground / Information Charts)

Step 3: Choose the Braking Action / Runway Condition

• Choose the (C) LDG PERF CODE that is most suitable to the reported landing runway condition / braking action.

You can bring up the RWY CONDITION / BRAKING ACTION matrix for reference by,

• Pull the RWY COND/BRAKING ACTION KNOB-SELECTOR to show the matrix on the SD
  (this knob is located just above the landing gear lever)
• Rotate the selector clockwise (or anti-clockwise) to choose between the various RWY CONDITION / BRAKING ACTION options
• Push the knob selector to hide the matrix on the SD

 
(Click to enlarge image)

Quote

Note: This method of arming BTV is useful users without Navigraph subcription, or if your landing airport/runway is NOT in the ANF database. The effectiveness of the BTV function in this instance is solely dependent on the accuracy of the distance data you feed into it.

BTV ARMING &  ENGAGEMENT

The BTV autobrake mode arms when the following conditions are met:

• A BTV exit is selected OR BTV distance is entered manually, AND
• A/BRK pushbutton is pressed

Once successfully armed,

• The A/BRK pushbutton will be lit up green
• The PFD FMA will show BTV in blue

 
(Click to enlarge image)

The BTV autobrake mode engages on landing if any one of the conditions is met:

• immediately after ground spoilers extension if the NLG is on ground; OR
• 5s after ground spoilers extension if NLG is not on ground

(Click to enlarge image)

BTV DISARMING & DISENGAGEMENT

The autobrake disarms if any one of the conditions is met:

• The A/BRK pushbutton is pressed again, OR
• The selected landing runway on the ANF is modified, OR
• The BTV exit is deselected, OR
• The FMS runway is changed to a runway that is different from the selected landing runway, OR
• A go-around is performed below 600 ft.
  The reversion occurs during the go-around, when the aircraft climbs above 600 ft. The computation is based on the minimum between the radio altitude, and the aircraft height above the runway threshold.
   

The autobrake disengages if any one of the conditions is met:

• The aircraft ground speed reaches the BTV disconnection speed (approx. 10 kt), OR
• The flight crew uses the brake pedals, OR
• The flight crew presses the A/THR instinctive disconnect pushbutton, OR
• The ground spoilers retract or disarm.
   

When autobrake disengages the the following happens:

• A single chime audio indicator sounds
• The MASTER CAUT lights comes on
• The AUTO BRK OFF memo appears on the PFD and WD.
   

Quote

Note: Reversion to BRK MED if the BTV function becomes inoperative. When this happens you will hear a triple click audio alert and BRK MED appear on FMA with a white box for 10s.

The A350 Airliner comes with a variety of quality of life features such as Pause at Top of Descent (TOD), Auto Step-Climbs and Time Compression to make long haul / away-from-keyboard (AFK) flying more accessible for simmers.

SETUP - OIS SIMULATION SETTINGS

All of these features can be set up via the On-board Information System (OIS) simulation options page, which is accessed from FLT OPS MENU > OPTIONS > SIMULATION. 

(Click to enlarge image)

AFK MODE

The AFK Mode is a conservative setting to be used with Time Compression when you are leaving your simulator unattended. Setting this to:

• YES: Pauses your simulator in case of autopilot disconnection during active Time Compression.
• NO: Will not pause your sim in case of autopilot disconnection during active Time Compression.

PAUSE AT TOD

The  Pause at Top of Descent (TOD) pauses your simulator at a set distance before the FMS computed TOD point. 

To enable the feature,

• PAUSE AT T.O.D: Select YES to arm this function
• PAUSE TOD DIST (nm): Enter the desired value for where you want the pause to engage (Default 30 nm, Max 100 nm)

Quote

Note: This option is saved between sessions and active for all variants. 

To unpause the simulator, 

• Click the RESUME FLIGHT button on the OIS notification

(Click to enlarge image)

AUTO STEP CLIMB

The Auto Step Climb feature automatically climbs your aircraft at the pre-defined steps that you have setup on the MFD FMS.

The Auto Import Step Climb feature automatically uplinks the planned steps from your Simbrief OFP for validation against FMS calculations. The step alts which are deemed valid are then input automatically on the F-PLN / VERT REV / STEP ALTS page. 

(Click to enlarge image)

TIME COMPRESSION

The Time Compression feature allows you to shorten your flight time by increasing the simulation rate by upto 4x. This is useful for completing longer flights in a shorter time. 

The TIME COMPRESSION option when set to,

• AUTO: Automatically manages the simulation rate (up to the MAX COMPRESSION rate set)
• OFF: Resets the simulation rate to 1x. 
   

Quote

Note: This feature can adjust the simulation rate, but it cannot completely disable on its own. As such should manually be turned OFF from the OIS when not required.

It is recommended to monitor your flight whilst Time Compression is in use as the autopilot can still disconnect due to excessive turbulence or abrupt weather changes for example. 

The MAX COMPRESSION option when set to,

• UP TO 2X: Limits the simulation rate to a maximum of 2x.
• UP TO 4X: Limits the simulation rate to a maximum of 4x.
   

Quote

Note: The actual simulation rate achieved will depend on factors such as your system hardware and present aircraft position. All systems and their calculations are run at the set simulation rate, leading to an increased demand of system resources. 

If the current FPS falls below the minimum required threshold, the simulation rate is dynamically reduced to improve stability. When more system resources become available, the simulation rate will again dynamically increase up to the set MAX COMPRESSION rate.

 The active simulation rate is shown via a green notification at the top of the OIS. 

Quote

Note: While the simulation rate changes, the simulator time still remains synced to real UTC time and will not advance at a higher rate currently (sim limitation)

DIR TO FUNCTION - OVERVIEW

On the A350, the Direct To (DIR TO) waypoint function can be accessed via

• Multi-Function Display (MFD) FMS DIR TO page, OR
• Navigation Display (ND) DIR TO page

You may create a direct flight leg from the aircraft's present position (P.POS) to

• Any FMS Flight Plan waypoint, or
• Any FMS Navigation database waypoint, airport or navaid, or
• Any FMS Pilot stored Latitude/Longitude (LL), Place/Bearing/Distance (PBD), Place-Bearing/Place-Bearing (PB) waypoint

There are four options for creating the direct flight leg

• DIR TO (DIRECT), or
• DIR TO with abeam waypoints (DIRECT WITH ABEAM), or
• DIR TO with inbound course (CRS IN), or
• DIR TO with outbound course (CRS OUT), or

DIR TO VIA ND
A. Waypoint Selection Method

1. Move the KCCU cursor to the ND by using the KCCU ND shortcut key or clicking anywhere on the ND
2. Click on target Waypoint / Airport / Navaid to bring up the Revisions List 
3. Select the FROM P.POS DIR TO * option
4. Choose the desired flight leg option (DIRECT / DIRECT WITH ABEAM / CRS IN / CRS OUT)
5. Select INSERT DIR TO*
   (or ERASE DIR TO* to cancel selection)

(Click to enlarge image)

B. Aircraft Icon Method

1. Move the KCCU cursor to the ND by using the KCCU ND shortcut key or clicking anywhere on the ND
2. Click on user aircraft icon and select the DIR TO option
3. Click on target Waypoint / Airport / Navaid
   (or anywhere on the screen to create a pilot LL waypoint target)
4. Choose the desired flight leg option (DIRECT / DIRECT WITH ABEAM / CRS IN / CRS OUT)
5. Select INSERT DIR TO* 
   (or ERASE DIR TO* to cancel selection)

OR

(Click to enlarge image)

DIR TO VIA MFD FMS

A. MFD Direct To Page Method 

1. Move the KCCU cursor to the MFD by using the KCCU MFD shortcut key or clicking anywhere on the MFD
2. Press the KCCU DIR shortcut key
3. Click the drop-down button and choose the target F-PLN waypoint from the DIR TO list
   OR
   Click the DIR TO waypoint field and use the KCCU to type in the target
   - Navigation database waypoint, airport or navaid, or
   - FMS Pilot stored LL, PBD, PB waypoint
4. Choose the desired flight leg option (DIRECT / DIRECT WITH ABEAM / CRS IN / CRS OUT)
5. Select INSERT DIR TO* 
   (or ERASE DIR TO* to cancel selection)

(Click to enlarge image)

B. MFD F-PLN Page Method 

1. Move the KCCU cursor to the MFD by using the KCCU MFD shortcut key or clicking anywhere on the MFD
2. Press the KCCU F-PLN shortcut key
3. Click the target F-PLN waypoint from the list
4. Click the FROM P.POS DIR TO option from the waypoint revision list
5. Choose the desired flight leg option (DIRECT / DIRECT WITH ABEAM / CRS IN / CRS OUT)
6. Select INSERT DIR TO* 
   (or ERASE DIR TO* to cancel selection)

You can create and store Latitude/Longitude (LL), Place/Bearing/Distance (PBD), Place-Bearing/Place-Bearing (PB) waypoints on the FMS as FMS Pilot Stored Waypoints via the following methods

• MFD DATA/WAYPOINT Page
• DIR TO Page (LL / PBD waypoints only)
• ND DIR TO Aircraft Icon Method (LL waypoints only)

Entry Formats

LAT: where DD= Degrees (0 to 90), MM.M= Minutes (0 to 59.9) and X= Hemisphere (N or S)

• XDD°MM.M, or
• DD°MM.MX or
• XDDMM.M 

LON: where DDD= Degrees (0 to 180), MM.M= Minutes (0 to 59.9) and Y= East/West reference (E or W)

• YDDD°MM.M or
• DDD°MM.MY or
• YDDDMM.M

VIA MFD DATA/WAYPOINT PAGE

To access the MFD DATA/WAYPOINT page click DATA from the MFD pages menu and then select WAYPOINT from the drop-down list. The DATABASE WPTS tab opens by default.

(Click to enlarge image)

To create a new LL, PBD or PB waypoint,

1. Click the PILOT STORED WPTS tab
2. Click the NEW WPT button 
3. Enter the target WPT IDENT
4. Enter one of the Waypoint Position Entry Fields 
   -  Latitude/Longitude (LL), or
   - Place/Bearing/Distance (PBD),or
   - Place-Bearing/Place-Bearing (PB)
5. Click the STORE WPT button

(Click to enlarge image)

On the PILOT STORED WPTS tab you can see your newly created WPT and its relevant information. Here you may also

• DELETE STORED WPT: To delete the currently displayed pilot stored waypoint
• DELETE ALL STORED WPTS: To delete all listed pilot stored waypoints

(Click to enlarge image)

VIA ND DIR TO - AIRCRAFT ICON METHOD (LL WAYPOINTS ONLY)

To create a Pilot stored LL waypoint, automatically at the co-ordinates of the KCCU cursor,

1. Move the KCCU cursor to the ND by using the KCCU ND shortcut key or clicking anywhere on the ND
2. Click on user aircraft icon and select the DIR TO option
3. Click anywhere on the screen to create a pilot LL waypoint target

This feature is useful for creating custom waypoints around a particular obstacle or for temporary weather avoidance.

(Click to enlarge image)

The Nose Wheel Steering is usually conducted using the tiller located on the side console. The tiller is bound to the 'NOSE WHEEL STEERING AXIS'.

For simulation purposes, this can also be linked to your rudder axis for ease of use. This is done on the On-board Information System (OIS) display aircraft settings page which can be reached via FLT OPS MENU > OPTIONS > AIRCRAFT. 

OIS AIRCRAFT OPTIONS

• Set the RUDDER CTRL TILLER option to YES to couple the Rudder Axis  to the Nose Wheel Steering Axis.
• (Optional) Set the AUTO TILLER DISCO option to YES to automatically de-couple the Rudder Axis  to the Nose Wheel Steering Axis when N1% > 70% for better directional control on the runway.

(Click to enlarge image)

(Click to enlarge image)