UICorner under BubbleChatConfiguration does not override the corner radius of chat bubbles

Setting properties of a UICorner under BubbleChatConfiguration does not update the chat bubble appearance.

image
image

This occurs with any UICorner CornerRadius, not just zero.

Reproduction:

  • Create a new place file
  • Go under “BubbleChatConfiguration”, set the CornerRadius to be zero.
  • Playtest

System info:

  • Windows 11
  • RTX 3060
  • i7 12700kf
  • 32gb DDR5 RAM
4 Likes

image

Can confirm! Tried to setup a 9-sliced image as a chat bubble ImageLabel and it’s applying a UICorner radius no matter what settings I apply.

image

image

2 Likes

CC @be_nj please take a look :eye:

1 Like

This seems somewhat related to TextChatService bubble configuration causing display issues on exit transition which we have also been looking into.

3 Likes

i’m still having this issue after roblox is forcing me to use the new textchatservice, i can’t believe roblox expects us to stop using legacy chat service when these simple features don’t work. the old chat service was more customizable as you could actually edit the bubblechat scripts

1 Like

This is still an issue, it just randomly stops working whenever it feels like it in my case.



This is still an issue and causes my image labels (when using slice) to look strange.
This is especially annoying since we’re all forced to use the new TextChatService and these features still wont work.

Hello, thank you all for your patience. Are you still facing this issue? I tried reproducing the bug and this is what UICorner.CornerRadius = (0, 0) looks like on my end.

seems that I still had the same issue
the only way to work around is to set UIcorner instance to bubblechatconfiguration after spawning character for the first time - if we set UIcorner instance prior to this, no effect will be visible to bubble chats

Understood! I’ll continue to investigate the issue. Do you have any additional bubbleChatConfiguration properties set?

1 Like

Thank you for following up! I had some properties set on my place - but after some tests, seems the current issue still presist if things are in default properties