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. After confirming that the game is selected, press the OK button.

The program should launch and display FactoryGame-Windows.pak in the Archives tab list, along with the paks 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 introduced changes in how assets are stored in pak 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.

If you are using Windows 10, Windows Notepad can successfully load the CustomVersions.json file and you can copy its contents to your clipboard normally. If you are using Windows 11, you will need to use another text editor such as Notepad++. Windows 11’s Notepad incorrectly loads the file with UTF-8 encoding and FModel will tell you that you broke the .json if you copy the contents over.

To start loading this additional information, open FModel and navigate to Settings > General. In the "UE Versions" dropdown, select GAME_UE5_2 (536870944), 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. (for example, C:\EpicGamesGames\SatisfactoryExperimental\CommunityResources\CustomVersions.json), 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 (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:

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.

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 find the sound files we care about.

Wwise audio event names are human-readable and can be found in subfolders of the pak’s FactoryGame/Content/WwiseAudio/Event/ folder. Using FModel’s Package Search functionality is beneficial here.

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 and select Export Raw Data (.uasset), which will export the bnk file despite the tooltip option claiming it will be a uasset.

You can click on the text (ex. Play_EQ_JetPack_Activate.bnk) in the log to open your system file browser to the containing 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.

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

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. After the file loads, select Generate TXTP which will create a folder in the same directory as the bnk file containing a txtp file which can be opened with a text editor. (ex. Play_EQ_JetPack_Activate {s} {m}.txtp)

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.

Take note of the sourceIDs of the sound file you want to extract, as you will likely need to review a few sounds to find the exact one you’re looking for.

Now that we have a sourceID, we can use FModel to extract the sound file. All game audio can be found in subfolders of the pak’s FactoryGame/Content/WwiseAudio/Media/ folder.

First, locate the sound file via its sourceID, which will be its package file name. Using FModel’s Package Search functionality is beneficial here.

To extract a sound file, first open its Package in 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 playlist and select Save, prompting a system dialog to select a save location.