# Occlusion implementation

**URL:** <https://qa.fmod.com/t/occlusion-implementation/16397>\
**Category:** FMOD Studio\
**Created:** [November 5, 2020, 11:08am UTC](https://qa.fmod.com/t/occlusion-implementation/16397 "2020-11-05T11:08:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![oliwoodt17](https://avatars.discourse-cdn.com/v4/letter/o/6a8cbe/32.png) [@oliwoodt17](https://qa.fmod.com/u/oliwoodt17)\
**Post date:** [November 5, 2020, 11:08am UTC](https://qa.fmod.com/t/occlusion-implementation/16397/1 "2020-11-05T11:08:20Z")

</div>

Hi, it looks to of been a while since this was asked so thought I would give it a bump.

It would be great to be able to have multiple events occluded at a more centralized level, rather than having to apply it to each event. Is there a more global application in the works, or already available that I am unaware of?

It would be incredibly useful… Especially when working with larger projects.

Thanks.

---

<div class="post-metadata">

**Author:** ![LenneR](https://avatars.discourse-cdn.com/v4/letter/l/ce73a5/32.png) [@LenneR](https://qa.fmod.com/u/LenneR)\
**Post date:** [November 5, 2020, 11:16am UTC](https://qa.fmod.com/t/occlusion-implementation/16397/2 "2020-11-05T11:16:08Z")

</div>

I’m actually wondering the same. Also wondering if, in the current workflow, there is an easy way to copy all properties that make up my occlusion to other events. Or maybe even the option to create an Occlusion preset and add it to events optionally.

---

<div class="post-metadata">

**Author:** ![mathew](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/mathew/32/431_2.png) [@mathew](https://qa.fmod.com/u/mathew)\
**Post date:** [November 5, 2020, 9:53pm UTC](https://qa.fmod.com/t/occlusion-implementation/16397/3 "2020-11-05T21:53:50Z")

</div>

On the calculation of occlusion value side of things we don’t have anything immediately available but it is on our list for addressing in the new year as part of our integrations.

On the application of occlusion value side of things the current approach would be to create a preset effect (or preset effect chain) tying an occlusion parameter to a series of effect properties. Then apply that preset to all events (and/or setup a default event that uses it). You need to drive the occlusion parameter with your own game code, but the behavior can be fully designed in Studio.