Feature Request: Allow Multiple Radial Menu Layers Instead of Just One
Having only a single radial menu layer is far too limiting. I would like to request the ability to configure multiple radial menu layer at the same time.
For example: creating multiple radial menu layer and organizing them by functional category — radial menu layer 1 could be themed as a Weapons Menu, and radial menu layer 2 as a Medic Menu.
This way, you wouldn't have to cram all functions into a single radial menu , which quickly becomes cluttered and cumbersome.
Additionally, allowing multiple Radial Menu Layers to be set simultaneously would resolve a logical conflict that arises when two different layers share the same radial menu layer — specifically, the issue of being returned to the wrong layer upon exit.
For example: both Layer 1 and Layer 3 have a function bound to hold LB to switch to the Radial Menu Layer. However, when I try to open the Radial Menu Layer while on Layer 3, releasing LB always returns me to Layer 1 instead of Layer 3.
This is because within the radial menu layer, the Shift Mode on LB release can only be bound to a single layer — either Jump to Layer 1 or Jump to Layer 2 — which creates a conflict during use.
If two separate Radial Menu Layers could be configured simultaneously — one exclusively for Layer 1 and one exclusively for Layer 2 — this issue would be completely avoided.
All of the issues described above are ones I have encountered through actual use. I strongly believe that support for multiple radial menu layer is a necessary and important improvement. As shown in the images below
For example: creating multiple radial menu layer and organizing them by functional category — radial menu layer 1 could be themed as a Weapons Menu, and radial menu layer 2 as a Medic Menu.
This way, you wouldn't have to cram all functions into a single radial menu , which quickly becomes cluttered and cumbersome.
Additionally, allowing multiple Radial Menu Layers to be set simultaneously would resolve a logical conflict that arises when two different layers share the same radial menu layer — specifically, the issue of being returned to the wrong layer upon exit.
For example: both Layer 1 and Layer 3 have a function bound to hold LB to switch to the Radial Menu Layer. However, when I try to open the Radial Menu Layer while on Layer 3, releasing LB always returns me to Layer 1 instead of Layer 3.
This is because within the radial menu layer, the Shift Mode on LB release can only be bound to a single layer — either Jump to Layer 1 or Jump to Layer 2 — which creates a conflict during use.
If two separate Radial Menu Layers could be configured simultaneously — one exclusively for Layer 1 and one exclusively for Layer 2 — this issue would be completely avoided.
All of the issues described above are ones I have encountered through actual use. I strongly believe that support for multiple radial menu layer is a necessary and important improvement. As shown in the images below
Attached Files