richboy2307

Navigraph is required for ANF yes. Mentioned on the store page, streams and differences chart we put out. Once you have ANF, you can use it for BTV via exit selection. If you don't have a Navigraph subscription, you can still use BTV via manual distance entry. Guide is here, see 2. Manual Distance Entry section.: You may need to manually load the airport if you're too far from it. Sometimes going out of ZOOM mode and back can help re-cycle it as well. See the ARPT SEL FUNCTION- CHANGING DISPLAYED AIRPORT MAP section of the guide below: Thanks

Hi @Delta_A350 You need to choose the correct winglet type from the OIS Equipment settings. Thanks!

What is WASM? 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.

What is WASM?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 also improves security of the sim and portability of projects across PC/Xbox/PS5. 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 & crash LVARs Report the WASM error message & crash LVARs with reproduction steps using the guide below. Verify WASM Crash in SimStep 1. Enable Developer Mode FS24 Settings > General > Advanced Options FS20 Options > General Options > Developers 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. Step 5. Check the newly exposed INI_CRASH LVARs via the Behaviours Menu. Also take a screenshot of this for making a report. Accessing Behaviours Menu FS24 Via the DevMode toolbar at the top, select Tools > Behaviours and navigate to the Variables tab. Uncheck "Only Show Variables get/set....". Type 'INI_CRASH' in the search box and expand their name to display the values. FS20 Via the DevMode toolbar at the top, select Tools > Behaviours and navigate to the Variables tab. Type 'INI_CRASH' in the search box and expand their name to display the values. Report WASM Crash on ForumStep 6. Paste the WASM Error message, screenshot of the Console and INI_CRASH LVARs obtained in Step 4 and Step 5 above into a forum post/discord message/ support ticket WASM Crash Report. Step 7. Take note of what you pressed or things you did, just before you noticed this crash happen. Step 8. Verify if you are able to repeat the crash by following those same steps. Step 9. 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 10. 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 Autosave File, include the latest ".bin" autosave file prior to your crash to help us reload into same scenario. Autosave Folder Paths These types of WASM crashes are heavily dependent on the actions taken just before the issue occurs. Detailed reports of the exact steps leading up to the crash are extremely helpful, as if we’re able to reproduce the issue internally using the same sequence, our team can investigate, debug, and resolve it much more effectively.

The iniBuilds A350 Airliner simulates the MFD Controlled Backup EFIS and AFS Control panels which can be used in case of inoperational buttons/equipment. 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)

The iniBuilds A350 Airliner simulates the MFD Controlled Backup EFIS and AFS Control panels which can be used in case of inoperational buttons/equipment. 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)

Changing Weight Measurement Units (LBS / KGS) 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)

Changing Weight Measurement Units (LBS / KGS) 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)

The iniBuilds A350 Airliner simulates the realistic boot time for the On-board Information System (OIS) by default. During the boot-up the computer that powers the OIS is turning on and running through its system checks. 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.

The iniBuilds A350 Airliner simulates the realistic boot time for the On-board Information System (OIS) by default. During the boot-up the computer that powers the OIS is turning on and running through its system checks. 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.

The iniBuilds A350 Airliner for MSFS 2020 and 2024 uses Web-Assembly Module (WASM) to run its code in the simulator environment. 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. 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:

The iniBuilds A350 Airliner for MSFS 2020 and 2024 uses Web-Assembly Module (WASM) to run its code in the simulator environment. 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. 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:

Hi For those of you experiencing these issues, first of all ensure all the assistances are disabled per below: Also ensure you do not have any conflicting keybinds (keyboard or other controllers) related to RUDDER, AILERON or PITCH TRIM set in your control settings. Thanks!

Note: On the iniBuilds A350 Airliner (v1.0.0), please make sure that if you change SID/STAR/APP or RUNWAY that you have your ICAO of your airport shown on the F-PLN page with the expected runway. 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.

