In order to use the gamepad in Unreal you need to do a couple of things as explained in the Unreal tutorial: https://www.noesisengine.com/docs/Gui.Core.UnrealTutorial.html#gamepad

1. Go to the Level Blueprint and configure the Enhanced Input to use the Noesis Controller config (or any one other actions configuration you want to use).
2. Enable Actions in the View to use them as input.

I've just did that in the Materials sample you mentioned and the gamepad works as expected to move the focus between the buttons and click them. Could you please try that?

Unlike vogelLightword , we are on Unreal 5.3.2. I tried the same Materials sample and also experience the same issue.
On Unreal 5.3, there is no "Add Player Mappable Config" in the Enhanced Input - those have been deprecated (see https://www.noesisengine.com/bugs/view.php?id=2919). So I used "Add Mapping Context" (see attached image)
As we are unable to make it work I thought this was the same issue as reported by vogelLightword but maybe it is different.

gamepad_setup.png (113,138 bytes)   

gamepad_setup.png (113,138 bytes)   

My bad, I forgot the footnote where it says the "Enable Action" in the view blueprint!
It works now.

Can we close this ticket then?

In our code we can't make it work, no matter what we set up (unless we actually modify the KeyToNoesisKey function). We have added an appropriate mapping context and it's added in game, the action (up in this case) does fire but it doesn't navigate up. The view has actions enabled and navigating the buttons with the arrow-keys on keyboard works just fine. As you can see in my attached screenshot, the mapping-context is added, OneNoesisControllerMapping action Up is triggered by the gamepad but it just doesn't navigate to the above buttons (same for navigating down).
Second image shows the view-setup. We add the mapping context via AddMappingContext as well. We also set the keyboard focus on the new widget (where "w" is the new widget):
UWidgetBlueprintLibrary::SetInputMode_GameAndUIEx(this->PCRef, w, EMouseLockMode::LockAlways, false, true);
w->SetKeyboardFocus();
Can you see anything we might be doing wrong/differently; anything I'm missing?

image-2.png (48,065 bytes)   

image-2.png (48,065 bytes)   

Okay managed to find the issue. The path of input-actions that are responded to are hard-coded (inside UNoesisInstance::InitInstance()), we duplicated them and had them in a different folder (so inside the project, not inside the plugins folder). Removing the hard-coding helped.
Another issue that arose from this is that we want to react to the "up"-action (which also refers the up-arrow-key). If we now add the up-arrow to the mappingcontext (for action up) it works fine in that case but now navigation is triggered twice (so instead of moving up one button, we move up two buttons). I attached a screenshot of what I mean. It's a different issue though, navigation now works after we realized the inputAction-paths are hard-coded (might be important for the documentation?). Thanks for the help!

image-3.png (62,462 bytes)   

image-3.png (62,462 bytes)   

that is now fixed as well (not a bug), we had to disable keyboard in the view. Ticket can be closed, thanks!