(These issues only persist in the studio and not in game. In game testing loading in the game is almost instant every time)
In studio the time it takes the client to fully load into the game starts drastically increasing every test play session. (It starts at 4 seconds+ which is still long but bearable). It slowly starts taking longer. From 4 seconds to 7 to 10 to 30 to 50 to 70 to 80 seconds long each test play session.
Timeframe:
This started happening and slowly getting worse 4 months ago. (We have been in development for almost a year now)
Recording Method:
I do an intro print that at the very start of a local script within StarterPlayerScripts that logs the difference between Workspace:GetServerTimeNow() and a time Attribute that is set to the player when ever it joins the server. This pretty much shows how long it takes from when the player joined the server to how long it took the client code to start executing on the client.
My Diagnosis Attempts:
I put all the (200+) Complex Models in the ServerStorage. I only load in Complex models that the client needs.
I set the incoming replication lag 0
I cleaned up CollectionService logic
End-Summary:
It is out of my scope of knowledge to why it’s taking longer and longer to load each test play session. I tried everything with all my programmers and none of us can figure out what could be causing this
roblox studio emulates both the client and the server, meaning that roblox studio is still going to be rendering the models in serverstorage because it is simulating the server in the background
Thank you for the help;
I completely understand this. What I dont understand is how it makes load times take longer and longer each test play. This doesn’t seem like something that should happen or is something we should accept as normal.
We have a massive codebase so i’m pretty sure its some coding practices we are doing that is interfering with the way roblox clears its cache each test simulation. I dont think it actually has to do with instance count or asset size of the project even though that does attribute to long load times it doesnt attribute to it climbing overtime.
There is something in the code that is causing this. That I can’t really find out what it is. At the end of the day no matter what I have in the code it should not persist outside of the tested simulation. So therefor this is a studio bug that should be fixed either way. I would love to know what specific code practice can cause this so me and my team can work around this until its fixed.
It’s been a while, but are you still experiencing these growing load times? I believe when this was originally reported, Roblox was about to roll out some changes that might have resolved the issue, but I don’t think we checked back to get an affirmative signal that it fixed your issue.
Hey there, just wanted to say that I am still running into these issues and it likely has to do with instance count, My game creates thousands of instances each playtest and every time i load into the game it takes longer and longer to the point that it could take like 30-40 seconds sometimes before i restart studio
Hi @forbrad ! Just following up: are you still running into this issue? If so, could you send me the full Studio log from a session where it happened in a private message? You can find the logs in %LOCALAPPDATA%\Roblox\logs on Windows or ~/Library/Logs/Roblox on Mac. The newest file with “Studio” in its name is the one we need. Thanks!
It seems im getting this issue aswell. Im unable to play test my game even though most of my assets are stored in Server Storage and arent required when the game starts
Studio Log.txt (227.7 KB)
Hello, sorry for the late reply, here is the full log. Im unsure where to send the private message. Also here is the game link, you should be able to edit it Untitled Experience | Play on Roblox
Hi @Craskle Thanks so much for sending those logs over. That really helped! They allowed us to pinpoint the root cause, and we’re actively working on a fix. We expect to have it resolved by the end of next week.