menu
버전
2015.1.9.5624
2024.1.6.8842
2023.1.14.8770
2025.1.0.8897
2022.1.19.8584
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
menu
2024.1.6.8842
2023.1.14.8770
2025.1.0.8897
2022.1.19.8584
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 enters in conflicts 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 arise, 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:
Re-order 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 conflicts. |
프로젝트를 등록하세요. 아무런 조건이나 의무 사항 없이 빠른 시작을 도와드리겠습니다.
Wwise를 시작해 보세요