Terrible UI rounding issue with ScrollingFrames

Bug Reports Engine Bugs
#1

Reproduction Steps
Create a ScreenGui and add a ScrollingFrame with its size set using Scale, e.g. {0.333, 0} {0.333, 0}. If the Scroll bar images aren’t already showing seams, resize the studio window.

Expected Behavior
For there to be no unwanted offset with any pieces of the scroll bar images. There should be no seams.

Actual Behavior
Each piece of the scroll bar sometimes, depending on my window size, is offset by 1 pixel in a random direction.

https://gyazo.com/5c8466f4360144cda9eaf2e9a623841f

Issue Area: Engine
Issue Type: Display
Impact: Moderate
Frequency: Often

4 Likes
#2

This is exactly what happend to me every time, I open my store gui to edit it

Expected Behaviour

image
image1174×536 63.3 KB

Now I close the UI, and later open it, then:
Actual Behaviour

image
image1142×522 49.5 KB

A video showing it:


In this video you can actually see, those gui buttons come back to their size, after moving before moving, it like in random position, and in-game, the gui is in random places

Issue Area: Engine
Issue Type: Display
Impact: Moderate
Frequency: Very Often

1 Like
#3

This is due to UI caching being broken, I’ve already made a bug report about it but nothing ever happened, its almost been a month.

Here’s some info about caching, you can find more on the ScreenGui api.

Caching static UI for performance improvements

A Gui’s appearance is cached until one of the following events occurs:* A descendant is added to the Gui.

  • A descendant is removed from the Gui.
  • A property of a descendant of the Gui changes.
  • A property of the Gui changes.

If any of these events occur, the Gui’s appearance will be recomputed the next frame it gets rendered.

#4

UIroundings are known to not work for ScrollingFrames. Just add an image label then add a UI corner in there and put it behind the Scrolling Frame. If this is what you mean.

#5

Not talking about UICorner. Re-read my post.

#6

@TheSteelEagle this should be fixed, can you verify? Thanks.

#7

I can confirm it is indeed fixed! Thanks!