Filesystem

Installation Folder (%BTI_HOME%)

To run BushTripInjector, you must unpack the “BushTripInjector” folder included in the package to a folder or drive where your user has read, write, create and delete permissions. It is recommended to run BushTripInjector without administrative rights.

This folder is referred to as %BTI_HOME% in the further documentation.

Inside %BTI_HOME% are some folders from the package and some other files and folders that are created at runtime:

• BushTripInjector.ini
  This file is only used and created, when you are not using BTI file format and will be deprecated in a future version.
  The INI file contains the same savings and settings that are needed if you are not using the new BTI file format.
• .config
  This folder contains files to configure the map views available in the BushTripInjector WorldMap. It also contains a file for configuring how simulation variables are mapped from FSX/P3D to MSFS.
• Lib
  The lib folder contains several binary libraries (DLL – dynamic link library) used by BushTripInjector. These libraries are part of the package and should not be moved, renamed or deleted.
• BushTripInjector_SAVES
  If you do not use the BTI file format and open LittleNavmap files directly, BushTripInjector needs to store some information about your mission. These are stored in this folder.
  Do not delete any files from this folder. You will otherwise lose the functionality of your mission.
  
  Following files are located here:

%missionname%-BTI-AssistancePresets.xml	This file keeps the AssistancePreset setting of your mission
%missionname%-BTIFLT.xml	Here are some additional information of your flightplan are stored, i.e. mandatory waypoints, user airports
%missionname%-BTI-Landmarks.xml	You defined landmarks and ingame markers are saved into this file
%missionname%-BTILNG.xml	The BTILNG.xml keeps the translated text of your mission including some references to assign them back.
%missionname%-BTI-TriggerAction.xml	Each definition from Event&Triggers Editor is located in this file.
%missionname%-BTITTS.xml	The defined text-to-speech of your mission is stored here

Projects / PackageSources (%PROJECT_ROOT%)

This folder holds all the relevant files for your mission in MSFS source format. The files are created by BushTripInjector and used by the MSFS compiler to build your mission. Each mission has its own subfolder (%MISSION_FOLDER%) which contains several subfolders again.

This folder is called %PROJECT_ROOT% in further documentation.

Do not delete files or folders of the %PROJECT_ROOT% if you are not sure about the consequences. You will lose the functionality of your mission.

You can change the folder location on the Options Tab.

Mission Folder

Inside the %PROJECT_ROOT% you will find the source folders of your missions for the MSFS compiler. Each of these folders has the name of your mission and contains the following files and folders. Do not edit or delete any of the files, except in the folder for additional files.

• Project Definition File
  This file is required and contains a link to the package definitions for your mission. There are also some definitions for the MSFS compiler. This is the first file that is read by the compiler. The name is “%projectname%project.xml”, i.e. “friendlyflyer-hawaii-missionproject.xml”.
• AdditionalFiles
  In this folder, BTI saves external files added to your mission, such as sound files, images, PDF files, or other files.

Subfolder	Description
Sounds	All of the sounds, you ever created or assigned to any action. If you remove, rename or add any file from this folder, it may have effect to your mission.
Documents	Flight books created by BushTripInjector. (BTI Versions >= 1.2.4)

• Community
  This is a folder created by BushTripInjector to publish missions to the MSFS Marketplace. It contains a zip file named export.zip with your compiled mission.
  Obsolete since Marketplace 2.0
• PackageDefinitions
  This folder is required by the compiler. It contains the asset definitions of your entire project. The files in this folder tell the MSFS compiler how to compile the various sources of your packages.
• Packages
  The Packages folder is maintained by MSFS. This folder contains the packages that MSFS has compiled. Here you can find the packages that you can copy to the community folder.
  It is present here, when you are using the “Compile to MissionPath” option from Options. If you untick this flag, this folder appears in %BTI_HOME%.
  You can delete this folder if no generation or compilation of BTI is currently running. This folder will be recreated by MSFS during the next compilation run.
• PackagesMetadata
  The PackagesMetadata folder contains the meta information for publishing a package to MSFS MarketPlace. It is present here, when you are using the “Compile to MissionPath” option from Options.
