Excessive lag using Team Create when another developer joins

I discovered recently in majority of team creates I have access to, if another developer joined the team create while I was in it, my FPS would drop significantly to around 10 - 15 FPS. After more testing, It seems that as soon as anybody joins the team create, the previous person that joined will always have their FPS drop significantly. This bug of course seems to affect all of our developers regardless of which team create we join (in other places for example, the same issue occurs). We’ve tried to disable all plug-ins and beta features and test if that fixed the problem; it didn’t. We’ve also tried deleting everything in workspace, it also didn’t solve the issue.

System Information:
12th Gen Intel Core i5 12400F
32GB RAM
NVIDIA GeForce RTX 5060 Ti - 16GB

Hello There! I hope you’re doing well.
Thank you for taking the time to submit this issue and for reading our message.

To help us move forward, we’d appreciate your support with a few questions:

  • Is this issue still occurring on your device?

  • If so, could you please include a microprofiler dump?

Don’t worry — we’ve got you covered!
You can find step-by-step instructions on how to generate and send the microprofiler [How to post a Bug Report - Bug Reports - Developer Forum | Roblox]. Following these steps will help us better understand the issue and work on a solution more efficiently.
Thank you again for your cooperation!

Hey there! I’m still experiencing the issue, I’ve attached the microprofiler dump for the last 256 frames. Thanks!

microprofile-20260226-210624.zip (1.5 MB)

I’m having the same problem, this is really hampering development, as we have to restart the studio every 3-20 minutes due to the lag

My team is also experiencing this issue. Framerate tanks when another person joins, and the only thing that fixes it is a studio restart…but then you get into a ping pong on who has the bad performance because restarting studio fixes it on one end, but wrecks performance for the other users.

Encountering this issue (same team as Mukar) via post above.
Am not able to send a microprofiler-- am unable to navigate to the library necessary via the instructions given above (macbook). Let us know if theres any other info we can submit that would aid to find/address the bug!

Hey!

Just as a follow up! Any updates on the issue since the microprofiler I attached in the message below yours? There seems to be quite a lot more people that are encountering this issue!

Hello, thank you for patience with this issue. It should be mitigated now. Please let me know if it is still happening.

I am still receiving very low fps when using team create with another person. I am also getting lag spikes in the code editor.

Encountering the same issue.

Pretty much happens 100% of the time when I exit play mode.

This also seems to occur anytime Studio loses window focus (such as minimizing) and you re-open studio. When this happens, I’m by myself in a team create place, so it’s more than likely something to do with team create itself.

Also still experiencing this issue. It is impossible to work on our game. My microprofiler view shows the label “TextureManager::processPendingRequests” (also seen in the microprofiler dump attached earlier) taking gradually more milliseconds each frame before Studio becomes unusable.

We are also still experiencing the issue.

Any updates on this? It’s been days, and this bug has still been going on and has been very harmful for our productivity on an already limited time budget. Should I create a new bug report?

I’ve found the solution to the bug I originally posted a day or two ago and forgot to update, sorry!!! After some digging and completely wiping out Roblox on my computer, I found out that if anybody in the Team Create has “MaterialVarient Alpha Mode” on at any point, seems to be the source of the extreme lag.

Ensure everyone in your Team Create has that beta feature in particular turned off and you should be okay. A fresh install of studio after removing may help too.

I disabled the MaterialVariant Alpha Mode Beta on my client, and it fixed the issue for my team as well. This definitely needs to be addressed before the feature is released.