# Sound Occlusion Integration Using Plugin Parameters Issue

**URL:** https://qa.fmod.com/t/sound-occlusion-integration-using-plugin-parameters-issue/23022
**Category:** Unreal Engine
**Tags:** ue5
**Created:** [June 8, 2025, 8:26pm UTC](https://qa.fmod.com/t/sound-occlusion-integration-using-plugin-parameters-issue/23022 "2025-06-08T20:26:59Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![zymian](https://avatars.discourse-cdn.com/v4/letter/z/bc79bd/32.png) [@zymian](https://qa.fmod.com/u/zymian)
#### Post date: [June 8, 2025, 8:26pm UTC](https://qa.fmod.com/t/sound-occlusion-integration-using-plugin-parameters-issue/23022/1 "2025-06-08T20:26:59Z")

</div>

Hello!

I’m trying to use the Occlusion parameter in the Fmod Plugin section within the Unreal Engine project settings.

While this is working correctly and passing what I want to certain events, it seems that the parameter is getting passed to all Fmod events no matter whether the Fmod Audio Component has Occlusion enabled or not.

This is causing a heap of errors from Fmod Audio components that will never need to use this Occlusion parameter.

Am I doing something wrong in my integration between Unreal Engine and Fmod of this parameter? Should I look into a different custom way of dealing with Occlusion parameter passing to Fmod for these certain audio components?

I’m currently using UE 5.5 and Fmod 2.03.06 in my project.

Thanks, any help here would be appreciated!

---

<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: [June 18, 2025, 2:03am UTC](https://qa.fmod.com/t/sound-occlusion-integration-using-plugin-parameters-issue/23022/2 "2025-06-18T02:03:38Z")

</div>

Thanks for reporting this, from what I can see these errors should only be visible when the `Enable API Logging` option is enable in the settings.

I have created a task to see if we can remove the chance of these errors showing up on events that aren’t using occlusion at all.
