社区问答

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

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

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

0 投票
Hello everyone!

We are having an issue where two developers have different paths to their Wwise installation, causing a situation where they are having to constantly change their project settings, invalidating the path of the other developer each other. Is there a solution to this?

Thank you! :)
分类:General Discussion | 用户: Rafael D. (140 分)

1个回答

+1 投票
 
已采纳
My team struggled with this a bit. Very bad design on Audiokinetic's part.

I ended up removing the WwiseSettings.xml file from the repo and adding it to the .gitignore file. I wrote a script so we have one WwiseSettings.xml in a config directory that gets copied into the project by the build machine before it builds soundbanks. All the developers just have to set up the path settings individually.

However, I do want to mention that eventually I ended up including our wwise install in the directory itself so that I could automate building soundbanks on our build machine. I didn't want to do this but Wwise is a pain to install via command line script. So if all your developers are working on windows machines it might be worth it to just have the wwise binary right in your repo.

Not a great solution but there ya go. If anyone has a more clever solution I'd love to hear it.
用户: Cory L. (460 分)
采纳于 用户:Rafael D.
...