Note: On the iniBuilds A350 Airliner (v1.0.0), please make sure that if you change SID/STAR/APP or RUNWAY that you have your ICAO of your airport shown on the F-PLN page with the expected runway. 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.

If your aircraft is not following the flight path correctly, please check your MSFS Assistance settings and ensure that the 4 options highlighted below in red below are switched to OFF.

If your aircraft is not following the flight path correctly, please check your MSFS Assistance settings and ensure that the options highlighted below in red below are set to OFF.

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 > Controls > Select your controller > Hardware settings and set it up as shown below.

Attached below is the Aircraft Manual for the iniBuilds A350 Airliner for your reference. 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. 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.

The iniBuilds A350 Airliner for MSFS 2024 has optional interior and exterior components that can be predefined with the livery. Below is a brief set of instructions on how to do this via the A350 Livery Configuration Generator. Instructions Add the following to the package definitions xml: <AssetGroup Name="LiveryConfig"> <Type Version="0">Copy</Type> <Flags> <FSXCompatibility>false</FSXCompatibility> </Flags> <AssetDir>PackageSources\Config</AssetDir> <OutputDir>Config\</OutputDir> </AssetGroup> In the PackageSources folder add the following folder structure: \\PackageSources\\Config\\MyAirline (where MyAirline = the airline livery you are creating) Create the required config file based on the livery you are creating using the A350 Livery Configuration Generator available for download here: livery_configurator.html To add an element select the desired option. There are some exceptions such as winglets (only configurable on -900) and the language pack, which is a drop down list. Click the Copy button and paste the result into a LiveryConfig.cfg file which you can create at this location: \\PackageSources\\Config\\MyAirline (where MyAirline = the folder name you created in step 2) Add the following to your livery.cfg file: [Panel_DynamicParameters] param.0 = "airline,MyAirline" (where MyAirline = the folder name you created in step 2) Export the livery as normal.

SYSTEM OVERVIEW On the iniBuilds A350 Airliner for MSFS 2024 you can use the Flight Attendant Panel (FAP) to manage and monitor: Cabin Lighting Avionics Bay Lighting Cargo Bay Lighting Cabin Temperature Cabin Doors Water and Waste Tanks Capacity / Status There are a total of 2 touchscreen FAPs installed on the aircraft located at FWD galley near door L1 AFT galley near door L4 (Click here to enlarge image) CABIN STATUS The Cabin Status page gives you a quick overview of the Lights, Temp and Door status of the aircraft. Buttons & Controls Cabin Ready: Press to send the CABIN READY ECAM alert to the cockpit. Press again to reset. Lights Graphic: Press to access the Lights page. Temp Graphic: Press to access the Temperature page. Door/Slides Graphic: Press to access the Doors page. Waster/Waste Graphic: Press to access the Water/Waste page. (Click here to enlarge image) LIGHTS The Lights Status page allows you to quickly toggle light modes for all or individual zones. Buttons & Controls Night Mode: Sets CABIN to the LOW DIM state Main On: Sets CABIN to the BRIGHT state Zones: Allows you to set the lighting of the Cabin, Avionics Bay or Cargo Bay zone individually. The current status of that zone is shown in text below it (Bright , Medium Dim, Low Dim) Local: Allows you to set the desired status of the selected zone (highlighted in green) To manually adjust the brightness of a selected zone Click on the desired zone button (Cabin / Avionics Bay / Cargo Bay) The active zone will be highlighted in green Click on the desired status for the selected zone in the Local section (Bright / Medium Dim / Low Dim) The current status of that zone is shown in text below it. (Click here to enlarge image) TEMPERATURE The Temperature Status page allows you to manually adjust the target temperature for the cabin. Buttons & Controls Zones: Allows you to view the temperature of the Zones A, B or C individually. The current temperature of that zone is shown in text next to it. Local: Allows you to set the desired temperature target for all the zones via the +/- buttons. To manually adjust the temperature of a selected zone Click on the + or - button to set the target temperature for the selected zone in the Local section a. The current target value is shown by the number and graphic scale in the Local section. b. The actual current temperature of each zone is shown on the number in the Zones section. (Click here to enlarge image) DOORS/SLIDES The Doors Status page allows you to open/close doors and monitor their current status. Buttons & Controls Door 1 Left: Click on the door icon to open/close the door Door 2 Left: Click on the door icon to open/close the door Door 3 Left: Click on the door icon to open/close the door Door 4 Left: Click on the door icon to open/close the door Door 1 Right: Click on the door icon to open/close the door Door 2 Right: Click on the door icon to open/close the door Door 3 Right: Click on the door icon to open/close the door Door 4 Right: Click on the door icon to open/close the door The legend on the left shows what status is reflected by each of the colours. (Click here to enlarge image) WATER/WASTE The Water and Waste Status page allows you to manage and monitor the status of the respective tanks. Buttons & Controls Refill Water: Sets the Water tank to 100% capacity Empty Waste: Sets the Waste tank to 0% capacity The Waste tank fills up, whilst the Water tank drains throughout the duration of your flight. The Water and Waste Quantity graphic reflects the current % value of the tanks. (Click here to enlarge image)

