I'm still not exactly certain what causes the issue in the first place but I believe I can say with some confidence now that updating Visual Studio 2017 seems to have solved the problem. I believe restarting Unity may be what causes the times to go back to normal. Sometimes it happens and sometimes it doesn't, I really have no clue why the behavior is inconsistent sometimes. In my last project changes like file deletion would take a few seconds at most, here it takes 30+, database would take a second or two before compiling, here it takes 90+ seconds. For some reason, beforeProcessingInitializeOnLoad, afterProcessingInitializeOnLoad, and ReloadAssemblies each seem to take 35,000 ms:Īny ideas would be helpful here, I'm at a complete loss and really can't see myself building this project without a fix. This one is a little different:ĮndReloadAssembly seems to be the culprit here. I also captured a freeze that happened from saving changes to a CS file from VS, before compilation. There are no errors so I'm not sure how they could be affecting it. dll files used by one of those packages could've been causing a slowdown, but I'm not totally sure. I'm including this info because I thought maybe the. I'm using the Input System and an SSAO package I got from the store. txt file is causing all this work, it's not a script or anything so not sure why VS needs to do anything.įor clarity, I'm also running this new project in URP version 7 I believe, with minimal packages. Is it causing something to run in Visual Studio? That seems to be where the majority of the hold up is. txt file from my project, here's what it said: I was able to capture the freeze using the Profiler after deleting a. Maybe it's because I switched it from V1 to V2 instead of starting in V2 already. This didn't happen in 2019.3 with a huge project (20+ GB), even though I was using Asset Database V2 there as well. I'm using 2019.4.14 and every time I add a file/delete a file/compile it hangs for a good 30 seconds, this is for a tiny project that I just started. I have exactly the same issue, not really sure what I can do about it. If specifics about our project, such as number of assets and directories (we have a lot of directories) would be helpful, please let me know and I can provide those numbers.Īny info/insight would be greatly appreciated! I didn't see anything in the Known Issues list that seemed related to refreshes, which worries me a little bit more than I would be otherwise. I'm hoping that someone can help me figure out what's going on here and whether or not this is something we can get fixed in a later release. This is a huge concern for us because refreshes are already extremely slow on our project and eat up a lot of productivity. Please note that these tests were done on a machine with a significantly better SSD than most developers at our company possess, so in actuality these numbers will be several times higher for our average dev. One of the features we were most excited about was v2 of the AssetDatabase, which was supposed to significantly increase Editor performance for large projects.Īfter creating two side-by-side versions of our project, one on 2019.2.2 and one on the latest 2019.3 beta release, not only did we not see any gains, but we actually took a ~40% hit in asset database refresh time (2-second average on 2019.2 and 2.8-second average on 2019.3). I'm doing some preliminary 2019.3 tests on a very large project in terms of number of individual assets.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |