Community Q&A

Where Wwise users help each other out!

Audiokinetic's Community Q&A is the forum where Wwise users ask and answer questions within the Wwise community. If you would like to get an answer from Audiokinetic's Technical support team, make sure you use the Support Tickets page.

Support for dynamically moving geometry (not just doors)?

0 votes
Everything moves in my game - huge walls, entire buildings, even the ground.
So far the only dynamic geometry I've seen being demonstrated are binary 'opened/closed' doors. I worry that Wwise needs to bake static geometry offline.

So my question:
Is it possible to - during runtime - arbitrarily spawn and move big geometries, and perhaps create rooms - on the fly, and have Wwise model occlusion and reverb or their approximations?

If not, then what are the limitations?

I have no prior experience with Wwise and I'm contemplating its usage, so any kind of advice on the subject that may seem obvious is still hugely appreciated!
asked Sep 9 in General Discussion by Vioxtar (100 points)

1 Answer

0 votes
Hey Vioxtar,

Yes, it is certainly possible, however, you may also want to consider other methods of simulating the same behavior, instead of having to use processing on constantly updating the entire geometry.
This video may shed some light on that topic - https://youtu.be/OKYEoGcEiYU?t=4664
answered Sep 10 by Mads Maretty S. (Audiokinetic) (15,000 points)
Awesome! Thanks for the answer and the referenced video!
Hey Mads,

While I did manage to get geometry components to update correctly during runtime, I encountered limitations with the UE4 integration. Unfortunately, a lot of AK components (e.g rooms and late reverb components, possibly portals too) rely on a parent that derives from AVolume (that derives from brushes), and brushes cannot be created at runtime as they require the unreal editor modules, which ideally should not be included in a published title. AKGeometryComponents work fine because they don't require AVolume parents.

Given that brushes are only used to obtain geometry data which is passed onto Wwise - this limitation imposes arbitrary constraints which actively prevent runtime spawning + updating of most Wwise game objects.
While I can tackle rewriting that part of the UE4 integration, I'd rather first ask: is AudioKinetic aware of this limitation, and are there known workarounds for this issue?

Thanks!
...