AudioLog Warnings spam about missing sound class properties

Development Audio
, , ,
1

Our project is seeing a spam of warnings from LogAudio:

LogAudio: Warning: Unable to find sound class properties for sound class Music

as an example, been trying to figure out what this relates to but there isnt much of a breadcrumb to follow for this warning, there are no associated errors either

2

bumping this

some more context, we have removed all Sound Classes in the project including any references to them and readded them as a test; this resolved the issue locally but open other users committing to the project the warnings have returned;

the amount of warnings has caused issues for many of us as they seem to spam out 1000s of warnings everytime a level load occurs that contains any sound that has an override to any Sound Class

3

Hey @WinegumsAndPlums,
I’m not sure what particularly could be causing this issue, but I know there are a few different ways to change the screen output, and the editor will remember the preferences.
This thread goes into a few ways, I hope one works for you: Disable sreen messages on launch? - #6 by SeanWenham
Let me know how it goes!
-Zen

4

the issue isnt that these console logs are disabled on screen in runtime the issue is that there seems to be some bug that introduces an ONSLAUGHT of console log warnings whenever using Sound Classes (or maybe sound classes in a particular way?) the only solution we can confirm works on our project is to completely remove and not use Sound Classes at all and that seems like a major bug (currently project is 5.1)

5

bump

6

We are having the same issue on our UE5.2 project.
We have enabled logs in shipping builds and one of our clients can reproduce these warnings with ease. It causes some FPS drops, since it’s printing every single frame.
When it occurs it seems like sounds are still able to play normally though.

It is not fully consistent, we have not been able to reproduce this on our local PCs with a build or just in the editor.

We have temporarily increased the log severity of LogAudio to Error, as to not have these warnings, but an actual fix would be preferred.

Any idea why this could be happening or how we could reproduce the issue more easily so we can debug what is happening?