menu
 

Community Q&A

Welcome to Audiokinetic’s community-driven Q&A forum. This is the place where Wwise and Strata users help each other out. For direct help from our team, please use the Support Tickets page. To report a bug, use the Bug Report option in the Audiokinetic Launcher. (Note that Bug Reports submitted to the Q&A forum will be rejected. Using our dedicated Bug Report system ensures your report is seen by the right people and has the best chance of being fixed.)

To get the best answers quickly, follow these tips when posting a question:

  • Be Specific: What are you trying to achieve, or what specific issue are you running into?
  • Include Key Details: Include details like your Wwise and game engine versions, operating system, etc.
  • Explain What You've Tried: Let others know what troubleshooting steps you've already taken.
  • Focus on the Facts: Describe the technical facts of your issue. Focusing on the problem helps others find a solution quickly.

0 votes
I am still figuring out the ins and outs of using Wwise + UE4.

 

Looking over the documentation for Occlusion: it seems the only way to enable occlusion is through blueprints. So does that mean I have to create Blueprint nodes for every AKComponent I am using? Or do I only have to set up occlusion for the player on their blueprint?

 

If the latter is the case then fine, but the former seems really time consuming and bloated. And how would AkAmbientSounds get occlusion enabled if the former is the case?
in General Discussion by Jack M. (430 points)

1 Answer

+1 vote
 
Best answer

This is actually going to change in the 4.7 integration. We've exposed the AkComponent directly on the AkAmbient, and as a result, the occlusion refresh interval shows up it its details panel (see image)

The same options will be available when you add an AkComponent to a blueprint, too.

by Benoit S. (Audiokinetic) (16.0k points)
selected by Jack M.
Cool! So to clarify for current implementation: the set Occlusion Interval does indeed need to be on each AKactor and *not* on the player/listener?

What is the ETA for 4.7 integration?
Yes, occlusion is set on AkComponents, not on the listener.

It usually takes us two weeks to get a new integration out.
And one more Q: How do I enable occlusion on sounds that are spawned at runtime or sounds on other players in a level? Do those have to be set up on a per object/component basis in a Blueprint?
Yes, you'll need to get the AkComponent, and then set the Occlusion refresh interval on them. However, the default value for the Occlusion refresh interval is 0.2, so the feature is on by default.
I keep getting confused!

So the refresh is on by default, or Occlusion is on be default? (I would prefer the latter)
Both. There is no switch for occlusion; everything is controlled by the refresh interval. If the interval is set to 0, occlusion is turned off for this AkComponent. Setting it to a non-zero value will enable the occlusion feature.
Hey, apologies for digging up an old thread (and hijacking it!) but it looks like in UE4.27 and Wwise 2021.1.10.7883 the Occlusion Refresh Interval is set to 0 as default. Is there somewhere in the settings that I can change this to a different value so that all sounds adhere to a new value by default?

Thanks
...