You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the current FMOD integration skips any creation of Fmod event instances/programmer instruments, and lives at the bus level, we miss out on a lot of routing QOL and effects that Fmod is able to provide for events. Things like spatialization data at the event level, and instanced parameters/effects per event would be awesome to be able to access.
There are definitely workarounds, (I'm currently creating a bus for every voice chatter and then adjusting duplicated global parameters to mimic the functionality of instanced event parameters) but it would be a huge QOL improvement.
The text was updated successfully, but these errors were encountered:
This was something we considered during the initial development, but decided against mostly due to the extra complexity involved. I'm also not familiar enough with the higher level functionality to decide how best to integrate with it, so some research would be involved there.
As such this isn't something we're likely to implement soon, but I will leave this issue open as a feature request for the future.
Since the current FMOD integration skips any creation of Fmod event instances/programmer instruments, and lives at the bus level, we miss out on a lot of routing QOL and effects that Fmod is able to provide for events. Things like spatialization data at the event level, and instanced parameters/effects per event would be awesome to be able to access.
There are definitely workarounds, (I'm currently creating a bus for every voice chatter and then adjusting duplicated global parameters to mimic the functionality of instanced event parameters) but it would be a huge QOL improvement.
The text was updated successfully, but these errors were encountered: