AutomaticSize is influenced by scaled UI elements

Bug Reports Studio Bugs
,
#1

my issue is explained in the video attached below, please watch it with audio on.

reproduction file
automaticsize issue.rbxl (57.4 KB)

my system:
CPU

AMD Ryzen 7 2700X Eight-Core Processor 

Base speed:	3.70 GHz
Sockets:	1
Cores:	8
Logical processors:	16
Virtualization:	Disabled
Hyper-V support:	Yes
L1 cache:	768 KB
L2 cache:	4.0 MB
L3 cache:	16.0 MB

Utilization	12%
Speed	3.91 GHz
Up time	0:06:49:54
Processes	259
Threads	4532
Handles	170857

Memory

16.0 GB

Speed:	2133 MHz
Slots used:	2 of 4
Form factor:	DIMM
Hardware reserved:	69.1 MB

Available	6.7 GB
Cached	6.8 GB
Committed	17.6/26.4 GB
Paged pool	620 MB
Non-paged pool	452 MB
In use (Compressed)	9.1 GB (960 MB)

GPU 0

AMD Radeon RX 5700

Driver version:	31.0.21018.6011
Driver date:	8/24/2023
DirectX version:	12 (FL 12.1)
Physical location:	PCI bus 9, device 0, function 0

Utilization	8%
Dedicated GPU memory	1.9/8.0 GB
Shared GPU memory	0.3/8.0 GB
GPU Memory	2.2/16.0 GB

beta features

  • Notched Screen Support
  • Updated Roblox Controls
  • Upgrade Shorelines
1 Like
#2

Hi @karlisjarl , thanks for reporting this issue. First question for this repro, what would be the expected result in this case?
The reason behind the size becomes some unknown value is that: the parent frame Container has Automatic Size on X axis, so its X size is depending on its children’s size on X, while the child frame Seperator has scale size 1, which is depending on the parent size. Their sizes depending on each other will cause unknown behavior in this case. Currently, this is not considered a valid usage for Automatic Size and is a known issue. Please describe more about the expected behavior and we’ll see if we can get a workaround for this.
Thank you!

1 Like
#3

I’d expect the Bar to have the same X axis size as the Container without the Container’s size being affected by it.

#4

I made a janky recreation of this and most likely your problem is the size of your Container frame. As seen near the end of my video, if the Container is too small, the Bar will effect the size of Container.

This is the intended behaviour of AutomaticSize.

#5

Thanks for getting back! In the result of your video, the Bar frame has the same X axis as the Container, the reason why the Containers size is unknown is that there is not a fixed size that’s actually deciding Containers size on the X axis. If you expect the container to have a certain width, you could consider giving the Bar frame a fixed offset size such as 100. So the Seperator knows what to grow and thus Container know about its expected width. Please let us know if you have any questions or thoughts!

#6