Creating a package with a sound inside of it which is linked to a soundgroup will work fine, but when it’s transferred to another place for use, I have to re-link the soundgroup in that place too, even if it uses the same name. Changing the soundgroup, will prompt the package for modification, but it has no effect on other instances when published.
System information: Windows 11, 13th Gen Intel Core i9-13900K, 64GB memory, NVIDIA geforce RTX 3080
Enrolled in all beta features
Expected behavior
I expect to be able to simply drop in the package and have it’s sounds link to its related soundgroups.