• PackageSources
  This folder contains all the assets of your project. These are the mission itself in a subfolder with your project name and the scenery data like airports, landmarks, etc.
  The sub folders are referenced by the definitions in PackageDefinitions. Do not edit these files if you are not sure what exactly you are doing. All of these files will be overwritten by the next generation, except for the images.

Logs-Folder

BushTripInjector writes log files to analyze issues when it has unexpected behavior on the client side.

You can change the folder location on the Options Tab.

Backup-Folder

BushTripInjector regularly creates multiple backups of settings, your flight plans and your mission files.

You can change the folder location on the Options Tab.

Database-Folder

Within the database folder, BushTripInjector is searching for your main, parking and navigation database and creates the model library database, the usage database, the database for the glossaries and some more..

The main, parking and navigation database can be downloaded as separate download from here.

The model library database can be created when searching for a model in Events & Triggers Editor.

The usage database is also created in this folder. If you delete the files in this folder, or just the BTI.USAGELIST.db file, BTI will not be able to detect missing airports, runways, etc. from your older missions.

You can change the folder location on the Options Tab.

Misc-Folder

At runtime, BushTripInjector creates various files when you record audio, resample audio files, view or import spb files, etc. These files are stored in this folder so you can reuse them later or in other missions. Within this folder, the following subfolders may appear.

• Recordings
  This folder contains the sound files you created with BushTripInjector’s internal audio recorder or TTS generator.
• SPBXML-Files
  When you decompile SPB files from FSX, Prepare3D or MSFS, the output is stored here. You can open these files with any browser or a xml viewer or editor of your choice.
• UserPoints
  In this folder BTI is searching for the UserPoints in LittleNavMap Format. You can use them for your mission from the landmarks sheet.

You can change the folder location on the Options Tab.

MSFS Output Path

When you compile your mission with the SDK or the simulator, MSFS creates 2 directories. A temporary folder and the folder with your compiled mission. Depending on the setting of “Compile to MissionPath” the files are located in %MISSIONPATH% or in a separate folder which can be defined under Options.

• _PackageInt
  The _PackageInt folder is managed by MSFS. This folder contains some intermediate packages created by the simulator’s compiler. It is present if you do not use the “Compile to missionpath” option in the Options. If you check this flag, this folder will appear in each of your mission folders.
  You can delete this folder if no generation or compilation of BTI is currently running. This folder will be recreated by MSFS during the next compilation run.
• Packages
  The Packages folder is managed by MSFS. This folder contains the packages that MSFS has compiled. Here you can find the packages that you can copy to the community folder.
  It is present if you do not use the “Compile to missionpath” option in the Options. If you check this flag, this folder will appear in each of your mission folders.
  You can delete this folder if no generation or compilation of BTI is currently running. This folder will be recreated by MSFS during the next compilation run.
• PackagesMetadata
  The PackagesMetadata folder contains the Meta information to publish a package on MSFS MarketPlace

You can change the folder location on the Options Tab.

Settings Folder

BushTripInjector store your settings, recent files, license information and some cache files in your LocalAppDataFolder.

To view the content of this folder, just open the following path with Windows Explorer: %LocalAppData%\BushTripInjector.

• .mapcache
  The mapcache folder is created at runtime and contains the cached tiles downloaded from the various map tile providers configured in the .config folder.
  It is safe to delete this folder when BTI is not running.

• EBWebView
  This is the caching folder for the WebView2 component used for displaying Html-Pages inside of BTI.

Default locations

When upgrading, BushTripInjector uses the folders of the previous version. The following paths are used for new installation by default.

Id	Folder
PROJECT_ROOT	%Documents%\BushTripInjector\Projects
LOG	%LocalAppData%\BushTripInjector\Logs
BACKUP	%Documents%\BushTripInjector\Backup
DATABASE	%Documents%\BushTripInjector\Database
MISC	%Documents%\BushTripInjector\Misc
MSFS OUTPUT	%Documents%\BushTripInjector\MSFS
PUBLISH	%Documents%\BushTripInjector\Publish