社区问答

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

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

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

0 投票
Hi

On a couple of games we have found that the AkComponent.cpp ObstructionService causes terrible performance across all platforms due to massive amounts of raycasts (FAsyncTraceTask goes mad)

Changing the raycast settings etc, even "disabling" occlusion in the wwise settings in UE4 does not fix or alleviate the performance issue

The only way to fix the performance issues is by hardcoding the OcclusionRefreshInterval to 0.0 so it skips it entirely

Is this a known issue? Any suggestions?

Thanks

Rich
分类:General Discussion | 用户: Richard Y. (100 分)
Hello. Could you tell me how did you solve this problem?

1个回答

0 投票
Hi Rich,

First, a clarification. The Unreal Wwise Integration casts rays using the unreal physics engine to drive the occlusion API in Wwise.  The sound engine is then presented with the results (a number between 0-1, indicating how occluded a sound is). The ObstructionService on the Unreal side is generally seperate from Wwise Spatial Audio. This system predates Spatial Audio diffraction, and is generally (at least without a bit of hacking) not compatible with the diffraction system.

If you are looking to get better performance out of the ray casts in unreal, it might be best to do a bit of digging into the Unreal docs (or maybe someone more knowledgeable in this area can chime in). I suspect it would start with reviewing your collision channels, and the complexity of the collision geometry.

The only control in the Wwise Integration is OcclusionRefreshInterval, which can be set to a larger number to reduce the frequency of the ray casts.

Hope that helps,

Nate
用户: Nathan H. (840 分)
...