Please select what you are reporting on:
Verse
What Type of Bug are you experiencing?
UI/Tools
Summary
There are two separate console compatibility issues I’ve found when building UI via Verse. I’ve only confirmed this on PS5, but assume it’s happening on Xbox as well.
-
When using the “button” widget (not “button_loud”, “button_quiet” or "button_regular), there is no visual indicator that an element is selected.
-
When a button (including “button_loud”, “button_quiet”, “button_regular”) is disabled in verse while it’s currently selected, but not clicked by the player, the players ability to navigate to other enabled buttons breaks
Steps to Reproduce
- Visual indicator issue:
Wrap any widget with the following and try to render it in the UI. Observe that there is no visual indicator to console users that the button is selected.
ButtonWidget : button = button:
Slot := button_slot:
Padding := margin{Top := 0.0, Left := 0.0, Right := 0.0, Bottom := 0.0}
Widget := AnyWidget
- Disabling button issue:
On a console, hover over a menu created in verse that has a button which can be disabled in code. Hover over the button and have some type of action disabling that button using:
YourButton.SetEnabled(false)
Expected Result
-
There should be some kind of visual indicator an intractable element in the UI is selected
-
Players should be able to freely navigate after a button they have selected is disabled
Observed Result
- There is no visual indicator. Here’s an example of what it would look like on console even if any of the weapons have been selected. On PC you’re able to freely interact with the entire images which is okay since you don’t really need to show a visual indicator. The buttons still work on consoles even though you don’t know what’s selected.
- Players are unable to navigate when a button is disabled
Platform(s)
PS5 confirmed, other consoles unknown