Avatar Context Menu sinks DPadUp even when a GuiObject is selected

[tbradm]

I posted this on a thread directly about the Avatar Context Menu, but received no response. I am reposting here as a bug report to try to get this updated. Proposed solution is included.

@tbradm

When enabling the Avatar Context Menu, it binds the open menu action to the Gamepad button DPadUp. This sinks all DPadUp presses and attempts to open or close the menu. This is fine except when the player is utilizing the Gui Selection/Navigation system.

DPadUp will not be able to control navigation as long as Avatar Context Menu is enabled. If the player isn’t near another player, nothing will happen. If they are, the menu will appear (possibly on top of what they are navigating). LeftThumbstick still works for navigation, but the user may not know this, and (especially if they are not near another player) may become confused or frustrated with the Gui interface they are attempting to navigate.

A simple fix would be to add the following code to gamepadOpenMenu :

if GuiService.SelectedObject ~= nil then
	return Enum.ContextActionResult.Pass
end

[tbradm]

Who do I have to tag to get this change made? The fix is as simple as adding the three lines of code provided above to CoreScripts/AvatarContextMenu.lua in the function gamepadOpenMenu (the last function in the script).

[TheGamer101]

Sorry for the late response, I didn’t see this thread until now. We will get this fixed ASAP.

[Club_Moo]

Hi. I’d like to mention that you don’t actually have to pre-enable the ACM to make it work, as enabling it
binds the DPadUp (and previously the B key) ie. you can use your own keybinding and when you get
your key, only then do you enable and open the ACM. Then you can immediately disable it
And amazingly the ACM, once it is opened (displaying) will still work even though it has immediately been disabled. This is not only a workaround for GUI nav, but also if your game uses DPadUp for something else.