BillboardGui TextBounds Incorrect

Bug Reports Studio Bugs
#1

The TextBounds for a TextLabel in a BillboardGui is reading incorrectly, as can be seen here.

1475Ă—668 307 KB

And in this video, I show the Size property being updated, to which the TextBounds property does not change.

https://i.gyazo.com/6940d47ff7589691a770885fc65d4ea7.mp4

The replication steps for this are:

  • Create a BillboardGui
  • Instance a TextLabel into it
  • Turn TextScaled on for the TextLabel
    And the TextBounds will read incorrectly.

If they it were to read correctly, you should be able to size the TextLabel itself to the same size as the TextBounds, and it would be the exact same size as the text itself.

Another possibly related bug to this is when I enable TextScaled, the text piles up like this, until I disable it and re-enable it.

1210Ă—422 319 KB

This was not an issue to me until the most recent Studio update. I also deleted the UIEditor.rbxmx from the BuiltInPlugins folder in my Roblox directory, in case that may be pertinent.

15 Likes
#2

As a follow up as I try to work around this issue, I’ve tried using TextService’s GetTextSize, but the issue with that is it requires a fontSize parameter, which isn’t possible to provide when the TextLabel’s TextScaled property is true.

It appears as though I am unable to continue forth with my development in this regard until this issue is resolved.

3 Likes
#3

Thanks for the report! @Tiffblocks and I have filed this bug and will schedule work to be done on this.

5 Likes
#4

Was this ever addressed? I appear to be having the same incorrect TextBounds.

This incorrect behavior only occurs when TextScaled is enabled, otherwise the property reads correctly.

2 Likes
#5

This issue still exists in 2021, nice.

#6

This issue still exists in 2022, nice.

Note: Turning on RichText for a label fixes this. Still not optimal for what I am wanting to do though.

#7

Why has this not been addressed?

1 Like
#8

This issue still exists in 2024, are there any updates?

#9

Can we get this fixed please? This is still an ongoing issue.