Welcome to the Oculus Developer Forums!
Your participation on the forum is subject to the Oculus Code of Conduct.
In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.
Your participation on the forum is subject to the Oculus Code of Conduct.
In general, please be respectful and kind. If you violate the Oculus Code of Conduct, your access to the developer forums may be revoked at the discretion of Oculus staff.
Unity 5.6, Wwise 2016, Oculus SDK 1.1.5 - no spatialization in Large/Multi-position mode
joakim_logtown
Posts: 2 NerveGear
Hi,
I'm currently designing the audio for a VR experience using OSP with Wwise and Unity. A problem that I have is that whenever i'm, in Unity, using the large or multi-position mode of the AkAmbient-component with an event that hosts actors being routed through the Oculus spatializer actual spatialization only occurs for the sound being played from the root location, and not for the added points of emission.
Of course - I can just add additional emitters and have them each play spatialized audio from the intended positions but it is much less performant.
Has anyone else experienced this? Bug or expected behaviour?
If it's caused by the AkAmbient-component that comes with the Wwise-integration, could we get the behaviour we want by posting the event via script instead?
Unity 5.6
Wwise 2016.2.3
OSP 1.1.5
Appreciate any input!
I'm currently designing the audio for a VR experience using OSP with Wwise and Unity. A problem that I have is that whenever i'm, in Unity, using the large or multi-position mode of the AkAmbient-component with an event that hosts actors being routed through the Oculus spatializer actual spatialization only occurs for the sound being played from the root location, and not for the added points of emission.
Of course - I can just add additional emitters and have them each play spatialized audio from the intended positions but it is much less performant.
Has anyone else experienced this? Bug or expected behaviour?
If it's caused by the AkAmbient-component that comes with the Wwise-integration, could we get the behaviour we want by posting the event via script instead?
Unity 5.6
Wwise 2016.2.3
OSP 1.1.5
Appreciate any input!
Tagged:
0
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 14.7K All Categories
- 648 General Development
- 171 AMA
- 1.3K Answers
- 77 Developer Dashboard
- 408 Store Submissions
- 492 Oculus Quest Development
- 3.8K Oculus Rift S/Rift Development
- 1.8K Oculus Go Development
- 3.7K Unity Development
- 970 Unreal Development
- 377 Platform SDK Development
- 345 Audio SDK Development
- 253 Avatars / Social SDK Development
- 15 360 Capture SDK Development
- 24 Developer Tool Feedback
- 378 Game Design
- 501 Collaboration
Comments