That’s great, but I am still wondering on why is that with every improvement that is being released there’s almost no difference that’s being made on real-world performance. I have just tested a few Roblox games that use TextChatService and I am still getting the same spikes with the same severity as before.
I am curious in what’s the main reason for these spikes and performance issues. All I know is that the spikes are worse and happen more often the larger a game server is and the more people are using the chat.
So apparently, the chat still takes up resources even when it’s disabled through the settings. Also the chat box shows on PC when it doesn’t on Mobile which is another bug. The window would still stay open and it isn’t possible to hide it due to the chat button not showing.
Great if it fixes the issue. @be_nj please update us on when the fix has rolled out, because I can’t seem to trust the release notes statuses so much when it has marked the fix of the scrollbar bug as pending now even though the fix has rolled out and even though it was marked as “live” when the release notes of version 661 were initially rolled out.
This level of performance is unacceptable and can only be mitigated by having CPU’s with industry-leading single-core speeds. Unfortunately, this very much lays in <1% of Roblox’s demographic.
Disabling the chat core gui on the client side does not prevent stutters from occurring for as long as other users in the same server have the ability to send messages. A game like Flood Escape 2 requires there to be no stutter for completing the hardest maps, and this is a direct threat to that.
Since it has been a year and a half and these performance issues are still present, the only valid method of communication from Roblox regarding this issue is now via any noticeable changes via the micro-profiler.
Given that the deadline for using the new TextChatService is by April 30th, developers should be preparing for the worst.
Developers; if your experience requires smooth frametimes I recommend offering a game setting that offers the ability to play in servers where the chat option is completely nuked and no players have access to any method of chat so that you have greater control over the performance of your experience; this should also help improve your placement in the algorithm due to increased FPS metrics on your experience if your game is not GPU-heavy.
I’ll make an actual bug report when I can confirm it happens and is very easily replicatable and it is not related to the chat issues.
Though it might be related to chat issues? Maybe it is re-rendering the entire topbar everytime (roblox uses React in lua) a chat message is sent because the chat ui change is still pending… And in microprofiler dumps they show up as ExperienceChatMain…
As I’ve said in the original comment, it’s really not that much or isn’t significant, however, if it’s completely disabled, it just shouldn’t take anything.
I can’t do that because I actually disabled the chat completely through player settings for all experiences
If anything I expect Roblox to do that by default when the chat is completely disabled through player settings. Now I would understand if a few resources are taken when having a TextChatService powered Chat with a Custom Chat UI, due to overhead of the TextChatService API, however if the chat is completely disabled through player settings or even from Studio (by disabling all default UI and stuff without making a custom chat UI), then it shouldn’t take anything, because not even the TextChatService API is supposed to run in that case.
I did notice some improvements on the peak frame time spike when playing on a Doors lobby server with a lot of players too. It now spikes at ~10ms max instead of ~15ms max. I hope to see more improvements on this field that would reduce the average and peak frame time usage even more. I want to see performance comparable or better than that of the Legacy Chat System. I want to see performance improvements on other CoreScripts too, especially for SchedulerHostConfig.default.
Also, it is interesting that there is a new ExperienceChat label. There was only the ExperienceChatMain label before.
