Unable to Map Contextually Sensitive Functions to Shared Button

Default control profiles have multiple instances of context-sensitive functions mapped to a single button.

For example, “Activate” and “Map” are both mapped to the View button. When there is no context of activating anything, the button brings up the map. When their is context for activating something like a race, then the button is used to activate.

This shared button mapping is impossible to configure in a custom controller profile.

  1. Create or modify a custom controller (or wheel) profile.
  2. Choose the ‘Activate’ function, and press A to map it.
  3. Press the View button. ‘Activate’ is now mapped to the view button.
  4. Choose the ‘Map’ function, and press A to map it.
  5. Press the View button. ‘Map’ is now mapped to the view button.
  6. ‘Activate’ has been removed from the View button, and is now unmapped.

Above is just a single example. You really get into the weeds when you try and map Anna’s controls.