Issue with RichText on a SurfaceGui's TextLabel

Bug Reports Engine Bugs
#1

Reproduction Steps

  1. Create a blank baseplate.
  2. Insert a part and a SurfaceGui. The SurfaceGui is parented to StarterGui and Adornee is the part inserted.
  3. Set PixelsPerStud on the SurfaceGui to a high value.
  4. Enable RichText and TextScaled on a newly inserted TextLabel that is parented to the SurfaceGui.
  5. Set the part’s size to 64, 1, 1 where it is wide.
  6. Resize the part upwards.
  7. See this:
    image
    image807×558 51.8 KB

Reproduction File:
reproPlaceSurfaceGuiTextLabelRichTextBug.rbxl (37.5 KB)

Expected Behavior (as shown in post 5):
Font size should be limited to 100, even with RichText enabled, as it does not seem to be supported.

Actual Behavior:
Font size is not limited to 100 while using RichText and causes unintended sizing of characters while the position of the characters is correct.

Notes:

  • The font is set to Enum.Font.Legacy. This does not change the behavior of the bug.
  • No rich text tags are present.
  • The issue does not go away when playtesting or in run mode.
  • I’m unaware of any other bug report describing this exact issue. If there is any earlier bug report that provides additional information, please ignore this one.

I’m unsure when this issue started happening.

3 Likes
BillboardGui Visual Bug
#2

We’ve filed a ticket to our internal database, and we’ll follow up when we have an update.

Thanks for the report!

2 Likes
#3

This issue is still occurring as of 8/18/2023.

image
image784×559 53.9 KB

#4

Hi @SubtotalAnt8185 , we will start investigating the issue shortly, thanks for your patience!

#5

In the meantime, we advise against utilizing font sizes larger than 100. Actually we limit font size to 100 for non-RichText for a better rendering result and performance. And the limitation should also apply to RichText which might be a regression that now it renders fonts that have sizes larger than 100. Considering this, opting for smaller pixel per stud values would be advisable. Thanks for your understanding!

1 Like
#6

I have encountered this issue as well.

Description

If you enter a high value on PixelsPerStud where a Rich Text is present with relative scaling, at some point the Text just stacks together.

Re-production Steps

pixelperstud_richtext_bug.rbxlx (75.7 KB)

Experiment with the PixelsPerStud Property from the SurfaceGui.

Expected Result

I expected a higher resolution text? :thinking:

Actual Result

PixelsPerStud seems to be having a clamped limit, but it goes over the limit and at some point it causes the Rich Text to stack together.