# SetEvent clearing automatedparametercache

**URL:** <https://qa.fmod.com/t/setevent-clearing-automatedparametercache/24399>\
**Category:** Unreal Engine\
**Created:** [July 15, 2026, 12:15pm UTC](https://qa.fmod.com/t/setevent-clearing-automatedparametercache/24399 "2026-07-15T12:15:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tom\_Jansen](https://avatars.discourse-cdn.com/v4/letter/t/9fc348/32.png) [@Tom\_Jansen](https://qa.fmod.com/u/Tom_Jansen)\
**Post date:** [July 15, 2026, 12:15pm UTC](https://qa.fmod.com/t/setevent-clearing-automatedparametercache/24399/1 "2026-07-15T12:15:28Z")

</div>

Hello,

We recently upgraded our project from Unreal 5.5.4 to 5.7 alongside upgrading FMOD Unreal integration from 2.03.11 to 2.03.14.

In our project we use _SetEvent_ calls on the _FMODAudioComponent_ to change between events we want to play. After upgrading this method became broken. I have it locally fixed but perhaps there is more wrong or something I misunderstand?

_SetEvent_ clears the newly added _AutomatedParameterCache_ but does not repopulate causing the occlusion to break on _PlayInternal_. That said  
adding a call _CacheDefaultParameterValues()_ after the event is updated is not sufficient as _GetParameterDescriptions_ is set for Editor  
and returns a nullptr in a non-editor build. I changed this to _FMOD::Studio::EventDescription \*EventDesc = IFMODStudioModule::Get().GetEventDescription(this, EFMODSystemContext::Max);_

Thank you

---

<div class="post-metadata">

**Author:** ![cameron-fmod](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/cameron-fmod/32/261_2.png) [@cameron-fmod](https://qa.fmod.com/u/cameron-fmod)\
**Post date:** [July 24, 2026, 4:47am UTC](https://qa.fmod.com/t/setevent-clearing-automatedparametercache/24399/2 "2026-07-24T04:47:01Z")

</div>

> [@Tom\_Jansen](#):
>
> _SetEvent_ clears the newly added _AutomatedParameterCache_ but does not repopulate causing the occlusion to break on _PlayInternal_

Thanks for reporting this, we have an upcoming fix for the `EFMODSystemContext` in `UFMODEvent::GetParameterDescriptions`. I have added another task to cache the parameters of the new event being set.