# Unable to build: Settings instance has not been initialized. Unable to continue build

**URL:** <https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668>\
**Category:** Unity\
**Created:** [December 20, 2022, 1:14pm UTC](https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668 "2022-12-20T13:14:01Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Bissonho](https://avatars.discourse-cdn.com/v4/letter/b/779978/32.png) [@Bissonho](https://qa.fmod.com/u/Bissonho)\
**Post date:** [December 20, 2022, 1:40pm UTC](https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668/2 "2022-12-20T13:40:54Z")

</div>

I’m having the same problem in the post

> [@Errors when launching FMOD after the project has been cloned to another machine](https://qa.fmod.com/t/errors-when-launching-fmod-after-the-project-has-been-cloned-to-another-machine/19666/2):
>
> Hi, Could you post your current .gitignore? Could you check how many FMODStudioSettings.assets are in the Unit Project/Assets/Plugins/Resources/ Folder? [image] If there is more than 1, try deleting all of them, this should make them recompile. Hope this helps!

---

_[View the full topic](https://qa.fmod.com/t/unable-to-build-settings-instance-has-not-been-initialized-unable-to-continue-build/19668)._