menu
Version
2021.1.14.8108
2024.1.4.8780
2023.1.12.8706
2022.1.18.8567
2021.1.14.8108
2019.2.15.7667
2019.1.11.7296
2018.1.11.6987
2017.2.10.6745
2017.1.9.6501
2016.2.6.6153
2015.1.9.5624
2024.1.4.8780
2023.1.12.8706
2022.1.18.8567
2021.1.14.8108
2019.2.15.7667
2019.1.11.7296
2018.1.11.6987
2017.2.10.6745
2017.1.9.6501
2016.2.6.6153
2015.1.9.5624
It is possible that multiple active bindings enter in conflict with their Controller Assignments. The Control Surface system does not allow to have multiple bindings with the same key that are loaded simultaneously.
| info | Note |
|---|---|
Bindings from a Control Surface Session are loaded from top to bottom. When a conflict arises, only the first conflicting binding will be loaded. Priority is given to the first binding found. |
When a conflict is found:
A yellow triangle is shown beside the group name in the Wwise toolbar.
A yellow message is shown beside the binding in the Control Surface Session view.
There are multiple ways to handle conflicts:
Reorder the bindings in the Control Surface Session view, to change priority.
Use the shortcut menu on the binding entries to resolve the conflict.
Assign a new controller assignment for one of the conflicting bindings.
| check_circle | Tip |
|---|---|
In some scenarios, it might be useful to assign the same controller assignment to different bindings on the same group. For example, you could create an Effect View Group that binds properties of different effects. Because the Effect Editor can only load one effect at the time, the bindings will never conflict. |
Questions? Problems? Need more info? Contact us, and we can help!
Visit our Support pageRegister your project and we'll help you get started with no strings attached!
Get started with Wwise