menu
 

在 Audiokinetic 社区问答论坛上,用户可对 Wwise 和 Strata 相关问题进行提问和解答。如需从 Audiokinetic 技术支持团队获取答复,请务必使用技术支持申请单页面。

+3 投票

Hello,

When I'm Built in Unity I have this Error :

IOException: Sharing violation on path D:\Projets Unity\Blablabla\Assets\StreamingAssets\Audio\GeneratedSoundBanks\Windows\DecodedBanks.meta" or "D:\Projets Unity\Blablabla\Assets\StreamingAssets\Audio\GeneratedSoundBanks\Windows\DecodedBanks.meta

I searched but I can not find a useful answer to this problem.
So, it's impossible to built.

Any ideas ?

Thank you,

Theophile Demarcq

分类:General Discussion | 用户: Théophile Demarcq (1.9k 分)

2 个回答

0 投票
 
已采纳

I also have the same issue, using Wwise 2019.1.4 - Unity 2019.2.9f1

I think it's related to the fact that both, source and destination paths for banks generation are the same (StreamingAssets/Audio/[PlatformName])

I made a quick fix to solve this issue, within the AKBuildPostProcessor.cs file, but it's not ideal.

Check this PasteBin: https://pastebin.com/DKzeb5x6

用户: Raúl Emmanuel I. (820 分)
采纳于 用户:Théophile Demarcq
+1 投票

Ok, we had the same problem today, and the other answer here isn't really the solution...

This exception happens because the SoundBanks path(s) inside Wwise is set to the StreamingAssets folder inside Unity, which is where they get copied on build.

So I discovered two things which are not very clear from the docs:

  • SoundBanks path(s) inside Wwise can be outside the Unity project (even better because this way the Unity Editor doesn't have to track unnecessary files), and all the sounds still work in the Editor.
  • SoundBanks path(s) inside Wwise should be outside of Unity's StreamingAssets folder if you have checked the option in Unity Project Settings > Wwise Editor > Asset Management > Copy SoundBanks at pre-Build step, because this way Wwise copies the SBs from the generation folder to the StreamingAssets, and it only copies the necessary platform, which is being built, so in this case the two folders are the same so the exception is thrown.
用户: Xriuk (250 分)
This is the solution. We were having the exact same problem and your post gave us clarity as to the root of the issue as well as pointing to the solution - many thanks!
...