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.

Occlusion and Obstruction - Creating your own system or not?

0 votes
So, I am looking into occlusion and obstruction behaviour and want to understand more about it. I know that Wwise has its own occlusion and obstruction system which seem pretty comprehensive and ready-to-use. But, I also came over this video:

https://youtu.be/1uNjiSCTX1o

He basically makes his own occlusion and obstruction system in Ue4 with Wwise, using splines in the game engine.

My question in general is why is it beneficial to create your own system like this instead of using obstruction and occlusion with game-defined auxiliary sends?  Or is it beneficial? What are the pros and cons of making your own systems like this, and what are the pros and cons of the built in system in Wwise? What can this system do that Wwise can not?
in General Discussion by Alexander O. (120 points)

Please sign-in or register to answer this question.

Powered by Question2Answer
...