I’ve run across a strange issue where I’m unable to add audio componants such as Metasounds to variables within the level Blueprint. Now I’ve seen som results before discussing it being a bug.
But here’s the even stranger part, I AM able add any audio object as long as it’s in the Start Content/Audio folder.
Why is that? I’m using 5.4.1 and this usually doesn’t happen. ONly with the LevelBlueprint. But it is still frustrating.
If it didn’t work at all, that’d be one thing, but the fact that the stuff in Starter Content works is just strange.
Hey there @ViRiX! How is it failing? When attempting to add the sound does the engine crash or are you just unable to find the sound listed? Are they the same sound format? Can the sound variables be changed inside of a Set node?
Ah, sorry. So the problem is that I can’t add the sound to the variable within the LevelBlueprint. So I’ll click on the menu to add a sound to the variable, I search and find it, click on it, and it will still say “None”.
I thought I just couldn’t add sounds that way, but I was able to add sounds that were located in Starter Content/Audio’s root. Subfolders under the audio folder don’t get accepted either.
Clicking the Asset Browser Selection arrow doesn’t work as well.
The formats are the same as far as I can tell. 44.1K wave files. Stereo or mono, doesn’t matter.
The only time this works is in the start content/Audio folder.
So I’m wondering what’s different about that folder.
As a last resort, I moved my sounds to the Audio folder and they worked! I’d rather not have to do that in the future though.
This is an interesting error! I’m currently installing a fresh 5.4.1 instance to verify reproduction steps on my side assuming this is a bug introduced in 5.4.1. Since this only affects the LevelBlueprint, can the reference be assigned outside of the LevelBP? (Not meant to be a workaround, but can help determine where the fault is).
Both sound waves and cues are able to be referenced from their respective types in the level blueprint. Does this occur on all level blueprints or just your main scene?
Thanks for getting back with me! That’s definitely one workaround! Though I can’t reproduce the issue, I’d recommend submitting a bug report in case there’s data on it for the team to work with:
