Question 2022 Performance - FMOD Audibility Computation

Hi all,

Since the 2022 LTS was released, I've been doing a test upgrade of our project. Our project used to run with a framerate in the hundreds (2021 LTS) but is now in the teens (any 2022 version). Running the profiler, shows that the majority of this is in the Audio.FMODSystemUpdate > Audibility computation.



Our project has a rather large number of AudioSources (2K+) added at startup/runtime from about 400 AudioClips, but very few, if any, are playing at any given time. In fact, I had zero playing and performance was still abysmal. In any case, 2021 was fine...

Does anyone know what changed in the 2022 versions that could cause this? General thoughts/comments welcome as well...

Thanks!

 

Also interested in this issue

 

+1 What's going on here?

 

Make a bug report with both 2021 and 2022 versions attatched so it can be fixed

 

I wasn't sure if this was actually a bug or something we simply missed, so I wanted to gather more info first.

Found a workaround... disabling all AudioSources then re-enabling them all seems to address our issues, at least initially at startup (I'd expect actually playing a large number of sounds would eventually reduce performance).

It does seem like a bug since simply disabling/enabling AudioSource corrects, will work on another bug report *sigh*...

Aside from not playing, does anyone know what disabling does?

 

Same issue here. Its only about 2ms for me but still significant issue.

 

For those curious, this was categorized as a regression, but "by design"...
https://issuetracker.unity3d.com/issues/performance-drops-when-using-a-lot-of-audio-sources

Though I'm not sure my report got transcribed correctly between bug report and issue ticket. i.e. you don't have to be playing any of the sounds to lose performance and various cases that have AudioSources in the same state result in some working and some not...

• AudioSources attached/enabled to scene before playing = ok
• AudioSources attached/enabled in "Start" = bad
• AudioSources attached/enabled in "Start" then toggle disabled/enabled = ok
  
• Regardless of how attached, playing an AudioSource (that completes and doesn't loop) = incrementally bad (leaks performance)

 

Did they say why unused AudioSources were designed to be a slowdown?

I'm doing much the same as you, huge pools of AudioSources.