社区问答

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

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

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

0 投票
We use Perforce with Wwise here at Insomniac, but recently we've had a couple of issues where a sound designer is making edits locally, and in the meantime another sound designer makes edits to the same work unit and submits them to Perforce. When the first sound designer is finally satisfied, they check out their now-outdated work unit and have to resolve against the most recent version to submit to perforce, sometimes letting Perforce auto-resolve and corrupting the Work Unit, rendering the entire WPROJ unopenable by the rest of the team.

While the P4V client can be configured to prevent users from checking out outdated files, there doesn't seem to be any way to do this for all checkouts or for all files in a specific folder at the server level. So, I think the best solution would be if Wwise itself prevented designers from checking out outdated files, or helped them to sync up before checking out so they don't potentially lose a lot of work,

And yes, it's true that their workflow should also change to check things out before editing them, but both times we ran into this were (of course) right near deadlines where people are paying the least attention to process and discipline.

In summary, I would like it if the Perforce integration in Wwise did one or all of the below:

1) Flat-out refuse to check out outdated work units--force designers to adopt a checkout-then-edit workflow.

2) Require sound designers to check out a work unit as soon as they start making changes to its contents

3) Offer an option at the project level to do (1) and/or (2)

4) Automatically sync an outdated work unit and smartly apply the designer's local changes, ideally walking them through conflicting properties and getting them to manually merge them, but aborting when there are conflicts is likely fine.

We have mysteriously lost work at a distance to this behavior, and it will likely only increase as our games get bigger.

I appreciate the help,

-Vitor
分类:Feature Requests | 用户: Vitor M. (180 分)

Please sign-in or register to answer this question.

...