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.

Automate detecting deployment platforms and packages

–1 vote
I am able to create an offline installer for wWise by installing everything I want, zipping up the install directory, unzip to my target machine, silently install the launcher, install the prerequisites and set the WWISEROOT and WWISESDK environment variables. I understand I am unable to automate the launcher detecting a local installation and i'm able to get around this by pointing it to the Wwise launcher executable, however none of the packages and deployment platforms are there, even though I had included all of them before zipping up the directory. I thought setting the environment variables would do this, but it appears not. Is there a way to get the launcher to pick these up without having to modify the install?
in Feature Requests by Craig S. (120 points)
recategorized by Samuel L. (Audiokinetic)

1 Answer

–1 vote
The information for what was installed for all Wwise installations on a machine is localized into a single file on the Wwise Launcher side.
Pointing the Wwise Launcher to an existing installation path only informs the Wwise Launcher that a Wwise executable is present at this location, but it cannot infer what was installed.

This is a feature request for moving this information inside individual installation so that they can be portable across machines.
Unfortunately, this is not currently supported, but we are considering going in this direction.
by Samuel L. (Audiokinetic) (23.6k points)
Powered by Question2Answer
...