Hi, we’re currently working on a multiplayer game and are looking for the most efficient and optimal way of organizing and calling events so that they can be routed to the right buses, as well as managing instance limitations and priorities depending on the entity playing it.
For the moment we’ve decided to organise the project as follows:
1/ We have a Parameter sheet in an event, in which we will select the variation of the event to be played according to the entity playing it using a command instrument.
3/ The NPC and ALLY events contain an Event Instrument that plays the PlayableCharacter event. As this instrument is in another event, it will be routed on its own bus and will have its concurrency parameter. This allows us to manage the volume and assets of all events simultaneously using a single event.
The question is: is this the most optimized and simple system for managing this kind of situation, or can we use code to re-routing sounds and apply different characteristics to them depending on a parameter?
Because we have a lot of events to manage, it’s quite time-consuming to maintain systems with so many events for a single sound.
Yes. This is the simplest and most performant way of doing this.
Technically there’s no way to change the routing destination of a bus at runtime, but you can achieve a very similar effect by automating the values of sends on a parameter, such that setting the parameter to different values changes which sends’ levels are audible and which are silent.
Hello, thank you for your previous reply, it was very helpful.
We have decided to use the return buses and parameters to solve this issue. Because it’s much easier to manage with shareset, etc..
However, a new question came to mind:
As we can not set an instance limitation to the return bus, if we place this return bus in a group bus, does it also apply the instance limitation of the group bus to the return bus?
Also, it would be very useful to be able to see the number of instances/voice per bus in the profiler (group and return if possible), and not only the master or the event. Maybe in a future update?
No. As of the time of writing (June of 2025), signals sent by sends to a return bus do not count towards the number of event instances routed into a group bus downstream of that return bus.
I can see how it might be useful for a project that makes use of group bus instance limits, so I’ll add your suggestion to our feature and improvement tracker.
