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.

0 votes
I am writing an effect plugin, which successfully builds to windows and authoring.
However after I have premaked the solution for PS5 and XboxSeriesX it flags error MSB8020 "build tools for v142  cannot be found".
The toolset is definitely installed as other projects dont have this problem.
Similarly to this question https://www.audiokinetic.com/qa/12151/failing-compile-effect-plugin-wwise-windows-visual-studio?show=12151#q12151 , premake console shows that it is running action for 2017 but also for 2019 and 2022. I am using the v160 (VS2019) project, the same as for Authoring and Windows.
Retargeting the project is not available in Visual Studio so at a bit of a loss what to do.

As an aside, I notice that the build target for Xbox is a dll and a lib, the same as the windows build. Is it necessary to build specifically for Xbox or can i simply copy the windows build to the Xbox directory before packaging?
in General Discussion by Jake B. (190 points)
edited by Jake B.
Hello! Have you found an answer to your problem? We're currently stuck on the exact same problem. The other post you pointed at doesn't fix it either.

Please sign-in or register to answer this question.

...