Let me start this post off by saying that we used to have a feature for shutting down TC servers. Every time this feature is removed, I complain about it and it gets reinstated, only to be silently removed at a later point. My entire team of 18 people can’t work right now, one week before release, because our TC server is completely busted and we have no way to recover it. No other engine has this problem, and it’s completely unacceptable.
About an hour ago, studio started becoming unbearably laggy. People assumed it was a memory leak and tried to rejoin. When you try to rejoin, you load forever. That’s all I know.
This has happened to one of my projects before and the only solution seems to wait for a couple of hours for the session to be terminated if shutting down TC isn’t an option, we need to toggle TC through the place settings (since it clearly is a variable stored in place settings already, just exclusively exposed through Studio).
We’ve experienced this issue in the last month as well as another odd issue that caused Team Create games to not push updates when overridden with a separate place file. Very buggy and frustrating.
Solution for us was to migrate to using sourcetree and rojo. Since we have branches and version control, there is no need for team create sessions unless it’s on an abstract place used for mapping
if shutting down TC isn’t an option, we need to toggle TC through the place settings (since it clearly is a variable stored in place settings already, just exclusively exposed through Studio).