Audiokinetic's Community Q&A is the forum where users can ask and answer questions within the Wwise and Strata communities. If you would like to get an answer from Audiokinetic's Technical support team, make sure you use the Support Tickets page.

Can't write bank file "__" for language "SFX"

+2 votes

I am working on a student project using Wwise with Unity and Perforce for version control. I was finally able to troubleshoot the integration successfully between Unity and Wwise, was able to generate a soundbank with a header attached, and got Unity to find and display this information in the Wwise picker. After I submitted my changes to my Perforce depot, I tried to add another sound to the soundbank I created. I had no problems with Wwise itself until now, I added the play event to the soundbank as I did with my first sound/event, but when I attempted to generate the soundbank it completed with the error Can't write bank file "ZombieGrunts" for language "SFX". I feel as though I am missing a very simple step that would cause these programs to communicate easily. I also get two errors stating "Can't write SoundBank into file", (With one pointing to my project folder " \GeneratedSoundBanks\Windows\Soundbanks.info.xml " and the other pointing to "\GeneratedSoundBanks\Windows\PluginInfo.xml") and one error stating "Can't write Wwise_IDs.h file". Any idea why these errors might be occurring?  Is there a more simple way of adding to an existing soundbank and having it appear in my project? Any help would be greatly appreciated!!

**Edit
Also, when I go to save the project after importing the sound > Adding play event > Adding event to soundbank, I get an error popup stating
-C:\Users\Andrew\.....\Deadweight\Assets\DeadweightWwiseProject\Deadweight\Actor-mixer Hierarchy\Default Work Unit.wwu: An error occurred while saving this file. You do not have permission to access this file, or it may be read only.
-C:\Users\Andrew\.....\Deadweight\Assets\DeadweightWwiseProject\Deadweight\Events\Default Work Unit.wwu: An error occurred while saving this file. You do not have permission to access this file, or it may be read-only.
-C:\Users\Andrew\.....\Deadweight\Assets\DeadweightWwiseProject\Deadweight\SoundBanks\Default Work Unity.wwu: An error occurred while saving this file. You do not have permission to access this file, or it may be read-only.


I am very new to Wwise, Unity AND Perforce so it could really be any number of issues causing this error. Again, if anyone has any hints/ideas/tutorials that could possibly resolve this issue, I'd love to try them!
Also, I apologize if this is a double post. I think I might have accidentally submitted a blank question form previously.

**FIXED**
So I realized that the error was being caused by Perforce. Because I had edited files that I was trying to save, I needed to "Check-out" those files before saving the project and writing to those locations locally. I hope if anyone else comes across this problem in the future they will find this post!

Best,
Andrew Robards

asked Feb 25, 2015 in General Discussion by Andrew R. (190 points)
edited Mar 8, 2015 by Andrew R.
Is the destination folder for the project anywhere in c:\program files\ or program files(x86)? Those folders often have problems with write protection in windows 7.

Edit: nevermind I just noticed they're in your user folder....
Hi,

Your fix makes sense, but since Wwise has Perforce Integration and offers to check out the required files when making changes to the project, I'm surprised that generating SoundBanks just dies when the files are not checked out.

Is this something that can be fixed by making changes to the C++ plug-in source?

1 Answer

0 votes
 
Best answer

**FIXED**
So I realized that the error was being caused by Perforce. Because I had edited files that I was trying to save, I needed to "Check-out" those files before saving the project and writing to those locations locally. I hope if anyone else comes across this problem in the future they will find this post!

answered Mar 8, 2015 by Andrew R. (190 points)
selected Mar 9, 2015 by Fabien B. (Audiokinetic)
I have this issue when trying to generate any file into any soundbank. I recently did a file purge with the file manager. I don't know if that is related.
My files are checked out so i don't think your solution is mine.
Do you have any other insights?
Did you manage to solve the issue?
...