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.

0 votes

I am testing out the effort to upgrade Wwise for our project to take advantage of the new workflow. 

When migrating to the new Wwise, every referenced sound asset triggers a delete notification requesting to delete AudiokineticEvent. This of course causes quite a number of assets with sound references to need redirectors cleaned up, causing some checkout conflicts as we are using perforce. Once we fix the redirectors I am assuming there will still be no sound in our project until the sounds are reassigned to the affected assets. I was hoping migration would auto replace the old audio uassets with the new workflow method ones. 

What should I expect after migration is complete? Will our team need to reassign sounds after redirectors are fixed? 

Migrating from Wwise 2019.2.0 with banks -> 2019.2.1 with no banks. 
Unreal Engine 4.24.3

in General Discussion by Justin D. (160 points)

1 Answer

0 votes

I had time to rerun the update. Seems this issue was cause by source control. 

If using source control, enable it in the UE4 editor and close the editor before integrating or migrating this version of Wwise for your UE4 project. Its pretty smooth after that.

First time I attempted the update I didn't have the assets checked out because i didn't know which assets were going to be affected and was prompted to delete the AudiokineticEvents for each sound in our project. I haven't found a way to rerun asset detection with sounds left outside of the new workflow directories due to some assets being locked by other developers. Seems the update is a one shot.  

by Justin D. (160 points)
...