# Disable spatialized sounds

**URL:** <https://qa.fmod.com/t/disable-spatialized-sounds/18943>\
**Category:** FMOD Engine\
**Tags:** cpp\
**Created:** [June 27, 2022, 6:42pm UTC](https://qa.fmod.com/t/disable-spatialized-sounds/18943 "2022-06-27T18:42:50Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rontt](https://avatars.discourse-cdn.com/v4/letter/r/779978/32.png) [@rontt](https://qa.fmod.com/u/rontt)\
**Post date:** [June 27, 2022, 6:42pm UTC](https://qa.fmod.com/t/disable-spatialized-sounds/18943/1 "2022-06-27T18:42:50Z")

</div>

I need to offer a player option to disable spatialized sounds. It does appear that if the sound is spatialized and I start it without setting the FMOD\_Studio\_EventInstance\_Set3DAttributes it just doesn’t play. Is there a way disable spatialized sounds even if the event is spatialized? I’m also trying to track down some performance issues that seem to go way if I hack the sounds to not be spatialized.

---

<div class="post-metadata">

**Author:** ![joseph](https://yyz2.discourse-cdn.com/flex036/user_avatar/qa.fmod.com/joseph/32/264_2.png) [@joseph](https://qa.fmod.com/u/joseph)\
**Post date:** [June 28, 2022, 12:07am UTC](https://qa.fmod.com/t/disable-spatialized-sounds/18943/2 "2022-06-28T00:07:10Z")

</div>

> [@rontt](#):
>
> Is there a way disable spatialized sounds even if the event is spatialized?

Yes, but the method of doing so depends on what you mean by “disable.”

Not setting an event’s FMOD\_Studio\_EventInstance\_Set3DAttributes means you’re not providing FMOD Studio with the event instance’s coordinates, but doesn’t change what effects are in the event - meaning that its spatializing effects are still present and still spatialize the event instance, but use the default coordinates of 0,0,0.

If I understand correctly, you want to disable the spatialization of events. To achieve this, you’ll need to provide an alternate routing path that bypasses each events’ spatializing effect, most likely by using a pre-spatializer send that targets a return bus in your mixer and a snapshot that controls whether the return bus or the group buses into which your events’ outputs are routed are ducked to -oo.

> [@rontt](#):
>
> I’m also trying to track down some performance issues that seem to go way if I hack the sounds to not be spatialized.

I’m curious as to what these performance issues are. What form of spatialization are you using that is consuming too many resources?
