This issue occurs in my experience that is in development.
The issue I’m having is it takes 10 tries which is about 30 seconds to load into my experience.
I have 1GB download and upload speed Fiber internet and this issue also occurs on other networks and devices.
The file size of the experience (.rbxl) was 110MB and I recently reduced it down to about 50MB by removing large portions of terrain, scripts, parts and nothing improved the loading time.
Thanks! We’re still looking into this, but I wanted to give you some more information on what’s happening. Because your experience is private and still in development, when you click “Play” from the website or app, there are usually no servers running your experience, so we need to start one. We call this a “cold start”. That’s what’s happening when you see the “Waiting for for an available server” message at the bottom of your screen.
A join with a cold start will always be slower than a normal join, but in your case, we think the cold start time is a bit longer than we would expect. We’re going to look into it from our side, but we might not have an update for you until next week.
In the meantime, you can try experimenting in Studio with the Client/Server testing mode. You can use the microprofiler, or add logging to your scripts to see if you notice anything in your experience taking a long time to initialize on the server.
Hey, sorry for the late response! We took a closer look, and we actually don’t believe this is out of the ordinary for a cold start. Once your experience is published and has players, cold starts should be less frequent. We also just announced some exciting changes to how we start up new servers, which should further decrease the probability of a cold start once your experience is published.