We dynamically start and stop our FMOD Audio Components in order to cull a little bit of component tick in a given frame. We’re encountering issues where deactivating and then activating ambient sounds causes their applied ambient settings to be incorrect.
I’ve been able to reproduce the issue with the following simplified setup.
1.) Place an FMODAmbientSound inside an AmbientVolume
2.) Bind Audio Component Start/Stop to a key bind in the level editor.
3.) Start PIE. ‘Stop’ the given audio component
4.) ‘Play’ the given audio component
Expected Results: The same settings have been applied to the sound instance as would have been applied on first autoplay ‘Play’
Actual: After toggling, the interior settings do not match the audio volume in which they reside.
Is this a known issue? It looks like Ambient Sounds are AutoActivate by default, was this intentional? Should we not be mucking with that default setting?