# FMOD\_ERR\_EVENT\_ALREADY\_LOADED when re-loading an unloaded master bank

**URL:** <https://qa.fmod.com/t/fmod-err-event-already-loaded-when-re-loading-an-unloaded-master-bank/12827>\
**Category:** FMOD Studio\
**Created:** [November 22, 2016, 1:00am UTC](https://qa.fmod.com/t/fmod-err-event-already-loaded-when-re-loading-an-unloaded-master-bank/12827 "2016-11-22T01:00:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bsupnik](https://avatars.discourse-cdn.com/v4/letter/b/a5b964/32.png) [@bsupnik](https://qa.fmod.com/u/bsupnik)\
**Post date:** [November 22, 2016, 1:00am UTC](https://qa.fmod.com/t/fmod-err-event-already-loaded-when-re-loading-an-unloaded-master-bank/12827/1 "2016-11-22T01:00:51Z")

</div>

Our app sometimes synchronously unloads and reloads the same master bank - while this isn’t the most efficient thing ever, it’s a side effect of fully tearing down and then rebuilding the FMOD environment based on a user selecting a new aircraft.

In the field we’re seeing intermittent cases of FMOD\_ERR\_EVENT\_ALREADY\_LOADED.

fmod studio is initialized normally (not in synchronous mode) and we are using blocking loads.

Do we need to do a studio::flushCommands after unload before the load to ensure correct ordering? All functions are being called from the main thread of our code, so we don’t think it’s a race condition in our own code.

---

<div class="post-metadata">

**Author:** ![Derek\_Burnheim](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/derek_burnheim/32/261_2.png) [@Derek\_Burnheim](https://qa.fmod.com/u/Derek_Burnheim)\
**Post date:** [November 22, 2016, 5:23am UTC](https://qa.fmod.com/t/fmod-err-event-already-loaded-when-re-loading-an-unloaded-master-bank/12827/2 "2016-11-22T05:23:45Z")

</div>

Hi Ben,

Yes, you will need to call either Studio::flushCommands or Studio::Update after you’ve unloaded the banks to make this work correctly.