With BushTripInjector Version 1.2.3, the support for localized sound files were implemented.
This means, depending on the language settings of the simulator of your clients, different language sound files were played.
All of the sound files are located in a Sound folder your Mission Folder in the AdditionalFiles folder. For each language, a folder needs to be created by you with the language code. The folder for your base language is maintained by BushTripInjector and it is created when you are adding a sound file for the first time.
All MSFS languages should be supported, the BTI-team just tested the bold ones and can confirm they are working. Feel free to report any of the other languages:
|en-US||English (United States)|
|es-ES||español (España, alfabetización internacional)|
|nb-NO||norsk bokmål (Norge)|
When BushTripInjector detects, you are using a sound file (i.e. FlyThroughTheValley.wav), it looks for a sound file in AdditionalFiles folder of the other languages in following order:
BushTripInjector will copy, rename and reference the files for you, as requested by MSFS-SDK. Of course, all names are not case sensitive.
BTI and MSFS has implemented also a fallback. If a localized sound files is not present, the “en-US”-file is used. If this is not present, the corresponding Text of your text-to-speech or InstructorDialogAction is used. For this, this is always translated independent of the setting on BaseTab. Of course, only if a sound file is attach to this object.
Because of this fallback situation and when you are using another base language then “en-US” and you do not have an “en-US” sound file, the sound file from you base language will be used as “en-US”, too.