Community Q&A

Welcome to Audiokinetic’s community-driven Q&A forum. This is the place where Wwise and Strata users help each other out. For direct help from our team, please use the Support Tickets page. To report a bug, use the Bug Report option in the Audiokinetic Launcher. (Note that Bug Reports submitted to the Q&A forum will be rejected. Using our dedicated Bug Report system ensures your report is seen by the right people and has the best chance of being fixed.)

To get the best answers quickly, follow these tips when posting a question:

  • Be Specific: What are you trying to achieve, or what specific issue are you running into?
  • Include Key Details: Include details like your Wwise and game engine versions, operating system, etc.
  • Explain What You've Tried: Let others know what troubleshooting steps you've already taken.
  • Focus on the Facts: Describe the technical facts of your issue. Focusing on the problem helps others find a solution quickly.

Wwise Forgetting Perforce Settings (and Launcher forgetting recent projects)

0 votes
Recently got Perforce integrated in a new Wwise project, however we've been noticing that every time we launch wwise, it's forgotten that it should connect by perforce and we have to go in and set it up every time. This is happening both on a Windows machine, and on a mac running the Windows version through Parallels (as Perforce integration doesn't work on the mac version at all).

Can anyone help with this, as it's a pain in the arse.

Also incedentally noticing that the Wwise launcher never seems to remember my recent project when I open it, although it goes straight to the right location when I go to open a new one. Not a huge deal, but thought I should mention it in case it's related.
in General Discussion by Jeremy C. (100 points)

1 Answer

+1 vote
Hi Jeremy,

At first sight, it sounds like your project's user settings file ".wsettings" might be set as read only, which would explain why your settings are forgotten every time you launch Wwise.

You can locate the .wsettings file right next to your .wproj file and make sure it is not set as read only.

Also, make sure this file is not added to your perforce depot since perforce will automatically add the read only flag when the file is not checked out.

Hope this helps
by Martin S. (590 points)
Powered by Question2Answer
...