Extracting Game Files

The first time you open FModel you will be presented with a Directory Selector. If you have already opened FModel in the past, you’ll be opened to another window, so you can bring the selector up again via Directory > Selector.

Under the "Add Undetected Game" heading, click the two-arrows icon, enter Satisfactory as the "Name", and enter your game install directory as the "Directory" (for example, C:\EpicGamesGames\SatisfactoryExperimental). Next, press the blue Plus button (NOT the OK button!) to add the game to the Detected Game dropdown, which should automatically select it. Back in the upper section, select GAME_UE5_3 (536870960) for the "UE Versions" selector. If this item doesn’t appear in the list, ensure "Enable custom UE versions" is unchecked. After confirming that the game is selected, press the OK button.

The program should launch and display FactoryGame-Windows.utoc in the Archives tab list, along with the paks and utocs of any other mods you may have installed. If it opens another game instead, return to the directory selector and review the above steps.

Unreal Engine 5 changed how assets are stored in packaged files. You will need to provide FModel with extra information so that it can read the data correctly. Coffee Stain Studios kindly ships this extra information with the game files for us.

First, navigate to your game install directory in a File Explorer window to locate the /CommunityResources/FactoryGame.usmap and /CommunityResources/CustomVersions.json files.

We need to open the CustomVersions file and copy its contents into a setting in FModel. However, the file is stored in a text encoding (UTF-16 LE) that can confuse some text editing programs. Many editors will auto-detect the encoding, but you may need to specifically select the UTF-16 LE encoding when opening the file if the text displays with egregious spacing.

To start loading this additional information, open FModel and navigate to Settings > General, then press the Custom Versions button in the "Version Configuration" row which opens a new text editing window.

Delete the text contents of the popup window and replace it with the copied contents of the CustomVersions.json file from your Community Resources folder, then press OK to save your changes.

Back on the Settings screen, check the box for "Local Mapping File" and then enter the full path to your FactoryGame.usmap file, which is also in the Community Resources folder, (for example, C:\EpicGamesGames\SatisfactoryExperimental\CommunityResources\FactoryGame.usmap).

Press OK to close the settings prompt, which will open another prompt asking you to restart FModel - press OK.

After specifying FModel’s Custom Version and Mapping for Satisfactory you will want change model export settings so it’s easier to work with exported results. To do so, return to the Settings menu and select Models on the left side.

From here there are several fields to modify in order to properly export models for use with modeling software such as Blender:

Press OK to save your changes.

Now that your settings have been configured correctly, navigate to the Archives tab in the FModel interface. This tab displays pak and utoc files located in subfolders of the directory you selected earlier. The base game’s utoc, FactoryGame-Windows.utoc, should be present, as well as utocs for any mods you have installed.

To load a utoc, select it and press the Load button. This enables browsing its contents in the Folders and Packages tab.

In order to perform a pak-wide search, navigate to Packages > Search or press the keybind (Ctrl+Shift+F). You can also search within a specific package by navigating to it in the Folders tab then using the search bar built into the Packages tab.

FModel’s search supports multiple terms, returning results that match all terms. For example, the search query Cave Play would find the assets Play_M_SmallCave_Parameter, Play_Boombox_JoelSyntholm_CaveFlowers and more.

Regular expression searches can be enabling via a button at the right side of the search bar.

Because Satisfactory uses the Wwise sound system, game sound files are stored in a manner different from standard Unreal Engine sounds.

Although all sound files are accessible via FModel, usage of Wwise means the files are not sensibly organized and do not have "nice" names, making finding the exact sounds you care about troublesome. Furthermore, the sound files are stored in their unmixed forms, meaning that the sound is lacking additional audio effects that are applied real-time in-game.

Thankfully, another tool exists to mitigate this problem. wwiser is capable of viewing data in Wwise bnk files, allowing you to connect a Wwise sound event (which has a human-readable-name) to the sound files it references.

The first step in extracting a sound is to locate the Wwise audio event bnk it’s triggered by.

Wwise bnk files contain information about what sound files are used by the game when a sound event is triggered. We can extract this file and use it in wwiser to locate the raw sound files we care about.

Wwise audio event names are human-readable and can be found in subfolders of the pak’s (not utoc’s!) FactoryGame/Content/WwiseAudio/Event/ folder. Note that bnk files are not in the Events (plural) folder, which instead contains their identically-named uasset counterparts not required for this process. You may still find the Events folder useful for leaning the context of sound events. For example, /Events/World_Events_FilatovD/Environment/Caves/ presumably contains environmental sounds that would play while in caves.

FModel’s Package Search functionality is beneficial for finding specific sounds. Events that begin sound playback follow the naming scheme Play_something.bnk, so you can search for Play something bnk to find a list of valid sound bnk files containing something.

Once you have found the bnk you want to extract (for example, FactoryGame/Content/WwiseAudio/Event/19/Play_EQ_JetPack_Activate.bnk) right click on it in FModel’s "Packages" tab list and select Export Raw Data (.uasset), which will export the bnk file despite the tooltip option claiming it will be a uasset.

Alternatively, you can extract the entire Event folder at once by right clicking on it in the "Folders" tab and selecting Export Folder’s Packages Raw Data (.uasset).

Click on the text (ex. Play_EQ_JetPack_Activate.bnk) in the FModel log to open your system’s file browser to the folder that contains the exported bnk, or the top-level export folder if you exported the entire Event folder.

You will need Python installed to utilize wwiser. Python 3.8.10 is known to work, and pyenv is the suggested method of install. Installing python is out of the scope of this guide.

Download the latest copy of wwiser from its releases page. You’ll want both the wwiser.pyz and wwnames.db3 files from the release.

Use a zip extracting program of your choice to extract the files from wwiser.pyz and place the wwnames.db3 file in the same directory as the extracted files.

To open the wwiser interface, run python .\wwiser.py in a terminal in that folder. Next, select Load banks…​ and select the bnk file you extracted earlier.

Check wwiser’s log panel before continuing. If it contains the message names: couldn’t find .\wwnames.db3 name file, go back to grab the wwnames.db3 from the GitHub release and put it in the same folder as the bnk file you opened.

Next, select Generate TXTP which will create a folder in the same directory as the bnk file containing a txtp file for the event. (ex. Play_EQ_JetPack_Activate {s} {m}.txtp)

Open the txtp file in a text editor of your choice. If the bnk is linked to any sound files their sourceID numbers will be displayed at the top of the file (ex. wem/633850317.wem has the sourceID number 633850317) along with additional audio information.

Sound events typically consistent of multiple sounds played at different volumes. Take note of all the sourceIDs of the event as you will likely need to review a few raw sounds to find the exact one you’re looking for.

Now that we have sourceIDs we can use FModel to locate and extract their corresponding sound files.

First, locate the sound file in FModel via its sourceID, which will be its package file name. Using FModel’s Package Search functionality is beneficial here. All game audio can be found in subfolders of the pak’s (note - NOT the utoc!) FactoryGame/Content/WwiseAudio/Media/ folder.

To extract a sound file, first open its Package from the main window, which will cause an Audio Player window to appear. After optionally previewing the sound file in the player, right click on it in the player’s playlist and select Save, prompting a system dialog to select a save location.

Community member MrCheese has created a python script that enables mass renaming of exported wem files to their associated named bnk files. If you decide to extract a large number of sounds, this script can save you a lot of time.

To use it: