# ERR\_OUTPUT\_INIT when clean-building on a headless machine

**URL:** <https://qa.fmod.com/t/err-output-init-when-clean-building-on-a-headless-machine/20880>\
**Category:** Unity\
**Tags:** unity\
**Created:** [November 15, 2023, 2:20pm UTC](https://qa.fmod.com/t/err-output-init-when-clean-building-on-a-headless-machine/20880 "2023-11-15T14:20:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndrewFray](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@AndrewFray](https://qa.fmod.com/u/AndrewFray)\
**Post date:** [November 15, 2023, 2:20pm UTC](https://qa.fmod.com/t/err-output-init-when-clean-building-on-a-headless-machine/20880/1 "2023-11-15T14:20:28Z")

</div>

we’re using an aws windows machine connected to jenkins to make builds of our game.

we’ve noticed that on a clean sync, the resulting build won’t function correctly, and will throw a ton of fmod errors, including not finding busses.

this error error in the output:  
`FMOD Studio: Encountered Error: ERR_OUTPUT_INIT Error initializing output device`

if we remote into the server and open unity, subsequent builds will work, and won’t have the error.

we _recently_ removed the fmodcache from source control, and rely on the server to generate it itself. we did this because we found everyone needed to check it out in perforce. I’m assuming there’s something about the headlessness of the build server that’s stopping it generating the cache the first time?

if we commit fmodcache again, but make it writable, when should it ever be committed, and by who? if we leave it out of source control, how do we properly generate it on a headless server?

thanks!

---

<div class="post-metadata">

**Author:** ![jeff\_fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/jeff_fmod/32/1766_2.png) [@jeff\_fmod](https://qa.fmod.com/u/jeff_fmod)\
**Post date:** [November 21, 2023, 12:22am UTC](https://qa.fmod.com/t/err-output-init-when-clean-building-on-a-headless-machine/20880/2 "2023-11-21T00:22:16Z")

</div>

There should be no need to track anything in Plugins/FMOD/Cache/ as this should be generated programmatically. You should be able to force cache creation with a call to `FMODUnity.EventManager.RefreshBanks` at the start of your build script. Can you please try adding that in and let me know if that helps at all?  
If you could also please tick [_Enable API Error Logging_](https://fmod.com/docs/2.02/unity/settings.html#enable-api-error-logging), set your [_Logging Level_](https://fmod.com/docs/2.02/unity/settings.html#logging-level) to “Log” and send me the output of your build log, that might reveal some more information on what’s failing.

---

<div class="post-metadata">

**Author:** ![AndrewFray](https://avatars.discourse-cdn.com/v4/letter/a/90ced4/32.png) [@AndrewFray](https://qa.fmod.com/u/AndrewFray)\
**Post date:** [December 1, 2023, 9:07am UTC](https://qa.fmod.com/t/err-output-init-when-clean-building-on-a-headless-machine/20880/3 "2023-12-01T09:07:50Z")

</div>

> [@jeff\_fmod](#):
>
> ity.EventManager.RefreshBan

thank you, calling RefreshBanks within our build function seemed to fix things!