# Best practices for setting up new FMOD + Unity project and version control - review my guide?
**URL:** https://qa.fmod.com/t/best-practices-for-setting-up-new-fmod-unity-project-and-version-control-review-my-guide/22872
**Category:** Unity
**Created:** [May 3, 2025, 2:36am UTC](https://qa.fmod.com/t/best-practices-for-setting-up-new-fmod-unity-project-and-version-control-review-my-guide/22872 "2025-05-03T02:36:24Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@twel\_ch](https://qa.fmod.com/u/twel_ch)
#### Post date: [May 3, 2025, 2:36am UTC](https://qa.fmod.com/t/best-practices-for-setting-up-new-fmod-unity-project-and-version-control-review-my-guide/22872/1 "2025-05-03T02:36:24Z")
## Setting up FMOD with Unity 6000.0.47f1
### Step 1: Install the correct FMOD versions
1. Create an account on the FMOD website if you don’t already have one
2. Download FMOD Studio 2.02.28 (the desktop application)
3. Download FMOD for Unity integration package 2.02.28 from either:
- The [FMOD website](https://www.fmod.com/download) in the Unity Integration section
- The [Unity Asset Store](https://assetstore.unity.com/) (search for “FMOD for Unity”)
**Important** : Always ensure both FMOD Studio and the Unity integration package are the same version (2.02.28) to avoid compatibility issues.
### Step 2: Import the FMOD integration package into Unity
1. Open your Unity 6000.0.47f1 project
2. Go to Assets → Import Package → Custom Package
3. Select the downloaded FMOD for Unity integration package (.unitypackage file)
4. In the import window, ensure all components are selected and click “Import”
5. The FMOD Setup Wizard will appear automatically after import completes
### Step 3: Configure the FMOD Setup Wizard
1. Click “Start” in the FMOD Setup Wizard
2. For the “Updating” section (if shown), follow the prompts to update existing FMOD references
3. For project access method, select “Multiple Platform Build” (recommended for version control)
4. **Important** : You’ll be asked to locate the build folder. If you don’t have a StreamingAssets folder:
- Navigate to your Unity project’s Assets folder
- Create a new folder named “StreamingAssets” (if it doesn’t exist)
- Inside StreamingAssets, create another folder named “FMOD”
- Select this newly created “FMOD” folder as your build location
5. Next, you’ll either need to select an existing FMOD Studio project (.fspro file) or create a new one
- If you already have an FMOD project, browse to select it
- If you don’t have one yet, FMOD will create one for you when you build your first banks
6. **Replace Unity audio with FMOD** : Enable this option to disable Unity’s audio system
7. If prompted about existing Audio Sources, review and decide which to convert to FMOD
8. Note the recommended .gitignore settings (we’ll implement these in Step 5)
### Step 4: Configure FMOD project settings
1. Open FMOD Studio and your FMOD project
2. Go to Edit → Preferences → Build
3. Set your build path to the StreamingAssets folder in your Unity project:
- `[Your Unity Project Path]/Assets/StreamingAssets/FMOD`
4. Under Build Platform, select all platforms your game will support
5. Set the “Bank Platform” to match your primary development platform
## Making it version control friendly
### Step 5: Create a proper .gitignore file
Create or update your project’s .gitignore file to include these FMOD-specific entries:
```auto
# Never ignore DLLs in the FMOD subfolder.
!/[Aa]ssets/Plugins/FMOD/**/lib/*
# Don't ignore images and gizmos used by FMOD in the Unity Editor.
!/[Aa]ssets/Gizmos/FMOD/*
!/[Aa]ssets/Editor Default Resources/FMOD/*
# Ignore the Cache folder since it is updated locally.
/[Aa]ssets/Plugins/FMOD/Cache/*
# Ignore bank files in the StreamingAssets folder.
/[Aa]ssets/StreamingAssets/**/*.bank
/[Aa]ssets/StreamingAssets/**/*.bank.meta
# Log files can be ignored.
fmod_editor.log
```
### Step 6: Set up your FMOD project folder structure
1. Create a dedicated folder for your FMOD Studio project **outside** your Unity project directory
- Recommended: `[Your Unity Project Path]/../FMODProject/`
2. Move your FMOD project (.fspro file and related assets) to this folder
3. Update your build path in FMOD Studio to point to your Unity project’s StreamingAssets folder
### Step 7: Configure FMOD Studio for multi-user workflow
1. In FMOD Studio, go to Edit → Preferences → Source Control
2. Enable source control integration if working with a team
3. Set up appropriate source control settings in FMOD Studio
4. Configure your .gitignore in the FMOD project folder to exclude:
- `.user` files
- `.cache` files
- `.unsaved` files
- Log files
## Best practices for version control
### What to include in version control
1. **FMOD Unity integration files** : The core FMOD plugin files in the Assets/Plugins/FMOD directory
2. **FMOD compiled bank files** : All .bank files in your StreamingAssets folder
3. **FMOD settings** : The FMOD Settings asset that contains your project configuration
### What to exclude from version control
1. **FMODStudioCache.asset** : This is regenerated when the project is opened
2. **fmod\_editor.log** : Log files that change frequently
3. **Temporary files** : All `.cache`, `.user`, and other temporary files
4. **FMOD Studio project files** : Keep these in a separate repository or folder
### Working with a team
1. **Decide on FMOD project location** :
2. **Bank build responsibility** :
3. **Handling audio asset changes** :
## Troubleshooting common issues
### Missing banks or audio not playing
If banks are missing or audio isn’t playing:
1. Verify banks exist in StreamingAssets/FMOD folder
2. Check that bank path in FMOD settings matches your StreamingAssets path
3. Rebuild banks in FMOD Studio and ensure they’re exported to the correct location
---
### Author:  [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)
#### Post date: [May 15, 2025, 6:27am UTC](https://qa.fmod.com/t/best-practices-for-setting-up-new-fmod-unity-project-and-version-control-review-my-guide/22872/2 "2025-05-15T06:27:32Z")
The specifics of setting up FMOD and Unity will depend on the exact needs of your project, but as a broad outline on setting them up for use with version control, your guide seems accurate!
---
### Author:  [@tom.baltaks](https://qa.fmod.com/u/tom.baltaks)
#### Post date: [December 6, 2025, 12:10pm UTC](https://qa.fmod.com/t/best-practices-for-setting-up-new-fmod-unity-project-and-version-control-review-my-guide/22872/3 "2025-12-06T12:10:01Z")
In this post you show the .gitignore recommendations from the set up wizard ignoring: /[Aa]ssets/StreamingAssets/\*\*/\*.bank
/[Aa]ssets/StreamingAssets/\*\*/\*.bank.meta
…but you state in the ‘What to include in version control’ section:
> [@twel\_ch](#):
>
> **FMOD compiled bank files** : All .bank files in your StreamingAssets folder
… I’m quite confused.
---
### Author:  [@Leah\_FMOD](https://qa.fmod.com/u/Leah_FMOD)
#### Post date: [December 9, 2025, 6:33am UTC](https://qa.fmod.com/t/best-practices-for-setting-up-new-fmod-unity-project-and-version-control-review-my-guide/22872/4 "2025-12-09T06:33:18Z")
I can’t speak for @twel_ch , but the inclusion of built banks in source control is optional, and often avoided in order to decrease file sizes. Instead, assuming you also have access to the source FMOD Studio project, you would build banks from the Studio project to generate them for the Unity project.