In MSFS 2024, 'Preflight Walkaround' is the first phase of a flight when you start 'cold and dark' from a parking spot / ramp. Your pilot character spawns close to the currently selected aircraft, and it is possible to walk around and interact with various doors, panels and hatches. Exiting Walkaround You may exit the pre-flight walkaround at any time by clicking on the door handle or using the user-defined key bind for 'TAKE CONTROL OF CHARACTER' (Default: Shift+C). Control Settings - Keybind for Entering/Exiting 'Preflight' mode Walkaround Operables On the iniBuilds A350 Airliner for MSFS 2024 there are over 15 doors, hatches or panels that open conditionally or via interactions in this mode: HP Air Service Panel LP Air Upper & Lower Service Panel Waste Water Service Panel Potable Water Panel Refuel Panel and Mode selector Refuel Coupling (during refuel) Yellow Hydraulics Panel Green Hydraulics Panel External Power Panel & Cart (when EXT PWR 1 in use) Main Gear Maintenance Panel & Doors - Left and Right Nose Gear Maintenance Handle (-900) / Panel (-1000) Forward, Aft and Bulk Cargo Door Control Panels & Doors (via OIS) Avionics Bay Door Engine Cowlings with engine oil indication Left/Right Nose Wheel Steering and Interphone panel

You can view a list of the key LVARs on the iniBuilds A350 Airliner via this sheet here or via the attached PDF for reference. What are LVARs? LVARs are "Local Variables" which are used to read/set various switches or system behaviours in the aircraft. How to use LVARs? You can bind the listed LVARs to various hardware switches, axis or buttons to control their virtual counterparts on the iniBuilds A350 Airliner externally using 3rd Party software (e.g. Mobiflight, Axis and Ohs, SPAD.Next or FSUIPC etc.) A350 LVARs-FEB2025.pdf

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 Download the latest version of iniManager from https://inibuilds.com/pages/inimanager-v2 Log in using your iniBuilds Store account. 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. Done! You may now download your desired products and liveries. Existing Users Ensure you have the latest version of iniManager from https://inibuilds.com/pages/inimanager-v2 Go to the iniManager 'Settings' page by clicking on your name on the top left corner. 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. Done! You may now download your desired products and liveries. IniManager - Liveries Management Accessing Liveries Open the iniManager Select the 'Liveries' from the sidebar Select the 'A350 Airliner FS24' or A350 Airliner FS20' Find your desired livery from the list. You may use the 'Filters' or 'Search Liveries' section at the top-right corner. Installing Liveries Click the 'Install' button on the desired livery. Read the disclaimer and press 'I Understand' button. Wait for the download to complete. You can see the status of your download via the Active Downloads icon on the top right corner. Done! You may now close the iniManager. Uninstalling / Updating Liveries Click the 'Uninstall' or 'Update' button on the desired livery. Done! You may now close the iniManager.