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.

Perforce settings are not properly parsed in Wwise

0 votes
We use a perforce p4port that is of the form ssl:ww.xx.yy.zz:ports

Wwise seems to incorrectly parse this form of p4port and we have to change the perforce settings every time we open wwise.  The setting gets stored in the wsettings file correctly,  but upon opening wwise, the perforce settings are hosed:

<Property Name="General\Source Control\Perforce\Version 1\P4Server" Type="string" Value="ssl:ww.xx.yy.zzz"/>

When opening the perforce settings in Wwise, I see:

Server:     ssl

Port:  ww (the same ww as above).

The problem seems to be that wwise is parsing for the : and assuming that everything after is the port and not accounting for the fact that ssl: is a valid prefix to a perforce port.
related to an answer for: Wwise Forgetting Perforce Settings (and Launcher forgetting recent projects)
in General Discussion by Mark A. (130 points)

Please sign-in or register to answer this question.

Powered by Question2Answer
...