社区问答

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

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

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

0 投票

I, just like a few others, am struggling to open Wwise from the launcher. I have the latest Launcher installed along with Wwise 2022.1.6.8263

Mac Specs:

  • 2021 Macbook Pro
  • Apple M1 Pro Chip
  • Ventura 13.5 macOS


Troubleshooting Steps I Have Tried

  • Uninstalling and re-installing both the Launcher and the Wwise software.
  • Restarting my computer both before and after re-installing.
  • Deleting all instances of Wine preloader before re-launching Wwise
  • There is no hidden Wwise2019 file to delete inside of Application Support directory

I waited about 20 minutes after trying to launch Wwise after following the "proper" steps and it still has not fully opened. I am pretty much at my wits end trying to solve this issue. 
It seems like the newer OS has also caused other people in the gaming community issues with Wine as the process has been messed with on Mac's side of things. I am no developer though. Will this get fixed soon? Is there an earlier version of Wwise that still works?

Thank you!

Tyrus

分类:General Discussion | 用户: Tyrus T. (110 分)

1个回答

+1 投票

You are correct in your assessment: the issue affects macOS Ventura 13.4+ on Apple Silicon and is due to a change with the Rosetta 2 emulator layer, and the fix is on the Wine side.
As such, this affects all versions of the Wwise Authoring application at the moment.

I'm glad to report that the fix for this issue is currently being tested and will be part of the upcoming patch version of Wwise, which is 2022.1.7, and is scheduled for next week.
Update: I'm glad to report that the fix has been released as part of 2022.1.7!

用户: Samuel L. (Audiokinetic) (23.6k 分)
修改于 用户:Samuel L. (Audiokinetic)
This is exciting news, I’m looking forward to the patch, thank you for the response!
Any plans on bringing this fix to 2021.1?
@Simon P.: Yes, this fix will be part of the next 2021.1 patch release.
Glad to hear that!
...