Those files store the reference database for the Artifact folder.
That shows you how much garbage is kept in that folder.ĭelete the ArtifactDB and ArtifactDB-lock files. There was for about 1 week worth of work done. For example, in my case, my project Artifacts folder was close to 5.5GB in size. This folder store ALL changes you have ever done in the Editor, keeping multiple versions of each single files with changes and so on. This is by design as you wouldn't want your ALT+Z (undo) to break the Editor or something like that. The issue is that there's not much of any cleaning done in terms of obsolete data. May take a while as this is primarily all the cached data stored by the Engine to run the build internally. You could delete everything, but some file contains your project's preferences and settings, so you would have to re-enter them if you do a full wipe of the content in the Library folder.ĭelete the whole "Artifacts" folder. Go to the project folder, then to the Library folder in it. This, but another thing that can help is to clean up the Library. I'm saying all this assuming in doesn't get better by relaunching an editor that has been running for a long time and reimporting the project (which equates to deleting/regenerating the library folder). If it is because your project is very large, there are some micro-optimizations you can do but Unity is known to be slow with very large projects. Having a lot of individual assets (several dozen GBs worth) Unity can also be slow at refreshing/updating them. If you have a prefabs that have hundreds of components on hundreds of childObjects that can be pretty slow to process.
Usually this means you have a lot of assets or very large scenes that Unity needs to check for modifications every time you compile. If it's slow coming back from visual studio this could point to a few things. You can check part of this by running the profiler and checking what's taking so long to boot. For entering playmode, this probably points to some slow code taking time to initialize.
0 kommentar(er)
