Experienced a similar issue. Some audios were being loaded but all audio TimeLengths were set to 0 (this only happened in-game and not in Studio). This impacted an audio playlist, as something like wait(audio.TimeLength) before continuing would now just skip the audio.
Players in my game are also experiencing no audio despite using new audios owned by the same entity as the game. Very frustrating that we were given this shake up only for it to break in the first place.
It’s assuring at least that we did the right thing and are just waiting for a fix.
I’m also still having this problem. I’ve tried setting the permissions through the website and by clicking on the error message, and while the website says that the experience has access to the asset, the same error pops in the console and the sound doesn’t play.
My game used a footstep sound module, most if not all sounds fail to load, werent those supposed to stay usable if below the 6s mark? The plugin showed everything with a blue check. But now i keep getting the “Universe doesnt have permissions for Sound Asset…” error message.
This bug is becoming increasingly CRITICAL to fix; the audio to my game is crucial to adding to the atmosphere and I’ve been getting endless comments about certain maps music not loading. I’ve actually noticed a dip in players because of this bug.
The longer this bug lasts, the longer my experience (and therefore revenue) is interrupted.
I’ve made my audience aware but it not a great feeling having to be the bearer of bad news for something I had already prepared for.
Oh hey, other people are experiencing this too?
This weird bug is getting pretty annoying, but I do have my experience to share too.
I am making a baseball bat weapon for my game and I only started experiencing this issue when I uploaded the sound of the baseball bat being swung. (see below)
And about the supposed patch of the bug that was announced by the staff, it was kind of fixed as you can still hear the sounds ingame rather than studio (probably just a me thing)
Anyways, just tried to share my own experience with this bug. Hope it gets fixed soon!