# Master.strings.bank won't build

**URL:** https://qa.fmod.com/t/master-strings-bank-wont-build/23014
**Category:** FMOD Studio
**Tags:** unity
**Created:** [June 4, 2025, 10:49pm UTC](https://qa.fmod.com/t/master-strings-bank-wont-build/23014 "2025-06-04T22:49:52Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Pnaser74](https://avatars.discourse-cdn.com/v4/letter/p/3be4f8/32.png) [@Pnaser74](https://qa.fmod.com/u/Pnaser74)
#### Post date: [June 4, 2025, 10:49pm UTC](https://qa.fmod.com/t/master-strings-bank-wont-build/23014/1 "2025-06-04T22:49:52Z")

</div>

Hi, I recently joined a team and am taking over from the previous sound person. They had already integrated Unity and FMOD. When I cloned the repo, I noticed that a lot of folders were missing from the folder where the FMOD studio file was located (all except “Assets” and “Build”), and I am running into issues. The Unity integration is 2.02.17 and the version of FMOD I’m using is 2.02.25.

When I open the FMOD studio file, it is essentially empty except for the assets. I don’t think there were too many events previously, but when I have tried to recreate the master bank and some of the events, I’ve found that master.strings.bank is not being created upon hitting “build”

I have two questions:

1. Can I salvage this situation without having to delete all references to FMOD in the Unity project? It wouldn’t be the worst, but there are still a dozen or so references to the FMOD namespace in scripts.
2. Is there a way to make sure that the master.strings.bank builds?

Thanks in advance for any help or ideas anyone can share

---

<div class="post-metadata">

### Author: ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)
#### Post date: [June 6, 2025, 6:07am UTC](https://qa.fmod.com/t/master-strings-bank-wont-build/23014/2 "2025-06-06T06:07:25Z")

</div>

Hi,

Thank you for sharing the information and version number!

> [@Pnaser74](#):
>
> Can I salvage this situation without having to delete all references to FMOD in the Unity project? It wouldn’t be the worst, but there are still a dozen or so references to the FMOD namespace in scripts.

It sounds like some essential FMOD project files such as the `Metadata` folder might be missing from your cloned repository. This can result in an empty FMOD Studio project and prevent the `Master.strings.bank` from being generated during the build process.

It’s quite common for `.gitignore` files to exclude important folders like `Metadata`. Could you please double-check your `.gitignore` to make sure this folder is not being ignored?

> [@Pnaser74](#):
>
> Is there a way to make sure that the master.strings.bank builds?

Have you tried using **File \> Validate Project** in FMOD Studio to check for issues? This can often identify missing references or problems that prevent proper bank generation.

Let me know if the issue persists, happy to help further if you have more info to share!

---

<div class="post-metadata">

### Author: ![Pnaser74](https://avatars.discourse-cdn.com/v4/letter/p/3be4f8/32.png) [@Pnaser74](https://qa.fmod.com/u/Pnaser74)
#### Post date: [June 6, 2025, 4:17pm UTC](https://qa.fmod.com/t/master-strings-bank-wont-build/23014/3 "2025-06-06T16:17:39Z")

</div>

Hi, thanks for getting back to me!

I looked back through old commits and saw that the original sound person did in fact add the metadata folder to the `.gitignore` shortly after the commit where they added fmod. They then deleted all of their files after leaving the project 😅

I wound up just creating a new fmod studio session and recreating the events and banks with the same names. It worked without issue, thankfully

---

<div class="post-metadata">

### Author: ![li\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/li_fmod/32/6577_2.png) [@li\_fmod](https://qa.fmod.com/u/li_fmod)
#### Post date: [June 11, 2025, 11:35pm UTC](https://qa.fmod.com/t/master-strings-bank-wont-build/23014/4 "2025-06-11T23:35:57Z")

</div>

Thank you for sharing the solution here! I’m glad to hear you got it working!
