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.

Including Ak Source file paths in Unreal

0 votes
Hi,

i've followed the steps in the integration guide, up to the "initial setup" step. So, i've got a WWise plugin integrated at engine level, and i can compile and run successfully, but i'm not actually doing anything (yet).

Next step, starting to call, from another plugin, that wraps engine-level custom functionalities, to WWise functions. I've got the includes where the plugin is ( \Engine\Plugins\Wwise\Source\AkAudio\ ) ,  so, question 1): how to properly make my other plugin to know the include path(s)? i've already added the AkAudio module dependency in the .cs file

PublicDependencyModuleNames.AddRange(new string[] {    ..   "AkAudio",     .. });

but i know i have to add here also the paths, what's the correct way? After doing this, will i need to do more?

Question 2): forcing in-code explicit include paths (e.g. ../../../../WWise/Source/AkAudio/Public/AkInclude.h ) i still get some compile errors, in AkInclude.h (syntax error: identifier 'FEditorViewportClient') but opening it i get to the default install path of WWise (in my case, S:\WWise\Source\ etc..) and not the in-engine copied plugin source. Is this an intellisense pitfall or a real issue due to something else? I tend to believe the second option, because it should know about the "correct" include path and not this other one.

thanks a lot in advance,

kind regards,

Michele.
in General Discussion by Michele C. (140 points)

Please sign-in or register to answer this question.

Powered by Question2Answer
...