Gamepad doesn't scroll ScrollingFrame

In my game, I have a vertical ScrollingFrame that contains x number of horizontal ScrollingFrames. Currently you can only navigate the items that are currently visible. When you reach the end of the visible items, it will not automatically scroll the ScrollingFrame down to see more items. Using the right thumbstick will scroll down, but it is very slow and only works about half the time.

It is expected that the ScrollingFrame should move down to reveal more content instead of just stopping and doing nothing.

The problem can be seen in this game

1 Like

Hi there! This is likely due to an error with our visibility calculation with nested scrolling frames. I’ve created a ticket and I’ll let you know when we’ve got a fix.

5 Likes

Hi there! I don’t seem to be easily reproducing this issue. Is this still an issue and can you provide a repro file? Or let me know how to get to that page in Simply Minigolf?

scrolling-frame-repro.rbxl (53.4 KB)

I am experiencing the same problem as OP, not sure if it’s caused by the same issue but this is what I found: when a ScrollingFrame has ClipsDescendants = false and is inside of a frame with ClipsDescendants = true it will fail to scroll down.

I’ve created a repro in the place you provided. If you switch the ClipsDescendants of the container frame and scrollingframe it will work fine.
scrolling-frame-repro.rbxl (53.9 KB)

For context, my games UI style utilizes a smaller scrolling frame than the container/background frame so that I can control the top/bottom padding of the scrollbar. Thus the container has ClipsDescendants on rather than the scrolling frame to prevent the bar of empty space you see here:

Thanks for the detailed repro! I’ve got a fix coming out you should see in ~2 weeks.

2 Likes

Sorry about the delay. Fix should be out now. Please let me know if you see any more issues!

1 Like

Same problem here. Still does not work for me. Is there perhaps a way to get gamepad Thumbstick1 direction to create a workaround?

Edit: I’ve found a workaround using ContextActionService.