# Build output directory being changed with source control commit

**URL:** <https://qa.fmod.com/t/build-output-directory-being-changed-with-source-control-commit/20358>\
**Category:** FMOD Studio\
**Tags:** unity\
**Created:** [June 27, 2023, 4:55pm UTC](https://qa.fmod.com/t/build-output-directory-being-changed-with-source-control-commit/20358 "2023-06-27T16:55:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![g.hadji](https://avatars.discourse-cdn.com/v4/letter/g/b19c9b/32.png) [@g.hadji](https://qa.fmod.com/u/g.hadji)\
**Post date:** [June 27, 2023, 4:55pm UTC](https://qa.fmod.com/t/build-output-directory-being-changed-with-source-control-commit/20358/1 "2023-06-27T16:55:07Z")

</div>

Hello.

We are 3 sound designers in my team, working on the same fmod project. We found out that when someone is pushing his version of the fmod session, it automatically sets up his absolute local path for the built banks output directory as the new path for everyone on the repository. It is pretty anoying because everytime you’re pulling a new commit, you have to think about reseting your own local path as the output directory for the built bank, and it is a very easy thing to forget.

We thought about adding the file containing this data to the ignore file in the source control. But I can’t find such a file. Is this something possible? I searched into project folder, since this data seems to be relative to project.

Thanks !

---

<div class="post-metadata">

**Author:** ![Connor\_FMOD](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/connor_fmod/32/3685_2.png) [@Connor\_FMOD](https://qa.fmod.com/u/Connor_FMOD)\
**Post date:** [June 28, 2023, 1:43am UTC](https://qa.fmod.com/t/build-output-directory-being-changed-with-source-control-commit/20358/2 "2023-06-28T01:43:39Z")

</div>

Hi,

Unfortunately, this is not a preference that can be ignored. In our documentation ([FMOD Studio | Souce Control](https://fmod.com/docs/2.02/studio/using-source-control.html#:~:text=The%20built%20banks%20output%20directory%20is%20the%20same%20for%20all%20users%20of%20a%20project%2C%20so%20it%20should%20be%20set%20to%20a%20relative%20or%20absolute%20path%20that%20everyone%20collaborating%20on%20the%20project%20agrees%20on.%20It%20is%20possible%20to%20change%20the%20bank%20build%20directory%20later%2C%20but%20doing%20so%20changes%20it%20for%20all%20users)) the `Built bank output directory` has to be the same for everyone collaborating on the project.