We need an update for what’s going on, as from what I know including myself this issue affects everybody. Even if they (the developer) don’t realize it does.
My experiences clientside performance is being severely hindered by this issue. We have changed to the legacy chat service and are still experiencing this issue.
Yeah, I can notice in some games that use LegacyChatService that ExperienceChatMain also uses a lot of frame time in large servers but it isn’t as bad as with the Modern TextChatService.
I don’t understand how sending and receiving some texts in a chat box can be this intensive honestly, it’s not like we can send videos or images there for example.
Issue is also happening to me, whenever i press / on my keyboard to type something, theres a sudden spike of lag
Disabling all chat and setting LoadDefaultChat
to false
still has big frame times for ExperienceChatMain
this issue is the main bottleneck to having larger, lag free experiences, and if it is not going to be fixed, I would like the ability to fully disable both the chat UI, and the playerlist UI as both of those are very non-perfomant, and run in the background even if they are both disabled.
Hey, thank you all for your responses and replies to this thread.
We have identified a few improvements to ExperienceChatMain that have being seeing lifts in performance in internal testing and plan to roll these out in the next couple of weeks. We are also seeing a non trivial amount of work being done in this script even when disabled as noted above.
We will be taking a much closer look at these issues. Expect improvements to roll out week by week.
Thank you for the update, and thank you to the team behind working at solving this problem! Looking forward to the changes.
As Andrew said, thank you soooo much for working on this and attempting fixes on this problem! In the coming weeks, I’ll try profiling my game to see what’s changed.
Again, super thanks for working on this bug, especially due to how major it was.
I hope that we would hopefully get noticeable results with these improvements, since all of the previous improvements that rolled out have almost made no difference at all as far as I have seen. Please keep up updated as these improvements roll out! I hope that this issue will be completely resolved sooner rather than later, as it has been a long standing issue without a complete solution yet.
I can confirm that this is still not fixed. I think it’d be a good idea to fix this issue before even considering retiring legacy chat service, as TextChatService does make the problem worse.
Still lagging on latest version
We’ve rolled out a change to all users today that should alleviate some spikiness when interacting with and receiving messages in the chat window which should help a fair bit.
Perf is still not at a place we want it to be
We have a change in flight to address billboard guis for bubble chat/voice bubbles and have more down the pipeline.
I ended up reverting and modifying LegacyChat because of these reasons. Just got the email that this will have to go. Glad to see performance issues are getting attention but I will miss chat channels (and custom hotkeys to switch between them!), resizing, and reading old messages upon log-in.
As far as I can see, not much has improved, none of these patches have actually made any difference at all if I had to be honest. I understand the different use cases and conditions but I want to see actual noticeable improvements. The progress is also just way too slow. The first bug report for this issue has been made in November 2023, and the issue probably existed for longer, yet it appears that it’s only now that it’s getting attention but the patches don’t even make a difference for it to be useful.
Anyways, I just hope that it gets a higher if not the highest priority and gets resolved completely relatively soon. I don’t want it to still be an issue after the Legacy Chat System gets removed next year on April 30th. A lot of developers are holding back on migrating to TextChatService from the Legacy Chat System because of the performance issues, so resolving them completely would help getting more developers migrate.
This was captured today while playing on a Doors lobby with 30+ people.
microprofile-20241115-185329.html (1.2 MB)
Can you let us completely disable the loading of it like what could be done with the old chat?
Yeah I agree – we should be able to minimize a lot of the resources used if your experience loads with ChatInputBarConfiguration, ChatWindowConfiguration, and BubbleChatConfiguration as Enabled=false
This has improved performance, quite a bit, usually before this, it’d go up to the max possible length.
However after sustained spam for 200 seconds, so this is not a realistic benchmark.
Doing some quick tests of it. I don’t quite understand how the chat needs 6 to 8 milliseconds to send a message.
I don’t know how roblox does their things or whatever but man i have to ask how bloated does the entire chat system have to be for this to be an issue? I’m sorry but you guys don’t get to force us to use your magic tech while having it barely perform. I don’t care if the excuse is that “well this only happens when you send a message and its not like you send it every frame!”. If my i7 14700k takes 6-8 milliseconds to “compute” a text message then how long would an i3 2100 take? How long would a mobile chip take?
Still having this issue after an entire year, I’m becoming confused as to what could be causing this lag. It clearly shows that the chat is taking a lot of computation time, and it’s not only for sending messages but also receiving messages.
Realistically all the computation power for filtering is done on the server, and the client does the rendering, only receives a message, creates a text and shows it. This is not really expensive at all, maybe the list used for the chat causes lag? Perhaps creating the text causes lag? Perhaps it’s in the code. Just ultimately very strange behavior.
The issue was gone for a while for me, but it has just recently came back, at the start of the month.
Still having this issue on our place where we have all the default chat stuff disabled and just use a custom system with TextChatService as the backend. Lots of GetFastFlag and FindFirstChild calls for some reason.
microprofile-20241221-130338.html (7.6 MB)