I noticed that after testing my place, studio would get very slow and unresponsive. I know it isn’t my computer because it’s very beefy and really, almost any modern hardware could run roblox.
The explorer, especially, gets very VERY slow.
I noticed that after testing my place, studio would get very slow and unresponsive. I know it isn’t my computer because it’s very beefy and really, almost any modern hardware could run roblox.
The explorer, especially, gets very VERY slow.
Yeah, I keep having the same issue. Eventually I just publish my game and restart studio.
Yup, same here.
How big are your places? Do you use Ribbon Bar or not? Getting more information would be very helpful when trying to figure out this issue.
When it was happening to me, my place was just the base terrain and a couple of guis I was working on. I’m not exactly sure what the ribbon bar is but I’m pretty sure I use the standard toolbar.
Same here.
And I’m running a very high end desktop PC.
The place is just one that simulates a plane flying down and crashing into an island.
I believe we figured out what it was. We have a fix in the pipe, and potentially going to patch early next week. I had to run a script spamming “New Play Solo → Reset” like 200 times before I saw the issue. I’m surprised people are getting it so easily.
I have this problem too. Would like it to be solved.
Not very large at all. Less than 5000 parts, im sure. I do not use the ribbon bar but I tested with it and I get the same issue.
We have a fix for this that will be in the next release.
We turned on a fix for this issue. Let us know if this is still happening after restarting Studio.
My explorer window will lag heavily after a few play/stops. Scripting and moving around the 3D view works fine, as well as using the explorer with a script (rather than the 3D view) open, or when testing in solo before pressing stop.
I use it while debugging my scripts, and when I start work on the 3D view again, I do a quick restart of Studio.
EDIT: Posted this before running Studio after the fix (and reading the above post…). The problem appears to be gone now