Search Issue Tracker
Active
Under Consideration for 2021.3.X, 2022.3.X, 6000.0.X, 6000.2.X, 6000.3.X, 6000.4.X
Votes
0
Found in
2021.3.29f1
6000.0.0b11
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
7000.0.0a1
Issue ID
UUM-44585
Regression
Yes
Wwise Unity Integration upgrade fails due to meta files being created in .bundle files
Steps to reproduce:
1. Create a new project in 2021.3.23f1
2. Download Wwise Launcher (Audiokinetic Launcher)
3. Download and install two versions of Wwise (e.g.: latest 2021, latest 2022). Include the SDK package and macOS/Windows deployment platform.
4. Integrate (install) the first/oldest downloaded version of Wwise into the Unity project in the Wwise Launcher
5. Open the Unity project, Wwise should be installed and working
6. Upgrade Wwise for the project in Wwise Launcher to the second/newest downloaded version e.g 2022
7. An error will appear in the Audiokinetic Launcher, and installation will fail
Expected results: Wwise Unity Integration update does not fail due to meta files being created in .bundle files
Actual results: Wwise Unity Integration update fails due to meta files being created in .bundle files
Reproducible in: 2021.3.23f1, 2021.3.29f1
Not reproducible in: 2021.3.22f1, 2022.3.6f1
Could not test on 2023.1.7f1, 2023.2.0b2, 2023.3.0a1 due to Wwise installation failing
Environment tested on: Windows 10
Notes:
-After upgrading Wwise version, the project can be accompanied with Infinite import loop, however, I was not able to reproduce it
-According to the user after installing Wwise 2021 and opening the project notice the missing .meta files on certain .bundle directories, I was unable to reproduce this behavior on Windows 10
-Related forums thread:
[https://forum.unity.com/threads/dylib-bundle-file-not-exporting-to-unity-package.427752/#post-9064171]
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment