When using a UIScale on a Frame that contains a TextLabel with a UIStroke, setting the StrokeSizingMode to Scaled causes incorrect behavior. As the UIScale.Scale value increases or decreases, the text scales correctly, but the UIStroke thickness does not scale proportionally.
Scaling without UIScale:
ScaledSizeUIStrokeBugPlaceTest.rbxl (82.0 KB)
Expected behavior
The UIStroke thickness should scale proportionally with the UIScale, maintaining consistent visual thickness relative to the text.
Hi @Galvagnii , I took a look at the RBX file - I’m not 100% sure if this is the issue, but I noticed you are using TextScaled on the TextLabel, which limits how large TextScaled can make it. I suspect what is happening is that increasing the size by means other than UIScale lets the text and stroke grow proportionally, but with UIScale the maximum size is reached.
Please try removing the usage of TextScaled, or using only one of TextScaled or UIScale
This is a problem for me when using BillboardGuis, with a TextLabel and UIStroke.
I want to make a BillboardGui whose size changes based on the distance from the screen, but when zooming in/out there’s no way for me to clamp the size so it the label & stroke rendering size doesn’t get bigger than 100 which is the max text size.
Personally a solution I’d be happy with would be a boolean property called UIScale.ConstrainToText
which makes the UIStroke be rendered according to the text size on the parent label and takes into account whatever limitations the text rendering has. If there is any other weirdness related to text rendering (e.g. discrete font rendering sizes vs continuous stroke rendering sizes) those could be via this property as well. 
Idk just a thought.
Well I just noticed this. I was using a .TextScaled = true textlabel as a referance for a textmodule and that was creating labels which were .TextScaled = false However the UIStroke with scaled thickness of .04, which was identical to both labels and the only difference was the .TextScaled Property would appear in different thickness. However this seems to only happen at runtime which is weird.
