社区问答

欢迎来到 Audiokinetic 社区问答论坛。在此,Wwise 和 Strata 用户可互帮互助。如需我们团队直接提供协助,请前往技术支持申请单页面。若要报告问题,请在 Audiokinetic Launcher 中选择“报告错误”选项(注意,问答论坛并不会接收错误报告)。我们内部设有专门的错误报告系统,会有专人查看报告并设法解决问题。

要想尽快得到满意的解答,请在提问时注意以下几点:

  • 描述尽量具体:比如,想达到什么样的目的,或者具体哪里有问题。
  • 包含关键细节:比如,Wwise 和游戏引擎版本以及所用操作系统等等。
  • 阐明所做努力:阐明自己为了排除故障都采取了哪些措施。
  • 聚焦问题本身:聚焦于问题本身的相关技术细节,以便别人可以快速找到解决方案。

0 投票
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.
分类:General Discussion | 用户: Michele C. (140 分)

Please sign-in or register to answer this question.

...