Title says it all. Unity has always been weirdly slow. I have a very simple project, that I made no changes to at all, and now it has gone from about 30 seconds to about 8 minutes, and sometimes as much as 18 minutes, to get back into the editor from the code window. And forget about compiling.
Rebooted, done everything I can think of.
Again, always been a problem with Unity. So bad that I eventually had to disable all of the automatic updates that occur, and only do code refreshes after code has been modified, in previous versions. Had hoped this would not be necessary in newer versions, but apparently, it’s still slow and trudgy.
Worse still, now it locks up windows. Like, I cannot even bring up any explorer windows or anything else.
My experience for Unity 6 so far so good. I’m not really sure how’s that happen to you. But I know it’s terrible experience.
The latest Unity 6 version is 6000.0.15f1, maybe tried upgrade to that if still not latest version.
Also, make sure delete Library and csproj before upgrading.
My games has 10++ scenes, more than 30000++ scripts, and everything working fine. I think it’s because i use assembly definition.
I also use generate package.json for my purchased assets where it installed inPackages folder rather than in Assets.
Based upon advice found on the internet, I started disabling scripts, and eventually identified the script that was making it slow. But my problem was that Unity Editor was saying it was waiting for Unity code to finish executing, when in actuality, it was waiting my my dumba$$ script to finish doing what it was doing.
(I was making a network map, so I was pinging local IP addresses 192.168.1.0-255, and the first few times I did it, it was very fast, but then all of a sudden it started taking 4-8 minutes to run. I’ve removed it.)
So, apologies Unity. This was an I/O (Idiot Operator) error, not a Unity issue. But you can share the blame for not letting me know it was my script, and having me think it was the editor based upon that message.
Maybe switch to something like “Executing Awake() and Start() in Project Scripts.”
So what exactly was the problem? I have same problem, I have even measured times for 2019 and Unity 6. My pretty big scene in both is entered in play mode for 30 sec. But in unity 2019 it takes 6 seconds to exit play mode and go back to editor. And in Unity 6 it takes 60 seconds for same 2D scene.
So you mean it is not Unity fault, but user problem. Well… but same scene could be stopped for 6 seconds in 2019. So are some playrules changed? Do I need to rewrite some scripts? Or what causes such behavior?
(forund this topic in google about long time to exit play mode on unity 6)
Yeah, I having this issue too!
Why Unity 6 very slow and recompile something so long?
Actually I used to working on huge project (50GB) in Unity 2022LTS or older, everything fast as it should without any issue!
so I paid for plus license about 400$ per years
so many years, because I love this game engine,
But this time I working on new project with small size (lest than 10MB)
with Unity6 and it very very slow, I don’t know what happen?
if some script has been changed (just a little bit)
But it will recompile so looong!
What happen? Unity?
I was planing to go Pro plan next…
But I stop because of this issue!
Into each life rain must fall but rain can be the giver of life and it is all in your attitude that makes rain produce sunshine. — Byron Pulsifer