We’re testing improvements we are making to the open place process in Studio. Our primary goal is to reduce hangs and the time it takes to open a place so you can spend less time waiting and more time creating!
With this being such a critical part of using Studio, we want to carefully deploy this into production. During the testing period this will be turned on for a small percentage of creators.
You will know if you have this feature if you see something similar to this new loading UI:
If you see this new UI and have any feedback, please let us know.
Known Issues
There may be missing information in the loading dialog and these are minor UI bugs we are working on.
You are more likely to see this under these circumstances:
Did you plan to let us choose which place to open? I have a teleportation place as main place (little to no content), and my main game baseplate (which isn’t the official default place of the experience). I need to open the teleportation place, then hop into assets manager to open the place I want. I feel this could be simplified and I hope it is planned !
You can already do this - you need to have the experience list in ‘list’ not ‘grid’ mode. You click on the experience and there is a dropdown for each place.
Place test speed improvements next?
Our testing place takes more than 30s to test. I think testing is even more critical than opening (used more often). Improvements would be greatly appreciated.
Basically this takes all the splintered codepaths which evolved separately as things like Team Create were added to the product over the last decade, and refactors them back into a nice unified architecture, while also using the more robust modern coding patterns we’ve developed in that time.
Is there a plan to increase or change the publish timeout limit?
I haven’t tested it lately but historically the timed publish limit is unfair to Dev’s with slow internets (their effective place size limit that they can upload in a given time is smaller).
This would be more fair if it was a size based limit. If a Dev wants to wait 30 minutes to upload a 20MB place file, let them do it.
That decision was a little bit before my time but my understanding is that one of the driving factors was a big push at improving security platform wide. The current login flow for Studio has some rough edges we look forward to smoothing over.
Can we also get a fix for auto-save?
When a autosave occurs it like “refreshes” studio meaning if I’m editing an instance and it auto saves I’ll continue typing and it will end up deleting an instance, reverting changes and more.
It’s overall annoying and should be fixed, if there’s an option to disable it as well where?
