OpenXR Suggested Bindings: Not working for "application_menu" on Vive Trackers

[Pascal]

I have a problem with SteamVR/OpenXR suggestedBindings. For Vive-Controllers there is a mismatch between the input-name in SteamVR and the OpenXR-Specification. The menu button is named "menu" in openXR-Specification, but is named "application_menu" in SteamVr.

When I suggest
XrActionSuggestedBinding(MyAction, FOpenXRPath("/user/hand/left/input/menu/click")
it works fine and steamVRs binding will look like this

 
              {
               "inputs" : {
                  "click" : {
                     "output" : "/actions/ue/in/vive_left_menu_click"
                  }
               },
               "mode" : "button",
               "parameters" : {
                  "force_input" : "click"
               },
               "path" : "/user/hand/left/input/application_menu"
              },

so somehow SteamVr seems to reinterpret "menu" as "application_menu" and it is working correct

But when I do the same for vive trackers it will not be translated to the correct path (I am using the pogo pins)
XrActionSuggestedBinding(MyAction, FOpenXRPath("/user/vive_tracker_htcx/role/chest/input/menu/click")

 
            {
               "inputs" : {
                  "click" : {
                     "output" : "/actions/trackers/in/chest-menu"
                  }
               },
               "mode" : "button",
               "parameters" : {
                  "force_input" : "click"
               },
               "path" : "/user/chest/input/menu"
            },

The binding will not work for tracker, unless you change it manually to "application_menu".

Do you think SteamVR developers forgot to make the name translation for the trackers and only did the controller?

I need to get the bindings to work without manual adjustments

Cross Posting:
Vive Developers[forum.htc.com]

[danwillm]

Thanks for spotting. It looks like the mappings to the vive controller interaction profile for the menu button were only added for the controllers, and not the trackers.

We've now applied the mapping to both the tracker and wrist tracker profiles, which should be released in the next beta update.

Let me know if this works for you.