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-Unity Integration Error Message (AkWwiseFirstImportCallback.cs fail)

0 votes
Hi,

I'm trying to install the Wwise-Unity integration but I get the following error message: "Assets/Wwise/Editor/WwiseSetupWizard/AkWwiseFirstImportCallback.cs(30,46): error CS0234: The type or namespace name `GetCommandLineArgs' does not exist in the namespace `Environment'. Are you missing an assembly reference?"

I've followed the exact steps as all tutorials that I can find tell me to, but when I get to the actuall instalation part (when I've selected all assets to import and the screen where I get to choose what Wwise-project to use is supposed to appear) nothing happens and the previously mentioned error message pops up in the console. I have done this integration before with another Wwise project and another Unity project but both being earlier versions of Wwise and Unity. And yes, this is the latest Integration-package available for download from this site.

Any help would be greatly appreciated!

Thanks!!

//Henrik
in General Discussion by Henrik B. (110 points)

1 Answer

0 votes
Do you by any chance have a class or namespace named "Environment" defined in your game? If you do, it will clash with System.Environment and might cause this error.
by Benoit S. (Audiokinetic) (16.0k points)
Powered by Question2Answer
...