The max instances property sets a limit on how many instances of this event can play simultaneously.
If your game’s code attempts to play any instance of the event, and that event instance would exceed the number set in the event’s max instances property, FMOD Studio culls or virtualizes event instances according to the event’s stealing property.
Oldest: Stop the event instance that was created the longest time ago.
Quietest: Stop the event instance that is the least audible, taking distance attenuation into consideration.
Virtualize: New event instances will be virtualized, meaning they are created and played but produce no output until an existing event instance stops.
None: No stealing will occur, therefore no new event instances can be played until an existing even instance stops.
Oldest would be most useful if playing the newest event instances were the most important. Perhaps for heavy gunfire? Or any super multiple event occurrence where the oldest one doesn’t matter as much as the newest…
Quietest seems to be most useful for using with distance and attenuation. For example, walking in an area with a long river, you’d only want 5 river sounds playing at a time, not the 100 river sounds that are actually present on the map. This would seemingly smoothly stop the river sounds you wouldn’t want playing. This is the one that seems best for my use, and I’ve used it and it seems to work very well.
Virtualize seems useful, but not sure how yet. It seems that the new audio event would be doing everything except playing until an old one stops. Perhaps useful for a rotating torso changing direction on a robot?
None seems to be most useful for focusing on the stopping of an older event and starting of a new event in its place. The new event only produces sound if the old event stops. Not sure what that would be useful for. Perhaps background 3D positional music sources (like a jukebox in-game?)