Audiokinetic's Community Q&A is the forum where users can ask and answer questions within the Wwise and Strata communities. If you would like to get an answer from Audiokinetic's Technical support team, make sure you use the Support Tickets page.

Windows_vc170 not detected in UE5 Project integration

+1 vote

 

Hi! This is my first post here and I am looking for help.

I am trying to use the existing Windows_vc170 in "C:\Program Files (x86)\Audiokinetic\Wwise 2022.1.0.8070\SDK" in our project, but it isn't being detected. What can I do to get it integrated? Manually copying the folder doesn't seem to work because I am getting some issues while cooking.

The Wwise Unreal Engine integration supports Windows, Mac, Linux, XboxOne, PS4, Stadia, Switch, Android, iOS, tvOS, PS5 and UWP. The "include", "Win32_vc150", "x64_vc150", "Win32_vc160", "x64_vc160" and "Mac" folders are mandatory. The Wwise SDK for these platforms will be copied for each one detected, including any installed plug-in.

The following platforms were detected:

  • Mac
  • Windows_vc150
  • Windows_vc160
  • WinGC
  • UWP_vc150
  • UWP_vc160
  • UWP_vc170
asked Nov 30, 2022 in General Discussion by Danilo G. (110 points)
Any thoughts on this? I am running into the same issue.

I was able to work around the issue by manually copying the x64_vc170 sdk folder into the plugin but that doesn't seem ideal.
My Wwise install of 2022.1.4.8202 seems to be missing the _vc170 folders entirely. Is thre a reason why this may be the case? I believe it is necessary for my current project in Unreal 5.1

2 Answers

0 votes
Hey, I had the same issue and was able to go through by updating my Wwise Launcher. Just downloaded it from Ak website. Hope it works for you. Cheers.
answered Aug 6, 2023 by Vincent D. (140 points)
0 votes

I had the same issue with the 2022.1.8 8316 version and Unreal 5.2.1, I was missing the Visual Studio 2022 Checkbox.

To fix it open the WWise launcher, go to "WWise -> Wrench Icon -> Modify -> Deployement Platforms -> Microsoft -> Windows -> Visual Studio 2022", I also had to check "Visual Studio 2022" in "Universal Windows Platform" to fix  "_vc160 is missing"

 

answered Oct 26, 2023 by Marco Patrignani (150 points)
...