Profiling in FMOD and GrowBuffer Confusion

[Connor_FMOD]

Hi,

Thank you for all the information.

@JohnGreska

Why am I receiving the growBuffer warning when I am not using that many sounds? Is it a big deal that it does this?

• This warning is telling you that the studio system is receiving more commands than it can currently keep track of. As a result, it is having to expand the command buffer to keep track of everything. That is the growBuffer warning.
• While 53 total events is not a large amount they all could be calling into the Studio system which could be a cause of the warning.
• In the profiler, I would suggest having a look at the API Calls View (FMOD Studio | Profiling - API Calls View) which you can use to check how many Studio calls are being made each frame.

@JohnGreska

Why are ambient sounds like the drying machine are playing even when I am not in audible distance? Is there any way to prevent this to save space?

• An option is the Stop Events Outside Max Distance option in the FMOD Integration settings
  
  This will stop sounds once they are out of their maximum distance, keep in mind they will have to be restarted if you want them to be heard again.
• An alternative option is setting the Max Instances on the Master Bus and setting Stealing to Furthest. This will limit the maximum instances that can be played in total but does solve the issue of having to replay events once coming back into range.

@JohnGreska

Are the sounds at the lake using transmission not set up correctly if, even though only 4 are active, all of them are playing? Is that a problem for memory?

• When you mention “However, even with setting a max instance of 4” is this on the Transiciver event or on the Reciever event? If there is only one Transceiver event with the limitation and lots of Reciever events that limit will never be hit.

Hope this helps!