Since upgrading to Unity 6, asset import is taking a lifetime during the “Copying files…” phase. For example, Dialogue System for Unity takes upwards of 15+ minutes for what should be a quick 5 minute process or less.
This is happening on a 4TB PCIe 4.0 NVMe SSD. So speed is not an issue. And the package size is only 32.4 MB so buffer overload on the SSD shouldn’t be a concern either.
Not sure what’s the reason, but it’s happening to all assets except for Shaders; they seem to import on a somewhat regular time schedule, if slightly longer than under the prior LTS.
Thank you for the feedback. I am using 6000.0.32f1. Anti-virus was already disabled for them, but I made additions. The compression is disabled. The issue is still recurring.
How many files are being imported, do you have a rough idea? And this “copying files” does this occur when importing the asset via Package Manager or .unitypackage? Or is this happening every time you work with that asset?
Does it take the same time when you create a new, empty project and import the asset there?
In some cases, such an issue may be caused by unoptimized editor scripts. Be it unnecessary, repeated imports and saves, or simply not using Start/StopBatchEditing when looping over files to be imported. And even editor scripts that hook into asset import or domain reload callbacks can severely degrade editor performance.
Try opening the Profiler, set it in deep profiling mode and editor profiling, then run the import and check the profiler output and callstack to get an idea where the most time is being spent.
PS: I flagged the first response as Spam since it is clearly AI fabricated.
I have exactly the same problem in Unity 6.
I tried to roll back to 2022 - everything imports quickly there.
Also tried Unity 6000.0.23f1, the problem remains.
Apparently, the problem is in the assets, because when I delete some of them - the problem disappears, but it is difficult to understand which assets are the problem, because it happened that I have 3 assets and whichever one I delete - the problem disappears, but it is important that only 2 of them remain. I know it sounds crazy, but it was.
This problem is especially noticeable when importing packages with a lot of visual assets (models, textures, etc.)
And perhaps the most unpleasant thing is that it is very difficult and time-consuming to catch this problem. You have to constantly re-enter Unity → delete some asset → then start importing another one → exit Unity with the help of task manager (because the Copying files stage takes a very long time) → start again. Profiler doesn’t help much either, as it either gets erased when the import is finished, or I have to force shut down unity and nothing is saved.
I don’t have that much time, unfortunately, so I’m back to version 2022 for now.
Windows 11
Unity 6000.0.42f1
Unity 2022.3.59f1
P.S. Found problem. It was Easy Save 3. I have written to them regarding this behavior.
The developer of Easy Save has a suggestion about this problem. Here is what he wrote:
It looks like on some versions of Unity 6 the EditorApplication.isUpdating flag isn’t always set to true in Unity’s OnWillSaveAssets event, which I suspect is a bug at their end. Luckily this is easy to work around at our end.