Difference between revisions of "TIE Fighter Custom Audio"
Lockesetzer (talk | contribs) |
Lockesetzer (talk | contribs) |
||
Line 67: | Line 67: | ||
If unsure, consider reviewing existing VOC files and noticing which audio corresponds to the specific message in the mission file. | If unsure, consider reviewing existing VOC files and noticing which audio corresponds to the specific message in the mission file. | ||
+ | |||
+ | === File Structure - Internal Files (within LFD) === | ||
+ | |||
+ | All audio for in-flight messages are stored within an LFD file named after the battle number and mission number it represents (ex: 1M1.lfd for Battle #1 Mission #1). It should always have the same name as the folder in which it resides. | ||
+ | |||
+ | This specific LFD file simply stores all audio for in-flight messages as a collection. However, the files within the LFD have their own naming convention that must be followed. TIE Fighter identifies which audio file to play within the LFD based on the name of the audio file stored within the LFD. If it cannot load an audio file (either because it does not exist within the LFD or because it is not in the correct audio format), it will not play any audio. | ||
+ | |||
+ | The format of the audio for in-flight messages stored within the LFD is as follows: | ||
+ | |||
+ | {| class="wikitable" | ||
+ | |- | ||
+ | ! Battle # !! M !! Mission # || Type () || Message # | ||
+ | |} | ||
== Audio Format == | == Audio Format == |
Revision as of 10:44, 15 July 2024
Audio files in TIE Fighter (for its CD and Remastered editions only) provide audio for briefings, debriefings, and in-flight radio messages. These files can be modified to provide custom audio files, which in turn can allow mission creators to accompany their custom missions with audio that matches their own custom briefings and in-flight radio messages.
This page serves as a guide on how to configure custom audio files for TIE Fighter, as well as an explanation for how audio files work in TIE Fighter.
Limitations
TIE Fighter CD vs. TIE Fighter Remastered
Audio is available in both TIE Fighter CD and TIE Fighter Remastered (95/98); however, only in TIE Fighter Remastered are the audio files stored on the user's hard drive. While it is possible to use custom audio on TIE Fighter CD, it would necessitate creating a new CD image / ISO with the updated files, or using a tool (such as XCDR) that could swap files from being read on the hard drive instead of on the disk. As both scenarios require considerable effort, this page will focus explicitly on the installation of custom audio for TIE Fighter Remastered, even though the steps and information would also apply to TIE Fighter CD in most cases.
Sixteen Radio Messages
By design, TIE Fighter only supports 16 in-flight radio messages (not counting mission complete/failure messages). While there are mixed results with having messages above this limit in TIE Fighter Remastered, this is not supported, and under no circumstances will function with audio messages.
Secret Order Debriefing Audio
Audio for the Secret Order member in TIE Fighter is hard-coded to run based on whether the ***secondary*** mission objectives are successful or not. It does not matter what the mission itself has been coded to display.
For example, a mission that has been configured for the Secret Order member to reply when the primary objectives are complete will play the audio for secondary objectives failed if the secondary objectives were not completed (or did not exist).
In general, this speaks to a standard principal: TIE Fighter is expecting certain standard behaviors when it comes to what audio is played, and anything outside of the standard game experience is unlikely to function as desired.
Location and File Structure
Folder Structure
All audio voice files are located within the VOICE folder in the TIE Fighter installation path for TIE Fighter Remastered (for TIE Fighter CD, they are stored on the root folder of the CD).
Within the VOICE folder, all folders use the following structure, to identify what mission they are for
Battle # | M | Mission # |
---|
Where Battle # represents which number battle the mission is for, and Mission # represents which mission number within the battle the mission is. For example, to find audio for mission 6 in Battle 1, you would navigate to the **1M6** folder.
(For the Historical missions, "A" is the Battle # for the TIE Advanced, "G" for Assault Gunboat, "D" for TIE Defender, "F" for TIE Fighter, "B" for TIE Bomber", "I" for TIE Interceptor", and "M" for Missile Boat).
Within each folder, there is an LFD with a name that matches the folder (ex: 1M6.LFD). All audio for in-flight radio messages are stored within the LFD. All briefing/debriefing audio are stored as external files within the folder. Both the audio files stored individually (for briefings/debriefings) and the audio files stored within the LFD (in-flight radio messages) all have their own naming convention that must be followed in order for the game engine to load them.
File Structure - External Files (non-LFD)
TIE Fighter load certain audio files to play during briefing and de-briefing based on the name of the audio file within the appropriate mission folder. If it cannot load an audio file (either because it does not exist or because it is not in the correct audio format), it will not play any audio.
The format of these briefing/debriefing audio files is as follows:
Battle # | M | Mission # | Type (I, OB, OD, OH, PB, PD, PH) | Message # | .VOC |
---|
Battle # and Mission # refer to the battle number and battle mission number respectively for the mission, and should match the folder they are contained within.
Types determine where and under what circumstance the audio will play. Each type option is explained in more detail below:
- I (or Initial Map Briefing): Audio that plays during each map message on the initial map briefing
- OB (or Officer Briefing): Audio that plays from the Briefing Officer during the briefing (pre-flight)
- OB or Officer Debriefing: Audio that plays from the Briefing Officer during the debriefing (post-flight) when the primary objectives are complete.
- OH or Officer Hints: Audio that plays from the Briefing Officer during the debriefing (post-flight) when the primary objectives failed or were incomplete.
- PB (or Priest/Secret Order Briefing): Audio that plays from the Priest / Secret Order representative during the briefing (pre-flight)
- PB or Priest/Secret Order Debriefing: Audio that plays from the Priest / Secret Order representative during the debriefing (post-flight) when the secondary objectives are complete.
- PH or Priest/Secret Order Hints: Audio that plays from the Priest / Secret Order representative during the debriefing (post-flight) when the secondary objectives failed or were incomplete.
Message # refers to which numbered item the audio pertains to. For a map, this means "2" would play for the second map message. For a briefing officer, "4" would pertain to whatever is set for "Question 4".
To gain a better understanding of the above, consider the following examples:
- 1M1OB1.VOC - This audio will play for Battle #1 Mission #1 ("1M1") during the briefing ("B") when the player selects the Briefing Officer's ("O") first ("1") question.
- 1M1I3.VOC - This audio will play for Battle #1 Mission #1 ("1M1") on the briefing map ("I") when the third ("3") message appears.
- 1M2PD1.VOC - This audio will play for Battle #1 Mission #2 ("1M2") during the debriefing (after the mission) when the secondary objectives have been complete ("D") and the player selects the Priest / Secret Order representative's ("P") first ("1") question.
- 1M2OH1.VOC - This audio will play for Battle #1 Mission #2 ("1M2") during the debriefing (after the mission) when the primary objectives failed/were incomplete ("H") and the player selects the Briefing Officer's ("B") first ("1") question.
If unsure, consider reviewing existing VOC files and noticing which audio corresponds to the specific message in the mission file.
File Structure - Internal Files (within LFD)
All audio for in-flight messages are stored within an LFD file named after the battle number and mission number it represents (ex: 1M1.lfd for Battle #1 Mission #1). It should always have the same name as the folder in which it resides.
This specific LFD file simply stores all audio for in-flight messages as a collection. However, the files within the LFD have their own naming convention that must be followed. TIE Fighter identifies which audio file to play within the LFD based on the name of the audio file stored within the LFD. If it cannot load an audio file (either because it does not exist within the LFD or because it is not in the correct audio format), it will not play any audio.
The format of the audio for in-flight messages stored within the LFD is as follows:
Battle # | M | Mission # | Type () | Message # |
---|